Re: none

[Joern Rennecke <amylaar at cygnus dot co dot uk>]

> 
>   In message <oru36c2pju.fsf@zecarneiro.lsd.dcc.unicamp.br>you write:
>   > > Is there some reason to use TESTSUITE_TMPDIR over TMPDIR?
>   > 
>   > Yes.  I already have TMPDIR set to /tmp, which is usually mounted on
>   > virtual memory (tmpfs); this is very fast for compiling files.
>   > However, I wanted to be able to run simultaneous tests of egcs, with
>   > different configuration flags (--{dis,en}able-haifa, for example), but
>   > using a single TMPDIR caused name clashes in files created by
>   > dejagnu.  Furthermore, I'd like failed binaries to be kept for further 
>   > analysis, so I didn't want them to be stored in /tmp.
>   > 
>   > So I came up with a solution that would keep gcc using TMPDIR for its
>   > temporaries, for speed, and would allow me to specify different
>   > directories for each run of dejagnu.  Perhaps the patch should use
>   > TMPDIR if TESTSUITE_TMPDIR is not set:
> Ah.  In that case, maybe the right way to go is to put temporary
> files in the testsuite object directory itself since you'd have
> different testsuite object directories for the different configs
> right?

No, this doesn't work when you want to run different tests from the
same (e.g. multilibbed) directory.