I have found some more information on this issue. Make, at the gcc level
runs the configure script in zlib. The error is occurring in the
configure script of zlib. In particular the following code is producing
the error:
# Some binutils ld are patched to set DT_RUNPATH
if test "${lt_cv_shlibpath_overrides_runpath+set}" = set; then :
$as_echo_n "(cached) " >&6
else
lt_cv_shlibpath_overrides_runpath=no
save_LDFLAGS=$LDFLAGS
save_libdir=$libdir
eval "libdir=/foo; wl=\"$lt_prog_compiler_wl\"; \
LDFLAGS=\"\$LDFLAGS $hardcode_libdir_flag_spec\""
if test x$gcc_no_link = xyes; then
as_fn_error "Link tests are not allowed after GCC_NO_EXECUTABLES."
"$LINENO" 5
fi
This code is executed twice, once with gcc_no_link set to no and another
with it set to yes. It is on the second pass that the error occurs. On
the first pass the variable lt_cv_shlibpath_overrides_runpath is set to
no, however on the second pass it has lost it's value. I have not yet
found out why it is losing it's value.
Another interesting thing I found was that during the first pass, the
library is compiled in a subdirectory of gcc called "64". The target of
this compile appears to be the x86 platform, not the arm.
Also for some reason the gcc compiler being found is gcc -m64. I have
not yet found out why.
Hopefully with this information some one can give me some guidance.
Thank You,
Donald Schlicht.
On Tue, 2010-07-20 at 19:44 -0400, Donald Schlicht wrote:
> I am trying to make an ARM cross compile from the current gnu gcc
> sources. I am encountering a problem when compiling the first gcc cross
> compiler. I get the error message "Link tests are not allowed after
> GCC_NO_EXECUTABLES". I have attached a screen drop from the make
> command.
>
> My system: Ubuntu 10.04 LTS. The OS is patched to the latest patches for
> that OS. The gcc version is 4.4.3. I have compiled and installed
> gmp-5.0.1, mpfr-3.0.0 and mpc-0.8.2. All of these pass their make check
> test.
>
> I have downloaded and extracted: binutils-2.20.1, gcc-4.5.0 and
> newlib-1.18.0.
>
> I have configured and make binutils with the commands:
> ./configure --target=arm-elf --prefix=/donald/home --enable-interwork
> --enable-multilib CC=gcc
> make all install
> Binutils appears to compile and link correctly, the executable files are
> created, and no errors are shown.
>
> However when I try to configure and make the first stage gcc compiler,
> using these commands:
> /configure --target=arm-elf --prefix=/donald/home --enable-interwork
> --enable-multilib --enable-languages="c,c++" --with-newlib
> --with-headers=/donald/Documents/newlib/newlib/libc/include CC=gcc
> make all-gcc install-gcc
> The configuration process appears to work correctly, however the make
> process fails when trying to compile the zlib library. The output of the
> make process is copied to the attached file.
>
> I can bypass this problem with adding the option --with-system-zlib.
> However I would like to solve this issue. It appears to be unique to my
> system, as I have searched the archives and have not found a similiar
> problem. Several years ago there was a similiar problem in the libstdc
> ++-v3 library. I looked into that fix, but could not see a similiar
> sequence of statements in zlib.
>
> Can someone send me down a path as to what causes this problem, and how
> to fix it.
