From: hjl@lucon.org (H.J. Lu)
To: manfred@s-direktnet.de
Cc: egcs@cygnus.com
Subject: Re: libg++ (again)
Date: Thu, 12 Mar 1998 08:22:00 -0000 [thread overview]
Message-ID: <m0yDAk8-00058JC@ocean.lucon.org> (raw)
In-Reply-To: <13575.33474.833614.662788@slsvhmt>
>
> On Wed, 11 March 1998, 20:07:00, jkj@sco.com wrote:
>
> > Ok.
> > Got libstdc++2.8.1. Got libg++2.8.1. Moves the extracted libg++2.8.1 into
> > libstdc++ directory and called it "libg++". Which, by the way, the
> > README doesnt tell you to do. Do a configure inthe main dir, start the
> > make, and everything works to a point. First think it barfs on it a
> > lack of "rx.h" ... did GNU rx used to be in this package somewhere?
> > Then start make again and it gets further, this time stopping due to:
> > 'No rule to make target libgxx.list'.
> >
> > This is on a multi-libbed target, if that makes any difference.
>
> Who packaged this file? The directory librx is missing, and I'd
> suppose adding the README.libg++ file wouldn't be bad, either.
>
Jeff, could you please install my egcs/configure patch? libstdc++
2.8.1 has it. But egcs doesn't. People still need to apply my patch
contained in README.libg++ if they want to use it as the libg++ addon
for egcs. Thanks.
> We should simply take H.J.'s file from
>
> < ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.1-980306.tar.gz >
>
> rename it to libg++-2.8.1.tar.gz and copy it ASAP over the existing
> one on ftp.gnu.org!
>
> manfred
>
--
H.J. Lu (hjl@gnu.org)
next parent reply other threads:[~1998-03-12 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13575.33474.833614.662788@slsvhmt>
1998-03-12 8:22 ` H.J. Lu [this message]
1998-03-13 18:29 ` Manfred Hollstein
1998-03-14 4:14 ` Alexandre Oliva
1998-03-16 20:04 ` Jeffrey A Law
1998-03-16 11:20 ` libg++ (again) - patch and rationale included Manfred Hollstein
1998-03-16 10:27 ` H.J. Lu
1998-03-16 20:25 ` Jim Wilson
1998-03-16 20:25 ` H.J. Lu
1998-03-17 1:28 ` Manfred Hollstein
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=m0yDAk8-00058JC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=manfred@s-direktnet.de \
/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).