public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2841 Date: Tue, 22 May 2001 17:46:00 -0000 [thread overview] Message-ID: <20010523004601.27889.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/2841; it has been noted by GNATS. From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, ro@TechFak.Uni-Bielefeld.DE Cc: Subject: Re: libstdc++/2841 Date: 23 May 2001 00:40:33 -0000 Synopsis: -static in libstdc++ v3 dejagnu testsuite causes linking to fail Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Tue May 22 17:40:33 2001 Responsible-Changed-Why: responsible State-Changed-From-To: open->analyzed State-Changed-By: bkoz State-Changed-When: Tue May 22 17:40:33 2001 State-Changed-Why: I'm taking this. Can you please send me a patch that includes your modifications for ld_library_path? Thanks this was a very clear bug report to understand. FYI to get shared libraries working/building, you'll have to do top-level work to the libtool cxx files (ltcf-cxx.sh) to add support for Tru64. Alexandre Oliva is a good person to talk to about this, as well as Loren James Rittle <rittle@latour.rsch.comm.mot.com>, who added support for BSD. thanks, benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2841&database=gcc
next reply other threads:[~2001-05-22 17:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-22 17:46 bkoz [this message] 2001-05-22 18:36 libstdc++/2841 bkoz 2001-05-23 8:36 libstdc++/2841 Rainer Orth 2001-05-23 9:46 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 14:16 libstdc++/2841 Benjamin Kosnik 2001-05-23 14:26 libstdc++/2841 Rainer Orth 2001-05-25 12:26 libstdc++/2841 Rainer Orth 2001-06-05 18:36 libstdc++/2841 bkoz 2001-06-06 5:06 libstdc++/2841 Rainer Orth
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=20010523004601.27889.qmail@sourceware.cygnus.com \ --to=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).