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: <43432755.9080900@cwilson.fastmail.fm>
Date: Tue, 04 Oct 2005 21:07:33 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: ATTN: g++ maintainer: Using string instances to pass arguments  to dlls
References: <20051004201411 DOT 23476 DOT qmail AT web31503 DOT mail DOT mud DOT yahoo DOT com>
In-Reply-To: <20051004201411.23476.qmail@web31503.mail.mud.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

James R. Phillips wrote:
> 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

IIRC this is what mathematicians call a "hard problem". :-)

gcc is fully autotoolized: it uses autoconf, automake, and libtool when 
building.  However, you really only get decent cygwin support for DLLs 
from libtool of 1.5.x series or better.  BUT, this requires at least 
automake-1.7.x or better, which in turn requires autoconf-2.5x or better.

Until "recently" (circa last 18 months or so), gcc used MUCH older 
versions of these tools: autoconf-2.13, automake???, and (worst of all) 
a privately hacked version of libtool-1.4.x.  However, over the last 
year or more, several dedicated people have been slowly moving gcc's 
build system over to more modern autotools.

I do not know if that process is complete, but it is a necessary (but 
not sufficient) step for building the runtime libraries as DLLs under 
cygwin.  There has been sporadic interest in correcting this problem, 
and convincing gcc to build dll runtimes under cygwin, but:
  (1) as I said, this is a "hard" problem
  (2) and it hasn't been very pressing issue: C doesn't have this 
problem; only C++, Fortran, (maybe others) need additional runtime libs 
other than cygwin1.dll -- and C is the 800 lb gorilla of open source 
software.  C++, Fortran, etc, are often afterthoughts unfortunately 
(except in specialized fields like hardcore numerics).

FWIW, Nicholas Wourms has expresses recent interest on this list in 
trying to resolve this issue (and IIRC he was active with the gcc team 
~18 months ago, and has just recently 'returned').  Nick?

--
Chuck


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