This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC 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: Tue, 28 May 2002 14:27:14 -0400
- Subject: Re: Fix testing libstdc++-v3 with multilibs
- References: <m37klo9qsm.fsf@north-pole.nickc.cambridge.redhat.com>
On Tue, May 28, 2002 at 05:32:25PM +0100, Nick Clifton wrote:
> The patch below fixes this problem by making libstdc++-v3-init
> rebuild the file every time it is called (if a wrapper is needed, of
> course). Since this function is called once per multilib testing,
> this works.
>
> May I apply this patch please ?
Looks safe to me. (BTW, it's usually easier and better to just mail
libstdc++ rather than each of the maintainers individually.)
Will "file delete" be okay the first time through, when the gluefile
doesn't exist?
A question: I plan to check in the testsuite-library patch described in
http://gcc.gnu.org/ml/libstdc++/2002-05/msg00295.html
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? Either way, would you be willing to test
that patch on your multilibbed target?
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