From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31363 invoked by alias); 21 Apr 2004 16:12:16 -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 31328 invoked from network); 21 Apr 2004 16:12:14 -0000 Received: from unknown (HELO blount.mail.mindspring.net) (207.69.200.226) by sources.redhat.com with SMTP; 21 Apr 2004 16:12:14 -0000 Received: from user-uive91t.dsl.mindspring.com ([165.247.36.61] helo=sevencardstud.cable.nu) by blount.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BGKKY-0000a2-00; Wed, 21 Apr 2004 12:12:11 -0400 From: Frank Krauss To: llewelly@xmission.com Subject: Re: Error during "make bootstrap" during GCC 3.3 Creation Date: Wed, 21 Apr 2004 16:12:00 -0000 User-Agent: KMail/1.5.2 Cc: gcc-help@gcc.gnu.org References: <200404170830.00230.fmfkrauss@mindspring.com> <200404201933.36112.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: <200404211208.54335.fmfkrauss@mindspring.com> X-SW-Source: 2004-04/txt/msg00276.txt.bz2 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. Yours truly, Frank +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On Tuesday 20 April 2004 23:17, llewelly@xmission.com wrote: > Frank Krauss writes: > > I guess I will try tomorrow to do the upgrade in the exact same order as > > I did it on my other System. > > 1. First upgrade GCC from egcs-2.91.66 to 3.0.4 > > 2. Then upgrade GCC to 3.3 > > This is (more or less) what I was going to suggest next. I hope this > works for you.