Re: egcs testsuite & dejagnu : A special case?

[Carlo Wood <carlo at runaway dot xs4all dot nl>]

| this need in the form of an interface exported by gcc.  If problems
| like this arise, it's because external products that already use
| built-not-installed versions of gcc have the same problems *now*, or
| they solve it somehow, in which case the solutions should be removed
| from those products to the implementations of these new interfaces.

The way dejagnu `solves' this is as follows:
It picks a foobar.cc file and collects all the gcc parameters it
needs to compile it (the -B, -L etc).  From that it determines
where the libstdc++ resides that apparently is wanted (from a
-L.*stdc++/).  It remembers this path in a variable, compiles the
program and then sets explicitly the LD_LIBRARY_PATH environment
variable to this path before executing the test program.
If you hide the -L paths from dejagnu, it won't be able anymore
to determine where the wanted libstdc++ is and thus it won't be
able to set the LD_LIBRARY_PATH environment variable.


-- 
 Carlo Wood  <carlo@runaway.xs4all.nl>