GCC Version
Paul C
crispy1975 at gmail.com
Fri Jul 22 10:11:12 PDT 2011
Here are the results from what I assume are the correct files:
$ file ./libmpfr.4.dylib
./libmpfr.4.dylib: Mach-O 64-bit dynamically linked shared library ppc64
$ file ./libgmp.10.dylib
./libgmp.10.dylib: Mach-O 64-bit dynamically linked shared library ppc64
$ file ./libmpc.2.dylib
./libmpc.2.dylib: Mach-O 64-bit dynamically linked shared library ppc64
That seems to suggest the libs are 64bit. The debug log for gcc says
it's found the header files, the --with config options all use the
prefix of /opt/local as defined in the Portfile.
--with-gmp=/opt/local
--with-mpfr=/opt/local
--with-mpc=/opt/local
On 22/07/11 18:05, Jeremy Huddleston wrote:
> Are you *sure* that gmp, mpfr, and mpc are ppc64? Did you run 'file' on the libraries? config.log will provide more specific information as to what went wrong...
>
>
> On Jul 22, 2011, at 9:00 AM, Paul C wrote:
>
>> On 22/07/11 15:43, Vincent Lefevre wrote:
>>>> http://www.linuxquestions.org/questions/linux-newbie-8/error-in-installing-gcc-4-5-0-a-818033/
>>>>
>>>> As detailed in the forum thread in the link the problem I get installing gcc
>>>> is not specific to ppc or to MacPorts. It would seem to be a generic problem
>>>> across platforms that shows up.
>>>
>>> I'm not sure, but this one can be a Linux-only issue. Under Linux,
>>> /usr/local/lib may have to be added to LIBRARY_PATH. Some responses
>>> mention LD_LIBRARY_PATH, but the error here is from gcc at link time,
>>> not at run time.
>>>
>>> I don't know about the error for MacPorts with ppc64. The config.log
>>> of gcc can give interesting information.
>>
>> I'm not so sure that's the solution for MacPorts either, but I pasted it more due to the same errors during configuration rather than the solution. Other solutions I've seen is the libraries being compiled for 32bit and gcc expecting 64bit versions, however I don't think that is the case here as I've opted for pure 64bit (ppc64).
More information about the macports-users
mailing list