Update GCC 4.8.0 will be branched in "jan" for release in march not final release got that mixed up sorry folks.
ive been cooking with GLIBC 2.17 / GCC 4.8.0 and indeed the dependancy cycle is a problem when bootstraping you need C++ but cant build C++ without glibc the option mentioned of linking the stubs is great if you have them .... the bellow refers to a cross build but the C/C++ dependancy loop is universal most users will not bump into it if they use a 3d party compiler to build glibc and then gcc this is "std" practice it will be a issue when X compiling without access to C libs. i have just baked a aarch64 [arm64] toolchain aint got round to it till now sorry for delay ... seems to all be there and built ok. to do this i built a "null" "c" cross compiler null as it cant build itself latter but can build glibc its only purpose is to build glibc once you have glibc its disposed and replaced with a clean build with c,c++,.... opts using the --disable-bootstrap option it does not bootstrap requiring c++ ../configure --libdir=/usr/lib64 --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --infodir=/usr/share/info --localstatedir=/var --program-prefix=aarch64-linux-gnu- --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=aarch64-linux-gnu --with-build-sysroot=/build/arm64/ --without-lto --disable-bootstrap --without-cloog --without-isl --disable-libitm --disable-libmudflap --disable-libswsp --disable-libgomp --disable-libatomic --disable-libssp --disable-libquadmath --with-system-zlib --disable-libada --enable-languages=c --disable-multilib --disable-shared --with-newlib --with-sysroot=/build/arm64 --disable-threads On 28/12/2012 18:25, thorsten wrote: >> Thanks for the info. If gcc-4.8.0 is due out in a month, we may want >> to hold off on gcc-4.7.3 and go directly there. I may pull a >> pre-release version to check it out. I'd expect potential problems >> with a c -> c++ conversion. >> >> -- Bruce > In case someone is interested, I have a working toolchain with glibc-2.17/ > gcc-4.8-20121223. > > The problem with the c++ is that the first gcc-compile now needs > --enable-languages=c,c++ . This leads to libstdc++ to be built, which > requires a libc to be present. -- This message has been scanned for viruses and dangerous content by Distrotech Solutions, it is believed to be clean. http://www.distrotech.co.za -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
