From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manfred Hollstein 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 Message-id: <13576.55644.732642.790993@slsvhmt> References: <13575.33474.833614.662788@slsvhmt> X-SW-Source: 1998-03/msg00504.html 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