Hi Eric!
On 7 Oct 2006, at 18:04, Eric Blake wrote:
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.
How can we tell the difference between an actual C entry point and a
magic
hook?
Cheers,
Gary.
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
