bug-m4
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cygwin vs. --disable-static


From: Ralf Wildenhues
Subject: Re: cygwin vs. --disable-static
Date: Sun, 28 Jan 2007 21:38:45 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

Old old thread:
<http://thread.gmane.org/gmane.comp.gnu.m4.bugs/2045/focus=2048>

* Eric Blake wrote on Sat, Oct 07, 2006 at 07:04:13PM CEST:
> According to Gary V. Vaughan on 10/5/2006 1:24 AM:
> > On 3 Oct 2006, at 13:44, Eric Blake wrote:
> >>> Is there some way to keep
> >>> the temporary .libs/m4.exeS.c to see what symbols it is trying to define,
> >>> and why the __fu0_* and __m4_thnk_* are failing to link?
> > 
> > Off the top of my head, ISTR rerunning the failed libtool line with
> > RM set to ':' in the environment leaves behind the temporory *S.c
> > files.
> 
> Indeed, that works.  Now my question is how to go about hooking libtool's
> calculation of $global_symbols_pipe on cygwin (and probably all Windows
> targets) to exclude the __nm_thnk* and __fu0_* symbols that nm lists, but
> which are only magic hooks to work around limitations of .dll linkage
> rather than actual C entry points.

The export_symbols_cmds variable should be kicking out __nm__* already,
see libltdl/m4/libtool.m4:_LT_LINKER_SHLIBS around line 3991.
Maybe that should instead be __nm_* and __fu0_*?  Maybe someone could
find out a definitive list of symbols to exclude, so we don't keep
tweaking this?

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]