configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
Tue Oct 18 21:19:00 GMT 2011
[Sorry, just realized this didn't go out on the list...]
On Tue, Oct 18, 2011 at 2:35 PM, Anthony Foiani
> Darcy --
> On Fri, Oct 14, 2011 at 10:40 AM, Darcy Watkins <firstname.lastname@example.org> wrote:
> > On Fri, 2011-10-14 at 06:41 -0700, Darcy Watkins wrote:
> > --snip!--
> > > But I think this is part of gcc 4.5.3, not glibc.
> > tried gcc 4.5.2 - same failure.
> > tried gcc 4.4.6 - success (no surprise since I used 4.4.5 before).
> > I guess for now, I just have to stick with the older gcc versions for
> > powerpc until some patches are available for the newer ones.
> Not sure what problem you might be having on your platform, but I've
> used 4.5.1 and 4.5.2, and am currently using 4.6.1. This is on a
> e300c3 32-bit platform (MPC8315E).
Also, my host system is Fedora 14 x86-64.
> (Be forewarned that going to current gcc will also require you to
> update to a much more current kernel, as the 4.6.x series introduces
> new warnings, and sections of the kernel are built with -Wall -Werror.
> I just went straight to 3.0, but I know that 2.6.36 was "too old" for
> I tend to get the "tests not allowed..." when I'm trying to
> cross-compile later packages, not during the crosstools build itself.
> I usually work around this by determining the appropriate variable in
> the ./configure script, then giving it as an environment variable in
> my own build script. E.g., for apache:
> ac_default_prefix=/ \
> ac_cv_sizeof_struct_iovec=8 \
> ac_cv_struct_rlimit=yes \
> ac_cv_define_PTHREAD_PROCESS_SHARED=yes \
> ac_cv_func_setpgrp_void=yes \
> ac_cv_file__dev_zero=yes \
> ac_site_file=NONE \
> ap_cv_void_ptr_lt_long=no \
> apr_cv_tcp_nodelay_with_cork=yes \
> apr_cv_mutex_robust_shared=yes \
> apr_cv_process_shared_works=yes \
> manualdir=/doc/httpd-manual \
> ./configure \
> --prefix=/ \
> --sysconfdir=/etc \
> --datadir=/www \
> --docdir=/doc \
> --host="$TARGET_TUPLE" \
> --enable-auth-digest \
> --enable-deflate --with-z="$PLATFORM_STAGE" \
> --enable-expires \
> --enable-headers \
> --enable-logio \
> --enable-ssl=no \
> || exit $?
> I suspect the correct answer for this issue is to switch over to
> OpenEmbedded or one of the other "build a distribution" methods,
> instead of the ct-ng "build a toolchain" model, but what I have works
> for now. :)
> Looks like I'm using ct-ng rev 181206f4bdbc from the repo. Config attached.
> Best regards,
More information about the crossgcc