GCC 4.3 - Error: Link tests are not allowed after GCC_NO_EXECUTABLES

[Hans Kester]

Ping!


When building GCC 4.3.0 for any newlib target I get:

...
supports shared libraries... yes
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking for shl_load... configure: error: Link tests are not allowed
after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/gcc/build-gcc'
make: *** [all] Error 2

I am using binutils 2.18, newlib 1.16.0 and Cygwin 1.5.24.
The configure line is:
../gcc-4.3.0/configure --prefix=/usr/local/gcc-4.3.0-i686-elf
--target=i686-elf --with-gnu-as --with-gnu-ld --with-newlib
--with-headers=/gcc/newlib-1.16.0/newlib/libc/include --disable-shared
--disable-libssp --enable-languages=c,c++

I searched for this error and found:
http://gcc.gnu.org/ml/gcc/2007-09/msg00421.html
Wasn't this patched? How do I fix this?

Regards,

Hans Kester

Re: GCC 4.3 - Error: Link tests are not allowed after GCC_NO_EXECUTABLES

[Hans Kester]

Thanks for your understandable summary.

On Tue, Mar 11, 2008 at 2:22 PM, Brian Dessent <[EMAIL PROTECTED]> wrote:
> There was one additional solution discussed: disable libtool's checking
> of dlopen() for newlib targets:
>   I think
> everyone agreed that this was a suitable compromise, and that the way
> forward was to revert the libgloss hacks, implement the config.cache
> idea as an optional alternative, and commit the patch to disable
> dlopen() checking on newlib.

That works. After replacing AC_LIBTOOL_DLOPEN with

  if test "x${with_newlib}" != "xyes"; then
AC_LIBTOOL_DLOPEN
  fi

and running autoconf I was able to build six different newlib targets.

> However nothing seemed to ever actually get committed: neither that
> above patch nor the config.cache one seem to have made it into the
> tree.  I think the thread had diverged somewhat into people discussing
> if and how it would be possible to make other target libraries more like
> libstdc++ so that they could more easily build for bare metal newlib
> targets too.  In all of that noise, nobody seems to have committed
> anything, and it looks like 4.3.0 went out the door meanwhile.

Can anybody put at least one patch in? The above one works fine for me.

Too bad GCC 4.3.0 fails to inline functions correctly. Only O0 and O1
work, O2 and O3 produce erroneous code.
So I will stick with 4.2.3 for a while.

Hans

x64_64-elf support

[Hans Kester]

Is there any reason why this contribution from Mikkel Krautz is still
not in the current sources?
http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01592.html

Hans Kester






===

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify Ellips B.V. This message 
contains confidential information and is intended only for the individual 
named. If you are not the named addressee you should not disseminate, 
distribute or copy this e-mail. Please notify the sender immediately by e-mail 
if you have received this e-mail by mistake and delete this e-mail from your 
system. If you are not the intended recipient you are notified that disclosing, 
copying, distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Ellips B.V, Urkhovenseweg 11, 5641 KA 
Eindhoven, The Netherlands, www.ellips.nl, [EMAIL PROTECTED]

Deze e-mail en eventuele bijlages zijn vertrouwelijk en alleen voor gebruik 
door de bedoelde ontvanger. Wanneer u deze e-mail onterecht ontvangen heeft, 
notificeert u dan Ellips B.V. Dit bericht bevat vertrouwelijke informatie en is 
alleen bedoeld voor de bedoelde ontvanger. Wanneer u deze ontvanger niet bent, 
dient u deze e-mail niet te verspreiden of te kopieeren. Bericht de zender 
alstublieft meteen door de e-mail te beantwoorden en verwijder dan deze e-mail  
van uw systeem. Wanneer u niet de bedoelde ontvanger bent, bent u bij deze 
ingelicht dat verspreiden, kopieeren en het oneigenlijk gebruiken van deze 
inhoud strikt verboden is. Ellips B.V, Urkhovenseweg 11, 5641 KA Eindhoven, 
Nederland, www.ellips.nl, [EMAIL PROTECTED]
Ellips B.V.

RE: GCC 4.5.1 Released (2)

[Hans Kester (Ellips B.V.)]

Ik zie ook wat leuke dingen in de release notes:

* MIPS targets now support the -fstack-protector option.

Uit de handleiding:

-fstack-protector
Emit extra code to check for buffer overflows, such as stack smashing
attacks.
This is done by adding a guard variable to functions with vulnerable
objects.
This includes functions that call alloca, and functions with buffers
larger than
8 bytes. The guards are initialized when a function is entered and then
checked
when the function exits. If a guard check fails, an error message is
printed and
the program exits.

-fstack-protector-all
Like '-fstack-protector' except that all functions are protected.




-Original Message-
From: gcc-announce-ow...@gcc.gnu.org
[mailto:gcc-announce-ow...@gcc.gnu.org] On Behalf Of Richard Guenther
Sent: Sunday, August 08, 2010 10:47 AM
To: gcc-annou...@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: GCC 4.5.1 Released


The GNU Compiler Collection version 4.5.1 has been released.

GCC 4.5.1 is a bug-fix release containing fixes for regressions and
serious bugs in GCC 4.5.0.  This release is available from the
FTP servers listed at:

  http://www.gnu.org/order/ftp.html

Please do not contact me directly regarding questions or comments about
this release.  Instead, use the resources available from
http://gcc.gnu.org.

As always, a vast number of people contributed to this GCC release --
far
too many to thank individually!

GCC 4.3 - Error: Link tests are not allowed after GCC_NO_EXECUTABLES

[Hans Kester (Ellips B.V.)]

When building GCC 4.3.0 for any newlib target I get:

...
supports shared libraries... yes
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking for shl_load... configure: error: Link tests are not allowed
after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/gcc/build-gcc'
make: *** [all] Error 2

I am using binutils 2.18, newlib 1.16.0 and Cygwin 1.5.24.
The configure line is:
../gcc-4.3.0/configure --prefix=/usr/local/gcc-4.3.0-i686-elf
--target=i686-elf --with-gnu-as --with-gnu-ld --with-newlib
--with-headers=/gcc/newlib-1.16.0/newlib/libc/include --disable-shared
--disable-libssp --enable-languages=c,c++

I searched for this error and found:
http://gcc.gnu.org/ml/gcc/2007-09/msg00421.html
Wasn't this patched? How do I fix this?

Regards,

Hans Kester