From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5614 invoked by alias); 25 Jan 2011 10:59:26 -0000 Received: (qmail 5604 invoked by uid 22791); 25 Jan 2011 10:59:25 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from wmh1.mail.saunalahti.fi (HELO wmh1.mail.saunalahti.fi) (62.142.5.133) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 25 Jan 2011 10:59:20 +0000 Received: from [192.168.1.3] (dsl-olubrasgw1-fe15f900-207.dhcp.inet.fi [84.249.21.207]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: kai.ruottu@wippies.com) by wmh1.mail.saunalahti.fi (Postfix) with ESMTPSA id F30081FC08A for ; Tue, 25 Jan 2011 12:59:16 +0200 (EET) Message-ID: <4D3EAD02.7090004@wippies.com> Date: Tue, 25 Jan 2011 10:59:00 -0000 From: Kai Ruottu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fi; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines References: <4D36F9D6.5020400@web.de> <4D36FCFC.1000907@acri-st.fr> <4D37089F.50700@web.de> <4D371361.9010609@web.de> <4D3713C3.2040705@redhat.com> <4D371A80.4020604@web.de> <4D371B3E.1090905@redhat.com> <4D37457B.2020003@web.de> <4D375CB5.4010602@caviumnetworks.com> <4D383EFF.1040503@web.de> <4D386FB7.1010407@web.de> <4D3EA686.4090806@web.de> In-Reply-To: <4D3EA686.4090806@web.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-01/txt/msg00357.txt.bz2 25.1.2011 12:31, Olumide kirjoitti: > On 20/01/2011 17:24, Olumide wrote: >> Good news. >> >> Build was successful -- I think, here's the log file http://goo.gl/SnKsP >> >> (I had to compiled and install textinfo version 4.9 and install the >> latest version ncurses in order to compile texinfo.) IMHO getting the 'info' docs nowadays isn't in any way important, but getting PDF-format manuals would be. Years ago I manually did them using 'pdftex' on some old RHL7.3 or 8.0 but whether that would succeed somehow nowadays is unclear :( Maybe I'm living in a totally different planet when needing (printable when needed) PDF docs for everything... > I would like to roll out the build to other machines (several dozen > actually). If I remember right, the goal was to get "plugins" for some AutoDesk (Maya?) system which was made on/for RHEL4 which had gcc-4.1.2 as its "system GCC". So the ultimate goal would be a (cross) "toolchain for RHEL4 target with gcc-4.1.2". But the original RHEL4 glibc etc. target libs are not freely available, so what on earth to do? - try the "native" glibc etc. in the own development platform? or - build a crosstoolchain with gcc-4.1.2 and with some freely available "very near" RHL4 target libraries like some CentOS ones? (Which ones for this case? CentOS5.x has gcc-4.1.2 and glibc-2.5 that I know...) I myself would choose the latter and then produce the crosstoolchain once, as "self-hosting" - built for the virtual "RHL4" host with the "stage1" GCC built first using the native GCC on the development platform. And then make a tarball for this "gcc-4.1.2 for RHEL4" and install it onto all those several dozen platforms...