public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/10508: libstdc++ from gcc 3.2.3 failed to boostrap on OpenBSD 3.2 Date: Fri, 16 May 2003 23:36:00 -0000 [thread overview] Message-ID: <20030516233601.5067.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/10508; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: gcc-gnats@gcc.gnu.org, bkoz@gcc.gnu.org Cc: Subject: Re: libstdc++/10508: libstdc++ from gcc 3.2.3 failed to boostrap on OpenBSD 3.2 Date: Fri, 16 May 2003 16:28:39 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=10508 Uhm, separate srcdir and objdir are mentioned, but not _required_. As my post on gcc mailing list last week indicated, we either need to support this, or not. Note that I have seen no problems with 3.3 yet when doing this. Dara
next reply other threads:[~2003-05-16 23:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 23:36 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-17 0:06 Dara Hazeghi 2003-05-16 23:46 Benjamin Kosnik 2003-05-16 20:15 bkoz 2003-04-26 17:36 tim
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=20030516233601.5067.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --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).