Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>, Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: Changing the C/C++ compiler for gdb testsuite runs
Date: Thu, 10 Jan 2002 11:10:00 -0000	[thread overview]
Message-ID: <1020110190932.ZM5067@localhost.localdomain> (raw)
In-Reply-To: Michael Elizabeth Chastain <mec@shout.net> "Re: Changing the C/C++ compiler for gdb testsuite runs" (Jan 10, 10:58am)

On Jan 10, 10:58am, Michael Elizabeth Chastain wrote:

> If you build gcc and gdb in a unified build tree then dejagnu will find
> and use the uninstalled compiler in the unified build tree, even in
> preference to $PATH.  That behaviour actually got in my way so I stopped
> using unified trees.

Here's one way to use a different compiler in a unified tree...

    1) In gdb/testsuite (in your build directory), do

	    make site.exp

    2) Add lines similar to the following to the end of
       gdb/testsuite/site.exp:
       
	    set CC_FOR_TARGET "/some/other/path/to/gcc"
	    set CXX_FOR_TARGET "/some/other/path/to/g++"

If anyone knows of other (more elegant) tricks that can be used to
accomplish the same thing, I'd like to hear about them...

Kevin


  reply	other threads:[~2002-01-10 19:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  8:58 Michael Elizabeth Chastain
2002-01-10 11:10 ` Kevin Buettner [this message]
2002-01-10 11:30   ` Daniel Jacobowitz
2002-01-15 10:24     ` Daniel Jacobowitz
2002-01-15 11:18       ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2002-01-11  8:07 Michael Elizabeth Chastain
2002-01-10  5:46 Richard Earnshaw
2002-01-10 17:30 ` Michael Snyder
2002-01-11  2:23   ` Richard Earnshaw
2002-01-11  7:26     ` Andrew Cagney
2002-01-11  7:38       ` Richard Earnshaw
2002-01-11  7:45         ` Andrew Cagney

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=1020110190932.ZM5067@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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