This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: migchain 0.8, migbat 0.8 available
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 23 Dec 2003 14:08:00 -0500
- Subject: Re: migchain 0.8, migbat 0.8 available
- References: <200312231837.hBNIbFV7002589@duracef.shout.net>
On Tue, Dec 23, 2003 at 01:37:15PM -0500, Michael Elizabeth Chastain wrote:
> Here is a new releases of Migchain and Migbat.
>
> 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
>
> These are all the scripts that I use to run my test bed. Migchain is a
> set of scripts to download and build a standard Gnu toolchain. Migbat
> is a set of scripts to download, build, test, and crunch results for
> various configurations of gdb. Both are GPL software.
>
> New in this release: Migchain supports native hppa2.0w-hp-hpux11.11.
> I have work in progress for Migbat to support this platform, too.
> I'm also working on:
>
> native hppa2.0w-hp-hpux11.00
> -- thanks to Dave A for machine access
> native alphaev7-dec-osf5.1
> native ia64-hp-hpux11.22
> native ia64-hp-hpux11.23
>
> There are two big obstacles in hpux development. (1) The HP test
> drive cluster went down on 2003-12-22. (2) The gdb test suite is
> gcc-centric. I can't even figure out how to run the test suite
> with /opt/ansic/bin/cc instead of using default [find_gcc].
Ask :)
The very easiest way is to create a gcc->cc symlink and put it in the
front of your path. Or you can edit dejagnu's unix.exp to say
set_board_info compiler "blah/cc";
set_board_info c++compiler "blah/aCC";
There are a handful of other ways but they get more complex.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer