* Error during "make bootstrap" during GCC 3.3 Creation
@ 2004-04-17 12:32 Frank Krauss
2004-04-17 13:37 ` Jack Liddle
2004-04-19 2:48 ` llewelly
0 siblings, 2 replies; 11+ messages in thread
From: Frank Krauss @ 2004-04-17 12:32 UTC (permalink / raw)
To: gcc-help
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'
When I searched on Google, I came across a mention of the exact same
problem in the GNU GCC Mailing list Archive, number gcc03062512, dated
6/25/03, from Joseph Lien.
I never saw any mention of the solution of the problem.
Would someone be kind enough to tell me how I can resolve this problem?
My environment is the following:
Computer - Pentium II
O/S - Linux
Distribution - Caldera 2.3
Kernel - 2.4.22
GCC being executed - egcs-2.91.66
GCC being created - 3.3
GLIBC - libc.so.6
Binutils - 2.12
Modutils - 2.4.15
Util-linux - 2.11q
Any assistance you can give me so that I can solve this problem will
be greatly appreciated.
Yours truly,
Frank Krauss
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Error during "make bootstrap" during GCC 3.3 Creation
2004-04-17 12:32 Error during "make bootstrap" during GCC 3.3 Creation Frank Krauss
@ 2004-04-17 13:37 ` Jack Liddle
2004-04-18 18:34 ` Frank Krauss
2004-04-19 2:48 ` llewelly
1 sibling, 1 reply; 11+ messages in thread
From: Jack Liddle @ 2004-04-17 13:37 UTC (permalink / raw)
To: Frank Krauss; +Cc: gcc-help
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Error during "make bootstrap" during GCC 3.3 Creation
2004-04-17 13:37 ` Jack Liddle
@ 2004-04-18 18:34 ` Frank Krauss
2004-04-18 23:33 ` Frank Krauss
0 siblings, 1 reply; 11+ messages in thread
From: Frank Krauss @ 2004-04-18 18:34 UTC (permalink / raw)
To: Jack Liddle; +Cc: gcc-help
Hello Jack,
Thank you very much for responding to my Problem.
The reason I don't believe that I should comment out thie 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 declard 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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Error during "make bootstrap" during GCC 3.3 Creation
2004-04-18 18:34 ` Frank Krauss
@ 2004-04-18 23:33 ` Frank Krauss
0 siblings, 0 replies; 11+ messages in thread
From: Frank Krauss @ 2004-04-18 23:33 UTC (permalink / raw)
To: gcc-help
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Error during "make bootstrap" during GCC 3.3 Creation
2004-04-17 12:32 Error during "make bootstrap" during GCC 3.3 Creation Frank Krauss
2004-04-17 13:37 ` Jack Liddle
@ 2004-04-19 2:48 ` llewelly
2004-04-19 17:14 ` Frank Krauss
1 sibling, 1 reply; 11+ messages in thread
From: llewelly @ 2004-04-19 2:48 UTC (permalink / raw)
To: Frank Krauss; +Cc: gcc-help
Frank Krauss <fmfkrauss@mindspring.com> writes:
> 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'
Maybe the host/target specific notes are useful? See:
http://gcc.gnu.org/install/specific.html#*-*-linux-gnu
>
> When I searched on Google, I came across a mention of the exact same
> problem in the GNU GCC Mailing list Archive, number gcc03062512, dated
> 6/25/03, from Joseph Lien.
>
> I never saw any mention of the solution of the problem.
>
> Would someone be kind enough to tell me how I can resolve this problem?
>
> My environment is the following:
> Computer - Pentium II
> O/S - Linux
> Distribution - Caldera 2.3
> Kernel - 2.4.22
> GCC being executed - egcs-2.91.66
> GCC being created - 3.3
> GLIBC - libc.so.6
'libc.so.6' covers many many versions of glibc. Including some (such
as glibc 2.2.5 and earlier) which do not work well with gcc 3.3,
but also later glibcs which work fine with gcc 3.3 .
Could you post the output of 'ls -l /lib/*libc*' ?
> Binutils - 2.12
Binutils 2.13.1 or later is required for gcc 3.3 . See the link I
posted earlier.
> Modutils - 2.4.15
> Util-linux - 2.11q
[snip]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Error during "make bootstrap" during GCC 3.3 Creation
2004-04-19 2:48 ` llewelly
@ 2004-04-19 17:14 ` Frank Krauss
2004-04-19 21:14 ` llewelly
0 siblings, 1 reply; 11+ messages in thread
From: Frank Krauss @ 2004-04-19 17:14 UTC (permalink / raw)
To: llewelly; +Cc: gcc-help
Thank you for looking into my Problem.
1. Your 100% correct about the Binutils being at the wrong Level.
I somehow missed seeing that in the Pre-req section and I will look into
updating that.
2. I believe that my problem is actually caused by your 2nd suggestion
concerning the level of GLIBC that I'm using.
I didn't see any mention of a need for a specific version of GLIBC.
3. In other words, do I have to update my GLIBC to a specific level
before updating GCC? I was under the impression that it was
supposed to be done the opposite way, with first GCC getting updated
and then using it to update GLIBC.
4. Would you know of any doc available to show the correct procedure
on updating these two Components?
I have enclosed the listing of my /lib/*libc* as you requested.
Thanks again for your assistance.
Frank
output of "ls -l /lib/*libc*"
-rwxr-xr-x 1 root root 1245005 Aug 10 1999 /lib/libc-2.1.1.so
lrwxrwxrwx 1 root root 14 Mar 28 03:25 /lib/libc.so.5 ->
libc.so.5.4.38
-r-xr-xr-x 1 root root 580288 Jan 7 1998 /lib/libc.so.5.4.38
lrwxrwxrwx 1 root root 13 Mar 28 03:26 /lib/libc.so.6 ->
libc-2.1.1.so
lrwxrwxrwx 1 root root 17 Mar 28 03:38 /lib/libcom_err.so.2 ->
libcom_err.so.2.0
-rwxr-xr-x 1 root root 7606 Aug 10 1999 /lib/libcom_err.so.2.0
-rwxr-xr-x 1 root root 25471 Aug 10 1999 /lib/libcrypt-2.1.1.so
lrwxrwxrwx 1 root root 17 Mar 28 03:26 /lib/libcrypt.so.1 ->
libcrypt-2.1.1.so
/lib/gnulibc1:
total 2788
lrwxrwxrwx 1 root root 14 Mar 28 03:40 libc.so.5 ->
libc.so.5.4.46
-r-xr-xr-x 1 root root 1824167 Mar 2 1999 libc.so.5.4.46
lrwxrwxrwx 1 root root 17 Mar 28 03:40 libcom_err.so.2 ->
libcom_err.so.2.0
-rwxr-xr-x 1 root root 5999 Mar 2 1999 libcom_err.so.2.0
lrwxrwxrwx 1 root root 14 Mar 28 03:40 libdl.so.1 ->
libdl.so.1.9.9
-rwxr-xr-x 1 root root 5796 Mar 2 1999 libdl.so.1.9.9
lrwxrwxrwx 1 root root 13 Mar 28 03:40 libe2p.so.2 ->
libe2p.so.2.3
-rwxr-xr-x 1 root root 11696 Mar 2 1999 libe2p.so.2.3
lrwxrwxrwx 1 root root 16 Mar 28 03:40 libext2fs.so.2 ->
libext2fs.so.2.4
-rwxr-xr-x 1 root root 81968 Mar 2 1999 libext2fs.so.2.4
-r-xr-xr-x 1 root root 51400 Mar 2 1999 libiberty.so.1.0
lrwxrwxrwx 1 root root 13 Mar 28 03:40 libm.so.5 ->
libm.so.5.0.9
-r-xr-xr-x 1 root root 75329 Mar 2 1999 libm.so.5.0.9
lrwxrwxrwx 1 root root 17 Mar 28 03:40 libncurses.so.4 ->
libncurses.so.4.1
-rwxr-xr-x 1 root root 274155 Mar 2 1999 libncurses.so.4.1
lrwxrwxrwx 1 root root 14 Mar 28 03:40 libpam.so.0 ->
libpam.so.0.58
-rw-r--r-- 1 root root 97274 Mar 2 1999 libpam.so.0.58
lrwxrwxrwx 1 root root 19 Mar 28 03:40 libpam_misc.so.0 ->
libpam_misc.so.0.58
-rw-r--r-- 1 root root 26420 Mar 2 1999 libpam_misc.so.0.58
lrwxrwxrwx 1 root root 15 Mar 28 03:40 libpwdb.so.0 ->
libpwdb.so.0.54
-rw-r--r-- 1 root root 336763 Mar 2 1999 libpwdb.so.0.54
lrwxrwxrwx 1 root root 12 Mar 28 03:40 libss.so.2 ->
libss.so.2.0
-rwxr-xr-x 1 root root 18364 Mar 2 1999 libss.so.2.0
lrwxrwxrwx 1 root root 19 Mar 28 03:40 libtermcap.so.2 ->
libtermcap.so.2.0.8
-rwxr-xr-x 1 root root 12565 Mar 2 1999 libtermcap.so.2.0.8
lrwxrwxrwx 1 root root 14 Mar 28 03:40 libuuid.so.1 ->
libuuid.so.1.1
-rwxr-xr-x 1 root root 7751 Mar 2 1999 libuuid.so.1.1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On Sunday 18 April 2004 22:48, llewelly@xmission.com wrote:
> Frank Krauss <fmfkrauss@mindspring.com> writes:
> > 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'
>
> Maybe the host/target specific notes are useful? See:
> http://gcc.gnu.org/install/specific.html#*-*-linux-gnu
>
> > When I searched on Google, I came across a mention of the exact same
> > problem in the GNU GCC Mailing list Archive, number gcc03062512, dated
> > 6/25/03, from Joseph Lien.
> >
> > I never saw any mention of the solution of the problem.
> >
> > Would someone be kind enough to tell me how I can resolve this problem?
> >
> > My environment is the following:
> > Computer - Pentium II
> > O/S - Linux
> > Distribution - Caldera 2.3
> > Kernel - 2.4.22
> > GCC being executed - egcs-2.91.66
> > GCC being created - 3.3
> > GLIBC - libc.so.6
>
> 'libc.so.6' covers many many versions of glibc. Including some (such
> as glibc 2.2.5 and earlier) which do not work well with gcc 3.3,
> but also later glibcs which work fine with gcc 3.3 .
>
> Could you post the output of 'ls -l /lib/*libc*' ?
>
> > Binutils - 2.12
>
> Binutils 2.13.1 or later is required for gcc 3.3 . See the link I
> posted earlier.
>
> > Modutils - 2.4.15
> > Util-linux - 2.11q
>
> [snip]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Error during "make bootstrap" during GCC 3.3 Creation
2004-04-19 17:14 ` Frank Krauss
@ 2004-04-19 21:14 ` llewelly
[not found] ` <200404192032.03563.fmfkrauss@mindspring.com>
0 siblings, 1 reply; 11+ messages in thread
From: llewelly @ 2004-04-19 21:14 UTC (permalink / raw)
To: Frank Krauss; +Cc: gcc-help
Frank Krauss <fmfkrauss@mindspring.com> writes:
> Thank you for looking into my Problem.
>
> 1. Your 100% correct about the Binutils being at the wrong Level.
> I somehow missed seeing that in the Pre-req section and I will look into
> updating that.
See: http://xrl.us/bwvk , and also, www.gnu.org/software/binutils .
Questions about binutils go to binutils at sources.redhat.com
> 2. I believe that my problem is actually caused by your 2nd suggestion
> concerning the level of GLIBC that I'm using.
> I didn't see any mention of a need for a specific version of
> GLIBC.
I don't either. I was sure there was one when I wrote my last post,
but now I think I was mistaken. I *do* know some additional
libstdc++ testcase failures occur with glibc < 2.2.5, but that
shouldn't prevent a bootstrap.
>
> 3. In other words, do I have to update my GLIBC to a specific level
> before updating GCC? I was under the impression that it was
> supposed to be done the opposite way, with first GCC getting updated
> and then using it to update GLIBC.
It depends on circumstance. I don't know all of the details.
>
> 4. Would you know of any doc available to show the correct procedure
> on updating these two Components?
>
> I have enclosed the listing of my /lib/*libc* as you requested.
>
> Thanks again for your assistance.
>
> Frank
>
> output of "ls -l /lib/*libc*"
>
> -rwxr-xr-x 1 root root 1245005 Aug 10 1999
> /lib/libc-2.1.1.so
[snip]
2.1.1 is a very old libc. Unfortunately, upgrading libc from sources
is difficult and error-prone. (It's not for the faint of heart,
it's not for people who don't have full system backups, and it's
not for people who don't have sstaticly linked copies of essential
tools in strategic places. Nor is it for people without rescue
disks and spare install CDs.)
Normally one upgrades libc with linux-distro-supplied packages. You'll
have to see your distro implementor for those.
Since libc is so difficult to upgrade, I suggest you try upgrading
binutils first, and hope that solves your problem.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2004-04-21 17:02 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-17 12:32 Error during "make bootstrap" during GCC 3.3 Creation 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 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).