Re: 22.locale.codecvt.out test failure

[Martin Sebor]

Travis Vitek wrote:

The named test fails on all platforms with an EXEC error. It looks like
the problem is that when trying to build the executable
'22.locale.codecvt.out', it actually generates an output file for the
test '22.locale.codecvt', which is obviously not going to be executable.

  $ gmake 22.locale.codecvt.out
  gcc -c -I/amd/devco/vitek/stdcxx/trunk/include/ansi -D_RWSTDDEBUG
-I/amd/devco/vitek/stdcxx/trunk/include -I/build/vitek/5.0.0/11S/include
-I/amd/devco/vitek/stdcxx/trunk/tests/include  -pedantic -nostdinc++ -g
-W -Wall -Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long
-Wcast-align
/amd/devco/vitek/stdcxx/trunk/tests/localization/22.locale.codecvt.cpp
  gcc 22.locale.codecvt.o -o 22.locale.codecvt
-L/build/vitek/5.0.0/11S/rwtest -lrwtest11S

-L/build/vitek/5.0.0/11S/lib -lstd11S -lsupc++ -lm LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/build/vitek/5.0.0/11S/lib

./22.locale.codecvt >22.locale.codecvt.out 2>&1

I know this worked at one time because I was involved in the discussion
for fixing this problem the last time it came up
[http://tinyurl.com/5nv7qx].

Any ideas why this problem is back to haunt us?

There are two tests with similar names:

    22.locale.codecvt and 22.locale.codecvt.out

I suspect that when 22.locale.codecvt runs, its output is redirected
to 22.locale.codecvt.out. If this is true, we might want to change
the exec utility (which does the redirection) to send the output of
tests somewhere else.

Martin