getopt: ugly linker messages

Ivan Warren ivan@vmfacility.fr
Sat Sep 20 19:40:00 GMT 2003



> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Ivan Warren
> Sent: Saturday, September 20, 2003 2:43 AM
> To: cygwin@cygwin.com
> Subject: RE: getopt: ugly linker messages
> 
> 
> > And.. Hmmm..
> >
> > I *think* auto import of data variables may be somewhat broken (and 
> > declared import of data variables too) if
> >
> > 1) The import library is stripped with --strip-unneeded
> >    and/or
> > 2) The import is from another DLL (.exe -> .dll[func] -> .dll[data])
> >
> > (See msg dated 9/17/03 which seems to have been drowned.. 
> There is a 
> > test case in it)
> >
> > --Ivan
> >
> Okies...
> 
> Does anyone know at least if it's a cygwin or core binutils 
> issue ? Or if I am at least looking in the right direction ?
> 
> --Ivan
> 
> 

<rant>
Sniff.. Why am I being ignored ?

I thought I had a quite thoroughly documented problem.

I have a test case which I posted 4 days ago..
(http://cygwin.com/ml/cygwin/2003-09/msg01132.html) and I asked again
yesterday if I was at least looking in the right direction. But it's just
like the messages are not even getting there (I know they are - they are on
the mailing list archive..)

I know this is a community effort and that no-one is obliged to answer (no,
I didn't go for the pay support.. I am working on an open source project, so
I don't have the monetary resource to spend).

But it's just frustrating.

The problem is I don't really understand the internals of the PE 386 binder
(or I would surelly propose a patch).

Also if the problem is a core "binutils" issue, please someone tell me (and
then I'll go bug the binutils folks !)

</rant>

However, in the meanwhile I have a workaround, so it's not an emergency..

(Workaround : The issue lies when the Makefile is generated with automake &
libtool - the 'make strip' insist on stripping the import library - the
workaround involves patching the libtool.m4 AC_LIBTOOL_SYS_LIBSTRIP macro to
force it NOT to strip libs on cygwin).

--Ivan


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list