<snip> >>>> So personally, I'd love to avoid that and get things compatible >>>> with XCode 4.2 by making sure everything gets to use GCC 4.2 by >>>> default. >>>> >>>> >>>> Cheers, Max > > Did we actually _confirm_ that Xcode 4.2 comes with gcc-4.2 on 10.6? > We've got a user in IRC today who doesn't have it on a fresh install, > and Alexander Strange is confident that Xcode 4.2 doesn't ship with > gcc-4.2 even on 10.6. > > I don't have the ability to confirm this for myself, so it would be > nice if someone could check. I _do_ know that the > "uninstall-devtools" script left gcc-4.2 untouched on my Lion install, > so it _looked_ like Xcode 4.2 had it. > >> Alexander, >> On my both my Lion machine (which was updated from Xcode 4.1 to 4.2) >> and my Snow Leopard machine (which was updated from Xcode 3.2.6 to 4.2) >> I see a residual binary for gcc-4.2 in /usr/bin. However, on the Lion machine >> there isn't a copy in /Developer/usr/bin. The same is true for my Snow >> Leopard >> machine except that a copy does still exist in /Developer-3.2.6/usr/bin. > >> The various copies appear as... > >> /usr/bin/gcc-4.2 -v >> Using built-in specs. >> Target: i686-apple-darwin11 >> Configured with: /private/var/tmp/gcc/gcc-5666.3~278/src/configure >> --disable-checking --enable-werror --prefix=/usr --mandir=/share/man >> --enable-languages=c,objc,c++,obj-c++ >> --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib >> --build=i686-apple-darwin11 --program-prefix=i686-apple-darwin11- >> --host=x86_64-apple-darwin11 --target=i686-apple-darwin11 >> --with-gxx-include-dir=/include/c++/4.2.1 >> Thread model: posix >> gcc version 4.2.1 (Apple Inc. build 5666) (dot 3) > >> for Lion and > >> /usr/bin/gcc-4.2 -v >> Using built-in specs. >> Target: i686-apple-darwin10 >> Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking >> --enable-werror --prefix=/usr --mandir=/share/man >> --enable-languages=c,objc,c++,obj-c++ >> --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib >> --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- >> --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 >> --with-gxx-include-dir=/include/c++/4.2.1 >> Thread model: posix >> gcc version 4.2.1 (Apple Inc. build 5666) (dot 3) > >> and > >> /Developer-3.2.6/usr/bin/gcc-4.2 -v >> Using built-in specs. >> Target: i686-apple-darwin10 >> Configured with: /var/tmp/gcc/gcc-5666.3~6/src/configure --disable-checking >> --enable-werror --prefix=/usr --mandir=/share/man >> --enable-languages=c,objc,c++,obj-c++ >> --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib >> --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- >> --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 >> --with-gxx-include-dir=/include/c++/4.2.1 >> Thread model: posix >> gcc version 4.2.1 (Apple Inc. build 5666) (dot 3) > >> for SL. My guess is that only users who upgrade from a previous Xcode >> release will retain the a legacy copy of gcc-4.2 in /usr/bin. >> It is unclear if this is a feature or a bug though. >> Jack >
Right, and the point I was trying to make is that fink-0.31.4 *doesn't work* for people who do a fresh install of Xcode 4.2, because of the absence of gcc-4.2 in the PATH. Bootstrap immediately fails, as per http://pastebin.com/5ZndHJP1 I'm not exactly sure why falling back to gcc-4.2 was suggested as a "solution", given that it is _absent_ in Xcode 4.2. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
