public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	michael.tung@uv.es, nobody@gcc.gnu.org
Subject: Re: bootstrap/4856: RUSAGE/PRUSAGE Compile Error with gcc-3.0.2 Source
Date: Thu, 01 Nov 2001 18:19:00 -0000	[thread overview]
Message-ID: <20011113040916.23991.qmail@sourceware.cygnus.com> (raw)

Synopsis: RUSAGE/PRUSAGE Compile Error with gcc-3.0.2 Source

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Mon Nov 12 20:09:16 2001
State-Changed-Why:
    Could you provide?
    
    (1)  What Linux distribution are you running?  What version?
    (2)  What version of glibc?
    (3)  Do you have a file on your system /usr/include/bits/resource.h
         or /usr/include/sys/resource.h which defines RUSAGE_CHILDREN?
    (3)  In the gcc directory, there should be a file
         config.cache which is created.   Are there some lines
    in that file that looks like:
    ac_cv_header_sys_resource_h=
    ac_cv_func_getrusage=
    
    What values are on those lines?
    
    Thanks.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4856&database=gcc


             reply	other threads:[~2001-11-13  4:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 18:19 rodrigc [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
2002-01-17 21:46 Craig Rodrigues
2001-11-16  9:07 rodrigc
2001-11-01 19:36 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=20011113040916.23991.qmail@sourceware.cygnus.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=michael.tung@uv.es \
    --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: 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).