Hi Jack, On 29 Apr 2014, at 16:31, Jack Howarth <howarth.at.f...@gmail.com> wrote: Hi Jack,
it looks all fine to me: $ which gcc /usr/bin/gcc $ gcc -v Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.1.0 Thread model: posix $ which g++ /usr/bin/g++ $ g++ --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.1.0 Thread model: posix The same when running within the gcc49 fink package: + which gcc /opt/fink/var/lib/fink/path-prefix-clang/gcc gcc -v + gcc -v Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.1.0 Thread model: posix clang: warning: argument unused during compilation: '-Wno-error=unused-command-line-argument-hard-error-in-future' which g++ + which g++ /opt/fink/var/lib/fink/path-prefix-libcxx/g++ g++ -v + g++ -v Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.1.0 Thread model: posix Remi > Remi, > The only instance of this sort of failure is from MacPorts last year… > > http://trac.macports.org/ticket/41917 > > The problem apparently wasn't considered critical by the MacPorts developers. > I believe this was because the user was using the ancient /usr/bin/gcc-4.2 > compiler. The fink packaging has been tested on both darwin12 and darwin13 > using Xcode 5.1.1 without issue as well as darwin11 with Xcode 4.6. I would > make sure that you have a stock installation of the devtools without any > customized symlinks or legacy binaries from previous Xcode releases left > behind. You might try executing the system compilers by hand with -v to > confirm that those in /usr/bin are really from Xcode 5.1.1. The Mavericks > release introduced compiler stubs into /usr/bin which automate the > installation of Xcode and the command line tools. If the upgrade to Mavericks > went wrong and those stubs are not installed, the legacy compilers might be > used rather than those from Xcode 5.1.1. Note that the Command Line Tools > don't install directly into /usr/bin in Mavericks so that if the compiler > stubs don't replace the legacy compiler binaries in /usr/bin during the > installation of Mavericks, the mechanism for finding the proper compilers is > defeated. > Jack > ps If you find that the legacy compilers haven't been replaced by the > compiler stubs in /usr/bin, a reinstallation of the latest Mavericks from > Apple followed by reinstalling the command line tools with 'xcode-select > --install' should solve the problem. > > > On Tue, Apr 29, 2014 at 9:15 AM, Remi Mommsen <remigius.momm...@cern.ch> > wrote: >> Hi Jack, >> >> I'm trying to build gcc49-4.9.0-1000 on a rather old MacBook Pro (15-inch >> Early 2008) with Mac OS 10.9.2. However, the build fails reproducible: >> >> /opt/fink/src/fink.build/gcc49-4.9.0-1000/darwin_objdir/./gcc/xgcc >> -B/opt/fink/src/fink.build/gcc49-4.9.0-1000/darwin_objdir/./gcc/ >> -B/opt/fink/lib/gcc4.9/x86_64-apple-darwin13.1.0/bin/ >> -B/opt/fink/lib/gcc4.9/x86_64-apple-darwin13.1.0/lib/ -isystem >> /opt/fink/lib/gcc4.9/x86_64-apple-darwin13.1.0/include -isystem >> /opt/fink/lib/gcc4.9/x86_64-apple-darwin13.1.0/sys-include -g -O2 -m32 >> -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual >> -Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition >> -isystem ./include -pipe -fno-common -g -DIN_LIBGCC2 -fbuilding-libgcc >> -fno-stack-protector -pipe -fno-common -I. -I. -I../../.././gcc >> -I../../../../gcc-4.9.0/libgcc -I../../../../gcc-4.9.0/libgcc/. >> -I../../../../gcc-4.9.0/libgcc/../gcc >> -I../../../../gcc-4.9.0/libgcc/../include -DHAVE_CC_TLS -DUSE_EMUTLS -o >> _mulxc3.o -MT _mulxc3.o -MD -MP -MF _mulxc3.dep -DL_mulxc3 -c >> ../../../../gcc-4.9.0/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS >> ../../../../gcc-4.9.0/libgcc/libgcc2.c: In function '__mulxc3': >> ../../../../gcc-4.9.0/libgcc/libgcc2.c:1964:6: internal compiler error: >> Illegal instruction: 4 >> a = COPYSIGN (isinf (a) ? 1 : 0, a); >> ^ >> libbacktrace could not find executable to open >> Please submit a full bug report, >> with preprocessed source if appropriate. >> See <http://gcc.gnu.org/bugs.html> for instructions. >> >> Package manager version: 0.36.4.1 >> Distribution version: selfupdate-cvs Tue Apr 29 11:13:50 2014, 10.9, x86_64 >> Trees: local/main stable/main >> Xcode.app: 5.1.1 >> Xcode command-line tools: 5.1.0.0.1.1396320587 >> Max. Fink build jobs: 2 >> >> >> I also tried the build with only one build job, but no avail. >> >> Any ideas? >> >> Remi >> >>
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs
_______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
