public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org, piotr.wozniak@cs.put.poznan.pl Subject: Re: c++/9340: compiling port /usr/ports/databases/postgresql7 failed Date: Wed, 26 Mar 2003 07:06:00 -0000 [thread overview] Message-ID: <20030326070151.11447.qmail@sources.redhat.com> (raw) Synopsis: compiling port /usr/ports/databases/postgresql7 failed Responsible-Changed-From-To: unassigned->ljrittle Responsible-Changed-By: ljrittle Responsible-Changed-When: Wed Mar 26 07:01:51 2003 Responsible-Changed-Why: Mine. Reassigned severity for obvious reasons. State-Changed-From-To: feedback->closed State-Changed-By: ljrittle State-Changed-When: Wed Mar 26 07:01:51 2003 State-Changed-Why: No additional feedback from the PR submitter. There are two major issues here: (1) This report is likely for gcc as installed as the system compiler. Normally, I will attempt to reproduce the error against the FSF tree however this is still a baking arch for FreeBSD and I rarely have I been able to obtain a stable build from the FSF tree; (2) In general, we are unwilling to look at complex "ports" that don't build. At the FSF/gcc-end of things, we need self-contained test cases. We look at those, I promise. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9340
next reply other threads:[~2003-03-26 7:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-26 7:06 ljrittle [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-16 15:16 bangerth 2003-01-16 10:46 piotr.wozniak
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=20030326070151.11447.qmail@sources.redhat.com \ --to=ljrittle@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=piotr.wozniak@cs.put.poznan.pl \ /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).