From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: ADAM Sulmicki <adam@cfar.umd.edu>
Cc: gcc-help@gcc.gnu.org
Subject: Re: building latest ( snapshot || cvs )
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <ord7pj1i2z.fsf@garnize.lsd.ic.unicamp.br> (raw)
Message-ID: <20000401000000.MgM63HX0IfQua2MoZajbzxJwjNf4qoF6OAQtmJGm8fg@z> (raw)
In-Reply-To: <Pine.SOL.3.95.1000226213249.19569Q-100000@chia.umiacs.umd.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
On Feb 26, 2000, ADAM Sulmicki <adam@cfar.umd.edu> wrote:
>> > I guess it is something wrong with 'configure' and HAVE_SYS_RESOURCE_H
>>
>> > This or other way, I have manually defined RUSAGE_CHILDREN to be -1
>> > and included declaration of struct 'rusage' and it comiled past it.
>>
>> It looks more like some conflict between glibc and the kernel headers
>> you're using.
> Is there some easy way to find out for sure?
Sure, just revert the link to the original kernel headers and try to
compile again.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Enjoy Guaraná
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-26 9:14 ADAM Sulmicki
2000-02-26 17:54 ` ADAM Sulmicki
2000-02-26 18:18 ` Alexandre Oliva
2000-02-26 18:33 ` ADAM Sulmicki
2000-02-26 18:43 ` Alexandre Oliva [this message]
2000-02-26 19:07 ` ADAM Sulmicki
2000-04-01 0:00 ` ADAM Sulmicki
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` ADAM Sulmicki
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` ADAM Sulmicki
2000-04-01 0:00 ` ADAM Sulmicki
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=ord7pj1i2z.fsf@garnize.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=adam@cfar.umd.edu \
--cc=gcc-help@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).