From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2613 invoked by alias); 19 Apr 2004 17:14:36 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 2604 invoked from network); 19 Apr 2004 17:14:35 -0000 Received: from unknown (HELO hall.mail.mindspring.net) (207.69.200.60) by sources.redhat.com with SMTP; 19 Apr 2004 17:14:35 -0000 Received: from user-uive84h.dsl.mindspring.com ([165.247.32.145] helo=sevencardstud.cable.nu) by hall.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BFcLn-0007JI-00; Mon, 19 Apr 2004 13:14:32 -0400 From: Frank Krauss To: llewelly@xmission.com Subject: Re: Error during "make bootstrap" during GCC 3.3 Creation Date: Mon, 19 Apr 2004 17:14:00 -0000 User-Agent: KMail/1.5.2 Cc: gcc-help@gcc.gnu.org References: <200404170830.00230.fmfkrauss@mindspring.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404191311.30687.fmfkrauss@mindspring.com> X-SW-Source: 2004-04/txt/msg00250.txt.bz2 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 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]