MacPorts 1.8.1 has been released
Ralph Pass
rppass at rppass.com
Tue Sep 29 17:31:15 PDT 2009
Yes, which gcc does return /usr/bin/gcc
Ralph Pass
Bryan Blackburn wrote:
> On Tue, Sep 29, 2009 at 05:34:49PM -0400, Ralph Pass said:
>
>> I did it from the shell (I did not know that ports had an interactive mode!)
>>
>> ls -l /usr/bin/gcc* ----->
>> lrwxr-xr-x 1 root wheel 7 Sep 8 12:56 /usr/bin/gcc -> gcc-4.2
>> -rwxr-xr-x 1 root wheel 97392 May 18 13:27 /usr/bin/gcc-4.0
>> -rwxr-xr-x 1 root wheel 166128 May 18 14:13 /usr/bin/gcc-4.2
>>
>>
>> port installed "gcc*" -------> None of the specified ports are
>> installed.
>>
>
> Okay, so no funky symlinks for gcc in /usr and no gcc ports installed which
> could be compiling wrong.
>
> Just to make sure, 'which gcc' does return '/usr/bin/gcc' right? Other than
> that, I'm out of ideas at the moment.
>
> Also, don't forget to send to the list instead of just me...
>
> Bryan
>
>
>
>> You did not ask but I have:
>> .
>> .
>> .# CPU architecture to compile for. Defaults to i386 or ppc on Mac OS X 10.5
>> # and earlier, depending on the CPU type detected at runtime. On Mac
>> OS X 10.6
>> # the default is x86_64 if the CPU supports it, i386 otherwise.
>> #build_arch i386
>> .
>> .
>> .
>> # machine architectures
>> universal_archs x86_64 i386
>>
>> in the macports.config file.
>>
>>
>> Ralph Pass
>>
>>
>>
>> Bryan Blackburn wrote:
>>
>>> On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said:
>>>
>>>> More information:
>>>>
>>>> doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that
>>>> on the system that works, the architecture is x86_64 and on the one
>>>> that does not work, the architecture is i386. Both cases the gcc is
>>>> gcc-4.2. Further the dates on the Macports.dylib file is the time of
>>>> the sudo port selfupdate.
>>>>
>>>>
>>>> So why did the selfupdate use architecture i386 (and I know that Snow
>>>> Leopard now defaults to x87_64 rather than i386)?
>>>>
>>> That's definitely the question, as it shouldn't be doing that. It shouldn't
>>> be what you have for build_arch in macports.conf as I tried that, and
>>> MacPorts.dylib was still x86_64 after a selfupdate.
>>>
>>> What is the result from the following commands?
>>>
>>> $ ls -l /usr/bin/gcc*
>>> $ port installed "gcc*"
>>>
>>> Also, did you run selfupdate from the shell, or where you in port's
>>> interactive mode?
>>>
>>> Bryan
>>>
>>>
>>>
>>>> Ralph Pass
>>>>
>>>> Ralph Pass wrote:
>>>>
>>>>> Like several other people I have had trouble with updating to 1.8.1
>>>>> on Snow Leopard.
>>>>>
>>>>> On my Mac Pro (about 19 months old), I updated to Snow Leopard and
>>>>> then 1.8.0 and things worked. I then did a sudo port selfupdate
>>>>> and it worked. A sudo port upgrade outdated also worked.
>>>>> On a new (3 month old) Macbook Pro, I updated to Snow Leopard and
>>>>> then 1.8.0 and things worked. However, it failed when I did a sudo
>>>>> port selfupdate:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> sudo port selfupdate
>>>>> dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable
>>>>> image found. Did find:
>>>>> /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong
>>>>> architecture
>>>>> while executing
>>>>> "load /Library/Tcl/macports1.0/MacPorts.dylib"
>>>>> ("package ifneeded macports 1.0" script)
>>>>> invoked from within
>>>>> "package require macports"
>>>>> (file "/opt/local/bin/port" line 39)
>>>>>
>>>>>
>>>>> Note that for
>>>>> uname -a gives:
>>>>> Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
>>>>> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
>>>>>
>>>>> sw_vers gives:
>>>>> ProductName: Mac OS X
>>>>> ProductVersion: 10.6.1
>>>>> BuildVersion: 10B504
>>>>>
>>>>> So I am bit perplexed and looking for guidance.
>>>>>
>>>>> Thanks,
>>>>> Ralph Pass
>>>>>
>>> [...]
>>>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
More information about the macports-users
mailing list