* Ralf Wildenhues wrote on Tue, Mar 29, 2011 at 07:55:27AM CEST:
* Ian Lance Taylor wrote on Tue, Mar 29, 2011 at 07:39:25AM CEST:
Shortly after that code in libtool.m4, I see this:
if test -f /etc/ld.so.conf; then
lt_ld_extra=`awk '/^include / { system(sprintf(cd /etc; cat %s
On Mon, 28 Mar 2011, Ian Lance Taylor wrote:
We have several bug reports for 4.6.0 about failures of the form
checking dynamic linker characteristics... configure: error: Link tests are
not allowed after GCC_NO_EXECUTABLES.
http://gcc.gnu.org/PR47836
http://gcc.gnu.org/PR46586
Joseph S. Myers jos...@codesourcery.com writes:
In general link tests *are* required for GNU/Linux targets, because of
e.g. uClibc configurations where some functions may be disabled and this
can sometimes only be detected through a link test. Furthermore, when
building shared libraries
On 03/29/2011 01:33 PM, Joseph S. Myers wrote:
But some of
those bug reports refer to target libiberty - which I still maintain
should never be built by GCC - and some to target zlib, which I think
should only be relevant when building Java.
Agreed on both counts.
Paolo
We have several bug reports for 4.6.0 about failures of the form
checking dynamic linker characteristics... configure: error: Link tests are not
allowed after GCC_NO_EXECUTABLES.
http://gcc.gnu.org/PR47836
http://gcc.gnu.org/PR46586
http://gcc.gnu.org/PR45174
http://gcc.gnu.org/PR39107
The
Hello Ian,
* Ian Lance Taylor wrote on Tue, Mar 29, 2011 at 07:39:25AM CEST:
We have several bug reports for 4.6.0 about failures of the form
checking dynamic linker characteristics... configure: error: Link tests are
not allowed after GCC_NO_EXECUTABLES.
Unfortunately, on a GNU/Linux
