This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ANNOUNCEMENT] New experimental package: gcc4-4.3.0-1


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Brian Dessent wrote:
> Well we already have this problem with the Cygwin DLL and standard
> malloc().  It's solved in
> lib/_cygwin_crt0_common.cc:_cygwin_crt0_common().  This code gets
> statically linked into every executable, which means when it takes the
> address of malloc and free that address will bind to the user's
> overrided function if present, otherwise it will import it from the
> DLL.  I think we can extend this for operator new and delete.

AFAICS, the problem with this approach is that it doesn't get to the
root of the problem, rather it just addresses one particular symptom.
As I mentioned previously, the weak symbol linking in binutils is what
caused XWin not to work when linked against a shared libXfont, and
certainly there are other cases where this issue arises.

OTOH, I really would like to see a dynamic libstdc++6 for 1.7.  So my
question is, how far off is a real fix to binutils, and if it's not
around the corner, will this workaround be compatible with the binutils
fix when it does happen?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkjNccwACgkQpiWmPGlmQSP38gCeNr2AZuQ3BJExY3qjAgex0P2p
HQAAoLcR5dmdFcQE7dhAdhOing0UMPlk
=qwUM
-----END PGP SIGNATURE-----

--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]