From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com, manjo@austin.ibm.com
Subject: Re: gdb build using different compiler
Date: Tue, 09 Mar 2004 20:09:00 -0000 [thread overview]
Message-ID: <404E2479.6050609@gnu.org> (raw)
In-Reply-To: <20040309185341.8027B4B104@berman.michael-chastain.com>
> Hi Manoj,
>
>
>>> How do I build gdb 6.1 using a compiler in /opt/tools/gcc instead of
>>> /usr/bin/gcc?
>
>
> Put /opt/tools/gcc/bin in your $PATH variable in front of /usr/bin.
>
> PATH=/opt/tools/gcc/bin:$PATH
> export PATH
FYI, a possibly better way is:
( CC=/opt/tools/gcc/bin/gcc ; export CC ; CXX=/opt/tools/gcc/bin/c++ ;
export CXX ; ..../configure )
This has the benefit(?) of hard-wiring CC and CXX into the Makefile and
hence making the build immune to changes in your path.
BTW, for testing the magic is more weird:
make check RUNTESTFLAGS='CC_FOR_TARGET=/../cc CXX_FOR_TARGET=/../c++'
I think they should default to CC/CXX, but I've no idea where/why that
isn't happening :-/
Andrew
> Then do this to make sure you're getting the gcc you want:
>
> gcc --version
>
> You might have to tweak "/opt/tools/gcc/bin" to get the result you want.
>
> That's all there is to it!
>
next prev parent reply other threads:[~2004-03-09 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 18:53 Michael Elizabeth Chastain
2004-03-09 20:09 ` Andrew Cagney [this message]
2004-03-09 21:50 ` Andreas Schwab
2004-03-09 20:43 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2004-03-09 17:54 Manoj Iyer
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=404E2479.6050609@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.com \
--cc=mec.gnu@mindspring.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