public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it>
To: egcs@cygnus.com
Subject: Re: Install instructions + dejagnu suggestion
Date: Mon, 01 Dec 1997 07:38:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.971201155236.31747A-100000@argon.roma2.infn.it> (raw)
In-Reply-To: <10126.880986687@hurl.cygnus.com>

On Mon, 1 Dec 1997, Jeffrey A Law wrote:

> 
>   In message < Pine.LNX.3.96.971201093807.17181A-100000@argon.roma2.infn.it >you 
> write:
>   > Now, at first the egcs thing: I think the instructions should contain some
>   > hint to the 
>   > 	--program-prefix
>   > configure option, which could be useful to those who would like to have
>   > both GNU gcc and egcs available (and was noted in some message in the
>   > mailing list).
> We're recommending using --prefix and a few symlinks.  It avoids problems
> with g++ header file conflicts.  See the faq.
> 
I'll try to post the dejagnu question to the right guys... And then, as
always, I forgot to write ALL what was in my mind... On my own system,
I'll do both a --prefix=/usr/local (yes, I use linux, and have gcc as the
default compiler) and a --program-prefix, to be able to call the compiler
I want from the command line, and avoid problems from different $PATH
values (sometime you have /usr/local/bin:..., some other you get
...:/usr/local/bin) I think this is more sensible than what I told, and
still useful... Only problem I envision is that I'll need to configure
--with-cc=... and so on if I want to compile with egcs.

Yours,


lorenzo




      reply	other threads:[~1997-12-01  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-01  1:28 Lorenzo M. Catucci
1997-12-01  7:38 ` Jeffrey A Law
1997-12-01  7:38   ` Lorenzo M. Catucci [this message]

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.3.96.971201155236.31747A-100000@argon.roma2.infn.it \
    --to=lorenzo@argon.roma2.infn.it \
    --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).