From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb@sources.redhat.com, manjo@austin.ibm.com
Subject: Re: testsuite questions.
Date: Sat, 24 Apr 2004 00:03:00 -0000 [thread overview]
Message-ID: <20040423221533.42E884B104@berman.michael-chastain.com> (raw)
> 1. Is there any enviroment variable that I can set to make the testcase
> use my custom GDB, for instance the one in /usr/local/bin/gdb?
I do this by setting $PATH.
BTW, if you build your software "--prefix=...", you don't even need root
access on the box. No need to touch /usr/local/bin.
> 2. Is there any enviroment variable I can use to control the value of
> these variables?
I do this by setting $PATH. Yup, I have a little shim directory,
with a script in it named "gcc" that just calls the real compiler
that I want with the options I want. Ewww, it's gross! But it
gets my testing done.
If I just want to adjust the version of gcc that I use, I just
make sure that I've configured that version of gcc using a
convenient "--prefix=/.../.../..." option, and that I've actually
installed that version of gcc. There's lots of code in dejagnu
to test built-but-not-installed yet gcc trees, but it doesn't
help me any.
> The intention is to disconnect the testsuite from using the system
> utilities and GDB that gets built, but use the testcase to test a
> different binary of GDB that I have in a separate local/system directory.
$PATH works really well for selecting the gdb to run.
> Any input is greatly appreciated.
You might wanna look at:
ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.8.tar.gz
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.8.tar.gz
http://www.shout.net/~mec/sunday/current/index.html
Michael C
next reply other threads:[~2004-04-23 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 0:03 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-23 18:15 Manoj Iyer
2004-04-24 0:03 ` 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=20040423221533.42E884B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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