Re: [PATCH/RFC] Get Alpha target to GDB_MULTI_ARCH_PARTIAL

[Daniel Jacobowitz <drow at mvista dot com>]

On Sat, Apr 20, 2002 at 01:31:34PM -0700, Jason R Thorpe wrote:
> On Sat, Apr 20, 2002 at 09:54:36AM -0700, Jason R Thorpe wrote:
> 
>  >                 === gdb Summary ===
>  > 
>  > # of expected passes            6595
>  > # of unexpected failures        945
>  > # of unexpected successes       4
>  > # of expected failures          143
>  > # of unresolved testcases       118
>  > # of untested testcases         6
>  > # of unsupported tests          3
>  > 
>  > I would really like to know what the test results are on Digital Unix
>  > or Linux (I can't easily install either of those on any of my Alpha
>  > systems, unfortunately).
> 
> FWIW, a very large number of my failures go away when I make sure the
> testsuite uses gcc-current rather than the 2.95.3 that's currently shipped
> with NetBSD.  (Lots of the failures are off-by-one in line numbers.)

<sigh> I was able to work around this for i386, but apparently for
Alpha (and PowerPC also, I think; maybe more) the bug was somewhat more
complicated.

> Is there a way besides placing the location of the alternate compiler
> first in the PATH to make sure the correct compiler is chosen?

Set c-compiler and c++-compiler in a board description file (and any
others you care about).  You can do this by:
  Copying dejagnu/baseboards/unix.exp to a new name in the same
directory
  Edit the copy
  Run the testsuite as '$path/runtest --target_board your-board' or
with RUNTESTFLAGS="--target_board your-board" if you use make check.

Note that you've got to run the copy of DejaGNU in the source
distribution for that to work... or install the baseboard in the global
dejagnu config directory off under /usr/share somewhere.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer