From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines
Date: Tue, 25 Jan 2011 10:59:00 -0000 [thread overview]
Message-ID: <4D3EAD02.7090004@wippies.com> (raw)
In-Reply-To: <4D3EA686.4090806@web.de>
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...
next prev parent reply other threads:[~2011-01-25 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 14:48 Olumide
2011-01-19 15:01 ` Cedric Roux
2011-01-19 15:51 ` Olumide
2011-01-19 16:21 ` Ian Lance Taylor
2011-01-19 16:37 ` Olumide
2011-01-19 16:39 ` Andrew Haley
2011-01-19 17:08 ` Olumide
2011-01-19 17:11 ` Andrew Haley
2011-01-19 20:13 ` Olumide
2011-01-19 21:51 ` David Daney
2011-01-20 13:56 ` Olumide
2011-01-20 17:23 ` Olumide
2011-01-20 20:04 ` Jonathan Wakely
2011-01-25 10:30 ` Olumide
2011-01-25 10:59 ` Jonathan Wakely
2011-01-25 11:34 ` Olumide
2011-01-25 11:56 ` Jonathan Wakely
2011-01-25 13:51 ` Olumide
2011-01-25 10:59 ` Kai Ruottu [this message]
2011-01-19 16:43 ` Cedric Roux
2011-01-19 16:47 ` Jonathan Wakely
2011-01-19 15:19 ` Jeff Law
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=4D3EAD02.7090004@wippies.com \
--to=kai.ruottu@wippies.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).