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, 23 May 2001 12:26:00 -0000	[thread overview]
Message-ID: <20010523192605.4452.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: Benjamin Kosnik <bkoz@redhat.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/2841
Date: Wed, 23 May 2001 18:50:32 +0200 (MEST)

 Benjamin Kosnik writes:
 
 > have you tried CVS/branch gcc to see if setting ld_library_path works for 
 > you?
 
 I'm not sure what you mean here?  I didn't have to set ld_library_path
 (either in the dejagnu testsuite or LD_LIBRARY_PATH in the environment) at
 all to have the make check to succeed.  In fact, I've just verified (by
 running the first compilation in libstdc++-v3.log manually) that the shared
 libgcc_s.so.0 is used in fact, and if I just try to run the resulting
 ./header_cassert in the shell, it fails since it cannot find that library
 (I don't have an installed gcc 3.0 yet, so the only place that library can
 be found is in the build tree.)  So at least that part of the testsuite
 change works as expected.  I'll learn about the rest (i.e. finding
 libstdc++.so.3) when I've bootstrapped and checked the other platforms
 where building shared libraries do work.
 
 	Rainer
 
 -----------------------------------------------------------------------------
 Rainer Orth, Faculty of Technology, Bielefeld University
 
 Email: ro@TechFak.Uni-Bielefeld.DE


             reply	other threads:[~2001-05-23 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23 12:26 Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-06  5:06 libstdc++/2841 Rainer Orth
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  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=20010523192605.4452.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: link
Be 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).