configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Darcy Watkins]

Hello,

Snippet from bottom of build.log.  Anyone seen this or know what's up
here?

Regards,

Darcy

-----------------

[ALL  ]    checking whether
the /media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc/./gcc/xgcc -B/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc/./gcc/ -B/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/../x-tools/powerpc-nptl-linux-gnu/powerpc-nptl-linux-gnu/bin/ -B/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/../x-tools/powerpc-nptl-linux-gnu/powerpc-nptl-linux-gnu/lib/ -isystem /media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/../x-tools/powerpc-nptl-linux-gnu/powerpc-nptl-linux-gnu/include -isystem /media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/../x-tools/powerpc-nptl-linux-gnu/powerpc-nptl-linux-gnu/sys-include    linker (/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc/./gcc/collect-ld) supports shared libraries... yes
[ALL  ]    checking whether -lc should be explicitly linked in... no
[ERROR]    checking dynamic linker characteristics... configure: error:
Link tests are not allowed after GCC_NO_EXECUTABLES.
[ERROR]    make[2]: *** [configure-target-libstdc++-v3] Error 1
[ALL  ]    make[2]: Leaving directory
`/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc'
[ERROR]    make[1]: *** [all] Error 2
[ALL  ]    make[1]: Leaving directory
`/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc'
[ERROR]    
[ERROR]    >>  Build failed in step 'Installing final compiler'
[ERROR]    >>
[ERROR]    >>  Error happened in: CT_DoExecLog[scripts/functions]
[ERROR]    >>        called from: do_cc[scripts/build/cc/gcc.sh@623]
[ERROR]    >>        called from: main[scripts/crosstool-NG.sh@590]
[ERROR]    >>
[ERROR]    >>  For more info on this error, look at the file:
'build.log'
[ERROR]    >>  There is a list of known issues, some with workarounds,
in:
[ERROR]    >>
'/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/fs_build/share/doc/ct-ng-1.12.4/B - Known issues.txt'
[ERROR]    
[ERROR]    Build failed in step 'Installing final compiler'
[ERROR]    
[ERROR]    (elapsed: 68:58.92)



Other relevant info I can think of off the top of my head...

powerpc405ep
using kernel headers from 2.6.39.2
binutils 2.20.1
gcc 4.5.3
extra languages added are C++ and Fortran
glibc 2.13
threads are nptl





--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Don Quixote de la Mancha]

On Thu, Oct 13, 2011 at 11:14 AM, Darcy Watkins
> Snippet from bottom of build.log.  Anyone seen this or know what's up
> here?

I keep getting this while trying to bootstrap llvm-gcc4.2.

The error is spurious.  It's caused by some cruft left over from a
previous build that is screwing up a new attempt to configure your
current build.

You can fix it with "make distclean" in the right directories,
unfortunately I cannot tell from your build log which directories you
need to do it in.

Once having done "make distclean", the next attempt at building should
do a full configure successfully in the directories that you cleaned.

There was more than one of them, as I recall.

I have not yet successfully built llvm-gcc4.2.  ./configure Is A Tool
Of The Devil.

-- 
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quixote@dulcineatech.com

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Darcy Watkins]

On Thu, 2011-10-13 at 11:23 -0700, Don Quixote de la Mancha wrote:
--snip!--
> The error is spurious.  It's caused by some cruft left over from a
> previous build that is screwing up a new attempt to configure your
> current build.
> 
> You can fix it with "make distclean" in the right directories,
> unfortunately I cannot tell from your build log which directories you
> need to do it in.
--snip!--

Thanks Don for the suggestion.

I tried a scratch build from extracting the tarball again, etc.  So this
time it is fresh build using the same config file as before (before it
was after earlier errors and then changes to the config, then retry).

Failed in the same spot as before.


Regards,

Darcy



--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Khem Raj]

On Thu, Oct 13, 2011 at 11:14 AM, Darcy Watkins <dwatkins@tranzeo.com> wrote:
> [ERROR]    checking dynamic linker characteristics... configure: error:
> Link tests are not allowed after GCC_NO_EXECUTABLES.
> [ERROR]    make[2]: *** [configure-target-libstdc++-v3] Error 1
> [ALL  ]    make[2]: Leaving directory
> `/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc'
> [ERROR]    make[1]: *** [all] Error 2
> [ALL  ]    make[1]: Leaving directory

Can you post the config.log file from libsdc++ configure directory ?

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Darcy Watkins]

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Thu, 2011-10-13 at 16:38 -0700, Khem Raj wrote:
> On Thu, Oct 13, 2011 at 11:14 AM, Darcy Watkins <dwatkins@tranzeo.com>
> wrote:
> > [ERROR]    checking dynamic linker characteristics... configure:
> error:
> > Link tests are not allowed after GCC_NO_EXECUTABLES.
> > [ERROR]    make[2]: *** [configure-target-libstdc++-v3] Error 1
> > [ALL  ]    make[2]: Leaving directory
> >
> `/media/stuff/workspace/tsf/powerpc-nptl-dev/pkgs_build/crosstool-ng-1.12_powerpc/crosstool-ng-1.12.4/targets/powerpc-nptl-linux-gnu/build/build-cc'
> > [ERROR]    make[1]: *** [all] Error 2
> > [ALL  ]    make[1]: Leaving directory
> 
> Can you post the config.log file from libsdc++ configure directory ?


Hi Khem,

It is attached (bzip compressed).  Actually this one was for glibc 2.14.
I figured I'd try 2.14 but got the exact same results as for glibc 2.13.
But I think this is part of gcc 4.5.3, not glibc.

Regards,

Darcy


> 
> 


[-- Attachment #2: libstdc++-v3_config.log.bz2 --]
[-- Type: application/x-bzip, Size: 6515 bytes --]

[-- Attachment #3: Type: text/plain, Size: 71 bytes --]

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Darcy Watkins]

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.

Regards,

Darcy




--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

[Anthony Foiani]

[Sorry, just realized this didn't go out on the list...]

On Tue, Oct 18, 2011 at 2:35 PM, Anthony Foiani
<anthony.foiani@gmail.com> wrote:
>
> Darcy --
>
> On Fri, Oct 14, 2011 at 10:40 AM, Darcy Watkins <dwatkins@tranzeo.com> 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
> 4.6.)
>
> 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,
> Tony