Greetings,
I was going through a build and after reading:
http://www.eglibc.org/archives/patches/msg01184.html
and
http://www.eglibc.org/archives/patches/msg01186.html
I have reduced the static build in cross tools configure line to this
(and added options for isl since it is separate now):
AR=ar LDFLAGS="-Wl,-rpath,/cross-tools/lib" ../gcc-4.8.1/configure --
prefix=/cross-tools --build=${CLFS_HOST} --host=${CLFS_HOST} --
target=${CLFS_TARGET} --with-sysroot=${CLFS} --with-local-prefix=/
tools --with-native-system-header-dir=/tools/include --disable-nls
--disable-shared --with-mpfr=/cross-tools --with-gmp=/cross-tools --
with-cloog=/cross-tools --with-mpc=/cross-tools --with-isl=/cross-
tools --without-headers --with-newlib --disable-decimal-float --
disable-libmudflap --disable-libatomic --disable-libgomp --disable-
libssp --disable-threads --disable-libquadmath --disable-target-
libiberty --with-system-zlib --enable-cloog-backend=isl --disable-
isl-version-check --disable-cloog-version-check --enable-languages=c
--enable-checking=release
I do not know why we had --disable-target-zlib and --with-system-
zlib.... as using --with-system-zlib disables the target zlib anyway.
Any comments on this?
libsanitize and libitm are automatically disabled so I removed those
options.
This results in:
*** This configuration is not supported in the following subdirectories:
zlib target-libquadmath gnattools target-libada target-libstdc++-
v3 target-libgfortran target-libgo target-libffi target-libbacktrace
target-zlib target-libjava target-libobjc target-libatomic target-
libmudflap target-libssp target-boehm-gc target-libitm target-
libsanitizer
Am I overlooking something or is this proper? I have the notion that
it is.
Sincerely,
William Harrington
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
