public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/4856: RUSAGE/PRUSAGE Compile Error with gcc-3.0.2 Source Date: Thu, 17 Jan 2002 21:46:00 -0000 [thread overview] Message-ID: <20020118054601.12414.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/4856; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@mediaone.net> To: michael.tung@uv.es, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, Eric.Paulson@yale.edu, jonathanpaton@yahoo.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: bootstrap/4856: RUSAGE/PRUSAGE Compile Error with gcc-3.0.2 Source Date: Fri, 18 Jan 2002 00:41:46 -0500 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4856 ================================================================== PR 5392 has been marked as a duplicate of this bug: http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4856 Jonathan, can you provide your config.log and config.cache files from trying to build gcc 3.0.3 on Suse 6.2? The test for getrusage() seems to be broken on Suse 6.2...... -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@mediaone.net
next reply other threads:[~2002-01-18 5:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-17 21:46 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 8:56 Dara Hazeghi 2002-03-15 20:36 Craig Rodrigues 2002-01-27 17:46 Jonathan E. Paton 2002-01-27 17:37 rodrigc 2001-11-16 9:07 rodrigc 2001-11-01 19:36 rodrigc 2001-11-01 18:19 rodrigc 2001-11-01 11:46 michael.tung
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=20020118054601.12414.qmail@sources.redhat.com \ --to=rodrigc@mediaone.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).