From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: ATTN: g++ maintainer: Using string instances to pass arguments to dlls
Date: Wed, 05 Oct 2005 01:07:00 -0000 [thread overview]
Message-ID: <43432755.9080900@cwilson.fastmail.fm> (raw)
In-Reply-To: <20051004201411.23476.qmail@web31503.mail.mud.yahoo.com>
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/
next prev parent reply other threads:[~2005-10-05 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 20:14 James R. Phillips
2005-10-05 1:07 ` Charles Wilson [this message]
2005-10-05 9:02 ` Pavel Tsekov
2005-10-05 10:37 ` Gerrit P. Haase
2005-10-05 17:15 ` Pavel Tsekov
2005-10-05 22:05 ` Gerrit P. Haase
2005-10-06 7:31 ` Pavel Tsekov
2005-10-05 10:35 ` Gerrit P. Haase
2005-10-06 21:16 ` Yaakov S (Cygwin Ports)
2005-10-11 20:56 ` Gerrit P. Haase
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 15:02 Pavel Tsekov
2005-10-04 19:09 ` Gerrit P. Haase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43432755.9080900@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).