public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: karipid@mae.cornell.edu (Daniel Karipides)
To: egcs@cygnus.com
Subject: pre-build advice
Date: Mon, 04 May 1998 18:07:00 -0000	[thread overview]
Message-ID: <199805042050.QAA06242@scotch.mae.cornell.edu> (raw)

I'm looking for a little advice before I build the latest snapshot
of egcs.  I'm worried that a little of the information in the FAQ
and other places may be a little out of date, so I thought I would
ask here.

I will be building egcs on three system types:

- Pentium II, 300Mz, running Linux RedHat 5.0 (not sure what the
  config.guess will be here...)
- mips-sgi-irix5.3
- mips-sgi-irix6.2

My questions:

(1) For linux, I plan to use glibc 2.0.6 ... is this what people
    would recommend?

(2) Also for linux, what version of binutils should I use?  I've
    seen people recommend 2.8.1.0.23 and 2.9.  Does the 2.9 version
    work with glibc2?  Or should I use 2.8.1.0.23 that H.J. Lu
    mentioned in a previous message?

(3) For the SGI's, would people recommend using gas for 5.3?  I know
    that gas _should not_ be used for 6.2.  I assume I should get
    the latest binutils (2.9) so that I have ranlib.

(4) Given that gdb-4.1.7 is out, is there any reasons not to use
    DWARF2 debugging information; i.e., configure with the --with-stabs
    option, for example?

and perhaps an ignorant question:

(5) If I build glibc2, binutils, etc with an old version of cc (on SGI)
    or gcc (on linux), do I need to rebuild them once I get egcs
    compiled?  Explicitly, do I have to:

    -build binutils, etc with old compiler
    -build egcs
    -build binutils, etc with egcs
    -build egcs using egcs built with the new binutils, etc.

   I can't see what this would do for me, but I want to be sure.

Thanks in advance,

-Dan
----
karipid@mae.cornell.edu

             reply	other threads:[~1998-05-04 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-04 18:07 Daniel Karipides [this message]
1998-05-05 13:33 ` H.J. Lu
1998-05-05 16:32 ` Horst von Brand
1998-05-06  2:02 ` Jim Wilson
1998-05-07 16:19   ` Alexandre Oliva
1998-05-08 15:42   ` Gerald Pfeifer
1998-05-09 23:12     ` Jeffrey A Law
1998-05-10 11:10       ` David Edelsohn
1998-05-10 20:57         ` Jeffrey A 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=199805042050.QAA06242@scotch.mae.cornell.edu \
    --to=karipid@mae.cornell.edu \
    --cc=egcs@cygnus.com \
    /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).