public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Karcz <jsk29@cornell.edu>
To: egcs@cygnus.com
Subject: Binutils
Date: Fri, 06 Feb 1998 17:06:00 -0000	[thread overview]
Message-ID: <199802062325.SAA22279@localhost> (raw)

Please excuse me if the answer to this is obvious,
but I haven't been able to figure it out from info
pages, install files, etc.

From my limited abilty to read make/configure files,
it seems that it's possible to put a directory for
Binutils under the, say, egcs-1.0.1 source directory,
and have configure also configure ar, ld, etc, and use
them in building targets.  My question is this:  What
should the directory tree look like?  Should I just
put the binutils-2.8.1.0.19 under the root egcs directory,
and rename it binutils?  Or should I somehow redistribute 
the various files and directories from binutils-2.8.1.0.19/
into the egcs root directory?

I hope the question was clear... Thanks for the help!
John

             reply	other threads:[~1998-02-06 17:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-06 17:06 John Karcz [this message]
1998-02-07  1:06 ` Binutils Jeffrey A Law
1999-09-12 16:10 Binutils Bruce M Beach
1999-09-12 22:03 ` Binutils Alex Buell
1999-09-30 18:02   ` Binutils Alex Buell
1999-09-30 18:02 ` Binutils Bruce M Beach
2001-06-18  8:12 Binutils Mathieu Chouinard
     [not found] <md5:679D2BAAB79B012F46C5D7BC9D8A4E84>
2001-06-18  9:01 ` Binutils Paolo Carlini
     [not found] <200106181556.LAA06106@one-point.com>
2001-06-19  5:47 ` Binutils Jeff Sturm
2001-06-19 15:13   ` Binutils Philip Blundell
2001-06-19 19:25     ` Binutils Jeff Sturm
2001-06-19 23:35       ` Binutils Philip Blundell
2001-06-20  4:40       ` Binutils Benoît Sibaud
2001-06-20 14:32       ` Binutils Alexandre Oliva
2002-01-14  2:33 binutils Earl Healey
2002-01-14  2:43 ` binutils Craig Rodrigues
2003-01-27 18:38 Binutils Diego Morales
2003-01-28  5:43 ` Binutils Ben Elliston

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=199802062325.SAA22279@localhost \
    --to=jsk29@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).