public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2841 Date: Wed, 06 Jun 2001 05:06:00 -0000 [thread overview] Message-ID: <20010606120603.5660.qmail@sourceware.cygnus.com> (raw) 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
next reply other threads:[~2001-06-06 5:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-06 5:06 Rainer Orth [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-05 18:36 libstdc++/2841 bkoz 2001-05-25 12:26 libstdc++/2841 Rainer Orth 2001-05-23 14:26 libstdc++/2841 Rainer Orth 2001-05-23 14:16 libstdc++/2841 Benjamin Kosnik 2001-05-23 12:26 libstdc++/2841 Rainer Orth 2001-05-23 12:26 libstdc++/2841 Rainer Orth 2001-05-23 9:46 libstdc++/2841 Benjamin Kosnik 2001-05-23 8:36 libstdc++/2841 Rainer Orth 2001-05-22 18:36 libstdc++/2841 bkoz 2001-05-22 17:46 libstdc++/2841 bkoz
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=20010606120603.5660.qmail@sourceware.cygnus.com \ --to=ro@techfak.uni-bielefeld.de \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ /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: linkBe 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).