On Fri, Dec 3, 2010 at 8:10 AM, Paul Koning <paul_kon...@dell.com> wrote: > > On Dec 2, 2010, at 4:06 PM, H.J. Lu wrote: > >> On Thu, Dec 2, 2010 at 1:01 PM, Paul Koning <paul_kon...@dell.com> wrote: >>> >>> On Dec 2, 2010, at 3:55 PM, H.J. Lu wrote: >>> >>>> On Thu, Dec 2, 2010 at 12:42 PM, Paul Koning <paul_kon...@dell.com> wrote: >>>>> >>>>> On Dec 2, 2010, at 3:05 PM, Ian Lance Taylor wrote: >>>>> >>>>>> Paul Koning <paul_kon...@dell.com> writes: >>>>>> >>>>>>> On Dec 2, 2010, at 2:55 PM, Ian Lance Taylor wrote: >>>>>>> >>>>>>>> Paul Koning <paul_kon...@dell.com> writes: >>>>>>>> >>>>>>>>> I'm trying to do a cross-build of gcc 4.5.1. It works fine until I >>>>>>>>> get to libstdc++v3, where configure blows up with a message saying >>>>>>>>> "Link tests are not allowed after GCC_NO_EXECUTABLES". This happens >>>>>>>>> on the "checking for shl_load" step (line 11221 in configure). >>>>>>>>> >>>>>>>>> I looked at configure.ac to see if there were any clues. I can't tell >>>>>>>>> which line in configure.ac produces the offending line in configure >>>>>>>>> (not enough autoconf skills). In an earlier gcc (3.3.3) there was a >>>>>>>>> similar issue, and in that case I worked around it by removing >>>>>>>>> "GLIBCPP_CHECK_COMPILER_VERSION" from the configure.in file. But that >>>>>>>>> line doesn't exist in configure.ac and attempts to find something >>>>>>>>> analogous didn't get me anywhere. >>>>>>>> >>>>>>>> GCC_NO_EXECUTABLES, in config/no-executables.m4, redefines >>>>>>>> AC_LINK_IFELSE to produce that error message. >>>>>>> >>>>>>> Thanks. But why does the released configure fail like this? Any idea >>>>>>> how to fix this bug? >>>>>> >>>>>> You need to tell us precisely what you tried to do and precisely what >>>>>> happened. >>>>>> >>>>>> The TARGET/libstdc++-v3/config.log file may contain a clue. >>>>> >>>>> It's configured --target=mips64el-netbsdelf --enable-languages=c,c++, on >>>>> an i686-pc-linux-gnu host. >>>>> >>>> >>>> Can you try sysroot with full mips64el-netbsdelf C library and header >>>> files? >>> >>> I have newlib and a full set of headers. >>> >> >> Please DO use sysroot. > > That doesn't help. > > No real surprise; --with-sysroot doesn't change the fact that I'm building a > cross-compiler, and that fact is what disables link tests. So the thing that > appears to be needed is to avoid the link tests. >
Link test should work with a fully populated sysroot, Build a complete cross toolchain, gcc + binutils + libc, is a different story. H.J.
