dejagnu
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[DejaGnu] Re: integrating with libgloss: finding baseboards


From: Rob Savoye
Subject: [DejaGnu] Re: integrating with libgloss: finding baseboards
Date: Sat, 12 May 2001 07:26:02 -0600

On Sat, May 12, 2001 at 01:34:40AM -0700, Benjamin Kosnik wrote:

> I'm having problems finding the correct baseboard (or even looking for
> it) for a libgloss-type cross compiler. I've got the sid-based

  Do the tests run native at all ? What's in libstdc++-v3/testsuite/config ?
That's where your tool-and-target-specific interface file should be. If it's
not found, default.exp gets loaded, which currently only works for native
tests. Is DEJAGNU pointing to your global site.exp file ? Ifd you add "-v"
to RUNTESTFLAGS, you can see what tool files it's trying to load, and
where from. That's how I usually debug these things.

> Running target unix
> Using /mnt/hd/ahimsa/H-x86-src/share/dejagnu/baseboards/unix.exp as board 
> description file for target.
> Using /mnt/hd/ahimsa/H-x86-src/share/dejagnu/config/unix.exp as generic 
> interface file for target.
> Using 
> /mnt/hd/bliss/src.calmrisc32-010108-branch/libstdc++-v3/testsuite/config/default.exp
>  as tool-and-target-specific interface file.
> WARNING: Assuming target board is the local machine (which is probably wrong).
> You may need to set your DEJAGNU environment variable.
> Running 
> /mnt/hd/bliss/src.calmrisc32-010108-branch/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp
>  ...
> Executing on host: ulimit -d 16384   (timeout = 300)
> spawn ulimit -d 16384 
> Executing on host: ulimit -v 16384   (timeout = 300)
> spawn ulimit -v 16384 
> 
> Which is obviously wrong, just by the schedule of variations.

  Hum... I'd really need to wander through your sources to see what the
problem is. It's not obvious from this.

        - rob -



reply via email to

[Prev in Thread] Current Thread [Next in Thread]