X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <48CD71CC.3060704@users.sourceforge.net>
Date: Sun, 14 Sep 2008 15:19:24 -0500
From: "Yaakov (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New experimental package: gcc4-4.3.0-1
References: <announce.001001c91336$91e70d10$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48C8FE4D DOT 1090103 AT users DOT sourceforge DOT net> <013401c9140b$22b569c0$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48CA2107 DOT FE8D0CB2 AT dessent DOT net> <01cb01c914db$53d34d80$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48CAFDD9 DOT 641C423A AT dessent DOT net>
In-Reply-To: <48CAFDD9.641C423A@dessent.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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