This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Fix testing libstdc++-v3 with multilibs
- From: Phil Edwards <phil at jaj dot com>
- To: Nick Clifton <nickc at cambridge dot redhat dot com>
- Cc: dosreis at cmla dot ens-cachan dot fr, drepper at redhat dot com, pme at gcc dot gnu dot org, bkoz at redhat dot com, gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Wed, 29 May 2002 15:50:56 -0400
- Subject: Re: Fix testing libstdc++-v3 with multilibs
- References: <m37klo9qsm.fsf@north-pole.nickc.cambridge.redhat.com> <20020528142714.A10652@disaster.basement.lan> <m3lma372ls.fsf@north-pole.nickc.cambridge.redhat.com>
On Wed, May 29, 2002 at 09:57:51AM +0100, Nick Clifton wrote:
> > Will "file delete" be okay the first time through, when the gluefile
> > doesn't exist?
>
> Yup - it is like doing "rm -f" except that it will work over a remote
> link.
Okay, cool. I've managed to forget nearly all the Tcl I've ever learned.
> > I'd forgotten about gluefile.o, but my subconscious made me write that
> > second paragraph. :-) Do you think this library could make gluefile
> > requirements easier to maintain?
>
> I doubt it - but then it should not make them harder either. The
> gluefile is (or should be) just a simple wrapper to catch abort, exit
> and main. It could be archived in your libv3test.a, which might
> simplify the linker's command line but other than that I doubt if it
> will have any impact on your change.
Okay. I've checked in that patch, so if it comes in handy, all good.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams