X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Requesting an updated gcc-mingw-g++ package to match gcc-g++-3.4.4-2 (PR24196)
Date:	Thu, 5 Oct 2006 10:52:46 +0100
Message-ID:	<028e01c6e864$02db7bf0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<BAY20-F3B265A04411F24FF307D0D6120@phx.gbl>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On 05 October 2006 07:19, Prehnite - wrote:

> I was running gcc-g++-3.4.4-1, and was running into the same problem of a
> std::string allocating memory in a different DLL described here:
> http://www.cygwin.com/ml/cygwin/2005-10/msg00051.html
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196

> Could someone please upload matching gcc-mingw-* packages that contain the
> fix applied to 3.4.4-2?

  Request duly noted.  I'm half-way through updating the main cygwin gcc
release ATM; I'll look at this after I've got it done and before I move on to
thinking about 3.4.6.

> Updated binary packages is of course the ideal. In the mean time, I
> attempted to build updated packages myself, however I found that the
> gcc-mingw-g++-20050522-1-src.tar.bz2 package does not meet the source
> package description described here:
> http://cygwin.com/setup.html#package_contents
> As the supposed source tarball inside it does not contain source files. It
> only contains executables, libraries, and headers. It also contains an
> un-usable configure script, and no build script. This may be ignorance on my
> part as I've never built a cygwin package from source before, but I could
> not get it to do much with the files provided.

  Yes, I am aware of that.  I have no idea how it came to be this way, it's a
situation I have inherited and will have to figure out how it's supposed to
work before I can roll any new versions.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -