public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Kramer <david@thekramers.net>
To: gcc-help@gcc.gnu.org
Subject: Re: how to combine gcc and binutils source into one tree
Date: Mon, 30 Aug 2004 18:28:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0408301339130.16746@uni.thekramers.net> (raw)
In-Reply-To: <2162.192.168.0.4.1093886737.squirrel@nautilus.tsunami.us>

On Mon, 30 Aug 2004 steve@millersnet.net wrote:

> ok that seems to be an easier way to handle things. I'm wondering which
> will work better when configuring gcc use --with-prefix=/opt/gcc-2.95.3
> and when configuring binutils use --with-prefix=/opt/binutils-2.15 this
> would keep everything contained to their own directories or gcc use
> --with-prefix=/opt/gnu and binutils use --with-prefix=/opt/gnu ..... would
> the latter work as well seeing how both gcc and binutils have common
> components?

Each package needs a different --with-prefix option.  That's the least 
risky way to do it.  You can settle any conflicts with your $PATH, and you 
can even try differernt gcc's with different binutil's that way.  Though 
doing
--with-prefix=/opt/gnu/gcc-2.95.3
--with-prefix=/opt/gnu/binutils-2.15
...
...

wouldn't be a bad idea, so you can just tar up /opt/gnu.


-- 
DDDD   
DK KD  
DKK D  Bush/Cheney '04: Putting the "Con" in Conservative
DK KD  
DDDD   

  reply	other threads:[~2004-08-30 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 17:42 steve
2004-08-30 18:28 ` David Kramer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-30 17:10 steve
2004-08-30 17:22 ` David Kramer
2004-08-30 16:19 steve
2004-08-30 16:52 ` Eljay Love-Jensen
2004-08-30 17:04 ` David Kramer
2004-08-26 16:05 steve

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=Pine.LNX.4.58.0408301339130.16746@uni.thekramers.net \
    --to=david@thekramers.net \
    --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).