From: llewelly@xmission.com
To: Frank Krauss <fmfkrauss@mindspring.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error during "make bootstrap" during GCC 3.3 Creation
Date: Wed, 21 Apr 2004 17:02:00 -0000 [thread overview]
Message-ID: <s3rsmexs1qe.fsf@xmission.xmission.com> (raw)
In-Reply-To: <200404211208.54335.fmfkrauss@mindspring.com>
Frank Krauss <fmfkrauss@mindspring.com> writes:
> Hello everyone,
>
> Before doing what I mentioned here I did some more research on the
> differences between my two Systems.
> I found that the entry HAVE_SYS_RESOURCE_H was missing from the
> confdefs.h file that is created during the configure step.
>
> I found a mention on the Net about this problem being caused by a
> duplicated defination for RLIM_INFINITY between the GLIBC and
> Kernel Headers.
>
> The suggestion was to remove the defination of this from
> /usr/src/linux/include/asm/resource.h
>
> I did this and after running "configure" I found that the entry for
> HAVE_SYS_RESOURCE_H is now in the confdefs.h file.
> I now started the "make bootstrap" over and it has been running now
> successfully for 1/2 Hour so far.
>
> It looks like this may have been the answer to my problem all along.
>
> Thank you all very much for the effort you gave to help me solve this problem.
> Especially thank you "llewelly" for your ideas.
Glad you were able to solve the problem. I never would have known
about the HAVE_SYS_RESOURCE_H issue.
prev parent reply other threads:[~2004-04-21 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 12:32 Frank Krauss
2004-04-17 13:37 ` Jack Liddle
2004-04-18 18:34 ` Frank Krauss
2004-04-18 23:33 ` Frank Krauss
2004-04-19 2:48 ` llewelly
2004-04-19 17:14 ` Frank Krauss
2004-04-19 21:14 ` llewelly
[not found] ` <200404192032.03563.fmfkrauss@mindspring.com>
2004-04-20 23:36 ` Frank Krauss
2004-04-21 3:17 ` llewelly
2004-04-21 16:12 ` Frank Krauss
2004-04-21 17:02 ` llewelly [this message]
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=s3rsmexs1qe.fsf@xmission.xmission.com \
--to=llewelly@xmission.com \
--cc=fmfkrauss@mindspring.com \
--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).