Menu
▾
▴
Re: [Fink-users] gcc45 install fails on Mac Pro 4,1
|
From: Alexander H. <ale...@gm...> - 2011-06-10 10:25:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/10/11 1:03 AM, Joe Borzellino wrote: > Hello, > > I am having trouble getting gcc45 to install on my Mac Pro 4,1 (nehalem single quad core). I tried both the stable release 4.5.0-1000 and unstable 4.5.2-1000. > > I am running fink 0.30.0 selfupdate-rsync under OS X 10.6.7 x86_64. > > This is the last series of errors I get from a fink install gcc45: > > make[5]: *** [boehm.lo] Error 1 > make[5]: *** Waiting for unfinished jobs.... > ../../../../gcc-4.5.2/libjava/posix.cc: In function 'int _Jv_platform_dladdr(void*, _Jv_AddrInfo*)': > ../../../../gcc-4.5.2/libjava/posix.cc:233:3: error: 'Dl_info' was not declared in this scope > ../../../../gcc-4.5.2/libjava/posix.cc:233:11: error: expected ';' before 'addr_info' > ../../../../gcc-4.5.2/libjava/posix.cc:234:28: error: 'addr_info' was not declared in this scope > ../../../../gcc-4.5.2/libjava/posix.cc:234:37: error: 'dladdr' was not declared in this scope > make[5]: *** [posix.lo] Error 1 > make[4]: *** [all-recursive] Error 1 > make[3]: *** [multi-do] Error 1 > make[2]: *** [all-multi] Error 2 > make[1]: *** [all-target-libjava] Error 2 > make: *** [all] Error 2 > ### execution of /var/tmp/tmp.1.dkNn3p failed, exit code 2 > Removing runtime build-lock... > Removing build-lock package... > /sw/bin/dpkg-lockwait -r fink-buildlock-gcc45-4.5.2-1000 > (Reading database ... 9525 files and directories currently installed.) > Removing fink-buildlock-gcc45-4.5.2-1000 ... > Failed: phase compiling: gcc45-4.5.2-1000 failed > > > I really don't have the know-how to figure out what is going on. This was also the error I received when trying to install 4.5.0-1000 under stable tree with fink 0.29. > > Any help would be appreciated. > > Thanks, > Joe > Post the compiler command from just before errors started to occur. This looks like an old FAQ: http://www.finkproject.org/faq/comp-general.php?phpLang=en#dlfcn-from-oo and showing that compiler line could tell us where to tell you to look for a bad header. - -- Alexander Hansen, Ph.D. Fink User Liaison http://finkakh.wordpress.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3x8RsACgkQB8UpO3rKjQ+ZlACgmkJa7ONc8HYHFzAUUvRc4Cnj NsQAn3g8o6Jjl1/hGc6kpoCTcvJeDjk+ =9FRt -----END PGP SIGNATURE----- |