From: Manfred Hollstein <manfred@s-direktnet.de>
To: law@cygnus.com
Cc: hjl@lucon.org, egcs@cygnus.com, Manfred.Hollstein@ks.sel.alcatel.de
Subject: Re: libg++ (again)
Date: Fri, 13 Mar 1998 18:29:00 -0000 [thread overview]
Message-ID: <13576.55644.732642.790993@slsvhmt> (raw)
In-Reply-To: <m0yDAk8-00058JC@ocean.lucon.org>
On Thu, 12 March 1998, 08:22:04, hjl@lucon.org wrote:
> >
> > 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.
>
As H.J. tried this several times now with no luck, perhaps it might
help to tell you, this patch is _really necessary_ and _fixes a real
bug_ in the configure mechanism.
I've used it since several months (and yes, even while building in
srcdir and even with multilibs, too ;-) without any problems - it's
really safe to be put into the release and the main trunk.
Just my 2 cents...
manfred
next prev parent reply other threads:[~1998-03-13 18:29 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
1998-03-13 18:29 ` Manfred Hollstein [this message]
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=13576.55644.732642.790993@slsvhmt \
--to=manfred@s-direktnet.de \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=law@cygnus.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).