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:
http://gcc.gnu.org/ml/gcc-patches/2007-11/msg01560.html I think
everyone
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
Hans Kester wrote:
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?
It wasn't actually fixed. That was a very long thread and it's easy to
get confused, particularly since the mailing list archives don't
crossthread
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.