This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/2841
- To: bkoz at gcc dot gnu dot org
- Subject: Re: libstdc++/2841
- From: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
- Date: 6 Jun 2001 12:06:03 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
The following reply was made to PR libstdc++/2841; it has been noted by GNATS.
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bkoz@gcc.gnu.org
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Subject: Re: libstdc++/2841
Date: Wed, 6 Jun 2001 14:00:36 +0200 (MEST)
bkoz@gcc.gnu.org writes:
> Synopsis: -static in libstdc++ v3 dejagnu testsuite causes linking to fail
>
> State-Changed-From-To: feedback->closed
> State-Changed-By: bkoz
> State-Changed-When: Tue Jun 5 18:31:09 2001
> State-Changed-Why:
> I'd like to fix this, as I believe the original problem is fixed. There are lingering bugs in the testsuite, but I'd appreciate it if you'd open new CR's for them...
Part of is, yes. But as Kaveh Ghazi reported in
http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00261.html
you still get unexpected behaviour since you need to run make check for
non-default multilibs manually in
$(top_builddir)/$(multilibsubdir)/libstdc++-v3, just invoking make check
with the appropriate RUNTESTFLAGS (either e.g. --tool_opts '-mabi=64' or
--target_board "unix{-mabi=64}") will still (seem to) fail, since that is
run in $(top_builddir)/libstdc++-v3, thus finding the wrong libstdc++-v3
dir.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE