From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Dumaresq <Andrew.Dumaresq@stmarys.ca>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problem building GCC
Date: Fri, 03 Nov 2000 18:51:00 -0000 [thread overview]
Message-ID: <orwvekbgch.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3A01B914.2FA1F323@stmarys.ca>
On Nov 2, 2000, Andrew Dumaresq <Andrew.Dumaresq@stmarys.ca> wrote:
> I am using Tru64 Unix and using the default
> make and utils for that OS.
You failed to mention it was Tru64 5.0, which is not supported by GCC
2.95.2. I heard there are patches floating around that fix this minor
problem, but I don't know whether there are any more significant
changes needed.
If someone collects the patches and send them to gcc-patches, I'd be
glad to add them to the system-specific installation notes.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-11-03 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 10:59 Andrew Dumaresq
2000-11-03 18:51 ` Alexandre Oliva [this message]
2008-08-28 13:28 problem building gcc collinr
2008-08-28 13:42 ` Brian Dessent
2010-05-06 5:40 Problem " Pavel Pavlov
2010-05-06 6:02 ` Pavel Pavlov
2010-05-06 6:16 ` Ian Lance Taylor
2010-05-06 6:40 ` Pavel Pavlov
2010-05-07 19:03 ` Ralf Wildenhues
2010-05-07 23:04 ` Pavel Pavlov
2011-11-30 8:35 gideon425.gb5
2011-11-30 8:58 ` Marc Glisse
2011-12-19 18:45 ` Abdul Wahid Memon
2011-12-19 21:21 ` Ian Lance Taylor
2011-12-20 2:25 ` Abdul Wahid Memon
2011-12-20 5:07 ` Ian Lance Taylor
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=orwvekbgch.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=Andrew.Dumaresq@stmarys.ca \
--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).