Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID:	<20051004201411.23476.qmail@web31503.mail.mud.yahoo.com>
Date:	Tue, 4 Oct 2005 13:14:11 -0700 (PDT)
From:	"James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
Reply-To:	antiskid56-cygwin AT yahoo DOT com
Subject:	Re: ATTN: g++ maintainer: Using string instances to pass arguments to dlls
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0

Does fixing this bug require upstream intervention, or can you just develop a
patch, and submit it to upstream?

Anecdotal evidence [1] exists that this issue may be what prevents compiling a
working version of octave 2.1.71 with gcc 3.4.4.  This comes from John Ewing
(octave upstream), who states that he is able to compile a working version with
gcc 3.4.4 only if it is statically linked.

John also wonders [2] why libstdc++ is static as opposed to shared on cygwin. 
I have searched the archives, and verified its static nature, but was unable to
find an explanation.

[1] http://www.octave.org/mailing-lists/help-octave/2005/3734
[2] http://www.octave.org/mailing-lists/help-octave/2005/3738

jrp


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