Re: Building non-cygwin DLL with cyg-gcc

["Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>]

At 01:43 PM 3/18/2001, John Fortin wrote:
> > There seem to be two methods of building DLLs, the User Guide method
> > (invoke dlltool multiple times) and the recent Mailing List method (use
> > the undocumented --output-implib ld switch).  If I do the ML method, I get
> >
> >   > gcc -Wl,--out-implib,file.a -shared -o file.dll file.o
> >   Cannot export _bss_end__: symbol not defined
> >   Cannot export _bss_start__: symbol not defined
> >   Cannot export _data_end__: symbol not defined
> >   Cannot export _data_start__: symbol not defined
> >   Creating library file: Packet.a
> >   collect2: ld returned 1 exit status
> >   make: *** [main] Error 1
>
>I'll ask this again...  Is the above the expected result of using -shared.
>Why is ld trying to export _bss_* and _data_*.
>Is it a requirement now to provide a .def file??  The mailing list archives
>talk a bit around this issue.


 From what I understand, you get this if you export everything.  In this 
case, you can end up with things looking for more than is really there.
A .def file stating exactly what you want to export resolves the situation.
My description of the details of this issue may be flawed (and someone should
correct me on these details), but I believe the solution I suggest here to 
this problem is sound.



Larry


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple