public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2841
Date: Wed, 23 May 2001 08:36:00 -0000 [thread overview]
Message-ID: <20010523153601.16245.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/2841; it has been noted by GNATS.
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bkoz@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/2841
Date: Wed, 23 May 2001 17:32:52 +0200 (MEST)
bkoz@gcc.gnu.org writes:
> FYI to get shared libraries working/building, you'll have to do top-level work to the libtool cxx files (ltcf-cxx.sh) to add support for Tru64. Alexandre Oliva is a good person to talk to about this, as well as Loren James Rittle <rittle@latour.rsch.comm.mot.com>, who added support for BSD.
I had them working some time in the past, but cannot find the old build
trees anymore, so I don't really know what changed since then. It may well
be related to one of Alexandre's recent checkins of more recent libtool
versions. I'll dig around a bit and report what I find.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE
next reply other threads:[~2001-05-23 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 8:36 Rainer Orth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-06 5:06 libstdc++/2841 Rainer Orth
2001-06-05 18:36 libstdc++/2841 bkoz
2001-05-25 12:26 libstdc++/2841 Rainer Orth
2001-05-23 14:26 libstdc++/2841 Rainer Orth
2001-05-23 14:16 libstdc++/2841 Benjamin Kosnik
2001-05-23 12:26 libstdc++/2841 Rainer Orth
2001-05-23 12:26 libstdc++/2841 Rainer Orth
2001-05-23 9:46 libstdc++/2841 Benjamin Kosnik
2001-05-22 18:36 libstdc++/2841 bkoz
2001-05-22 17:46 libstdc++/2841 bkoz
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=20010523153601.16245.qmail@sourceware.cygnus.com \
--to=ro@techfak.uni-bielefeld.de \
--cc=bkoz@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
/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).