This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Am 02.08.2005 22:54, Peter Schaefer wrote: >> I'm currently struggling with crosstool trying to compile >> the subjects' toolchain. The core-gcc seems to miss libiberty.a; >> however, libiberty.a is available in $RESULT_TOP/lib. Replying to myself, without solution yet. What i can see by investigating the build logs is that the steps * Build binutils * Build gcc-core w/o shared libgcc (just enough to build glibc starfiles) * Build glibc startfiles (required for shared libgcc) went OK, however, the step * Build gcc-core w shared libgcc failed. The last two steps were added by the NPTL patch, so Dan probably cannot help me here... The configure call used for shared libgcc is ${GCC_DIR}/configure $CANADIAN_BUILD --target=$TARGET --host=$GCC_HOST --prefix=$PREFIX \ --with-local-prefix=${SYSROOT} \ --disable-multilib \ ${GCC_EXTRA_CONFIG} \ ${GCC_SYSROOT_ARG_CORE} \ --disable-nls \ --enable-symvers=gnu \ --enable-__cxa_atexit \ --enable-languages=c \ --enable-shared Does anybody else see the light? (.. sorry for those questions, but i'm just starting with cross-compiling business - just because the need for NPTL ...) Best regards, Peter ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |