This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Linux vs Cygwin linkage
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 18 Feb 2006 13:45:34 -0500
- Subject: Re: Linux vs Cygwin linkage
- References: <1140287981.4091.76.camel@rosella.wigram>
- Reply-to: cygwin at cygwin dot com
On Sun, Feb 19, 2006 at 05:39:41AM +1100, skaller wrote:
>I have found some unexpected differences between Cygwin and Linux. FYI
>I think Cygwin is right, and Linux is wrong.
>
>What happens is I have a DLL P which depends on a DLL F and a DLL D. A
>also depends on R. The executable depends on R D and F.
>
>Under Linux, I link P against F, and it works. IMHO this is just plain
>wrong. It seems to be pooling symbols globally or something.
>
>Under Cygwin this does not happen. The link of P fails with an
>undefined symbol from D. I think this is correct.
>
>If anyone can throw some light on this I'd appreciate it. Is it this
>option:?
>
>--allow-shlib-undefined --no-allow-shlib-undefined Allows (the default)
>or disallows undefined symbols in shared libraries.
>
>Can I fix that with
>
>-Wl,--no-allow-shlib-undefined
>
>switch to gcc, so Linux and Cygwin behave the same?
This is a question for a linux mailing list. Why are you asking here?
cgf
--
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/