From: Frank Krauss <fmfkrauss@mindspring.com>
To: gcc-help@gcc.gnu.org
Subject: Error during "make bootstrap" during GCC 3.3 Creation
Date: Sun, 18 Apr 2004 23:33:00 -0000 [thread overview]
Message-ID: <200404181930.36840.fmfkrauss@mindspring.com> (raw)
In-Reply-To: <200404181431.28046.fmfkrauss@mindspring.com>
On Sunday 18 April 2004 14:31, Frank Krauss wrote:
> Hello Jack,
>
> Thank you very much for responding to my Problem.
>
> The reason I don't believe that I should comment out this statement is as
> follows:
>
> 1. Back in 5/02, I had upgraded another computer I have from egcs-2.91.66
> to GCC 3.0.4.
> 2. Then, in 6/03, I upgraded that system to GCC 3.3.
> 3. It had the same Distribution, Caldera 2.3, and the same Kernel, 2.4.22,
> as my new Computer has.
> These updates all went fine.
>
> I therefore believe that this upgrade should be valid also.
>
> In trying to debug this problem, I have noticed a difference between the
> output of the "configure" step on these two Systems.
> 1. On the Good update, "getrlimit", "setrlimit" and "getrusage"
> were all declared as "yes".
> 2. On the Bad update, these three entries are all declared as "no".
>
> I'm hoping that this information may be a pointer to someone in the GCC
> area who will be able to tell me what the error is and how I can correct
> it.
>
> Again, thank you for your effort in trying to solve this problem.
>
> If I get a solution, I will be glad to pass it along to you.
>
> Yours truly,
>
> Frank
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> On Saturday 17 April 2004 09:37, Jack Liddle wrote:
> > On Sat, 17 Apr 2004, Frank Krauss wrote:
> > > Good day,
> > >
> > > While attempting to update my GCC to the 3.3 Level,
> > > during the "make bootstrap" step, it failed with the following
> > > messages:
> > >
> > > ../../gcc/ggc-common.c: In function `ggc_rlimit_bound':
> > > ../../gcc/ggc-common.c:294: storage size of `rlim' isn't known
> > > ../../gcc/ggc-common.c:294: warning: unused variable `rlim'
> >
> > I'm no expert but could you comment out line 294 if the variable isn't
> > being used.
> >
> > Jack Liddle
next prev parent reply other threads:[~2004-04-18 23:33 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 [this message]
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
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=200404181930.36840.fmfkrauss@mindspring.com \
--to=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).