Richard Guenther wrote:
> On Fri, Sep 4, 2009 at 1:00 AM, Richard Henderson<r...@redhat.com> wrote:
>> Can someone tell me how to debug this:
>>
>>> splitting
>>> /home/rth/work/gcc/bld-sjlj/gcc/testsuite/ada/acats0/tests/c3/c35502i.ada
>>> FAIL: c35502i
>> I haven't been able to figure out what command to issue from the command
>> line to reproduce this. Cut and paste from the dejagnu log doesn't work,
>> which is more than annoying...
>
> Same for libjava ...
To debug libjava tests, run the testsuite with about half-a-dozen -v
switches in your RUNTESTFLAGS and look through the output for lines that look
like:
> board is unix, not remote
> set_ld_library_path_env_vars:
> ld_library_path=.:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/./libjava/.libs
> LD_LIBRARY_PATH =
> .:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/./libjava/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libstdc++-v3/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libssp/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libgomp/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/./gcc:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/./prev-gcc:.:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/./libjava/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libstdc++-v3/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libssp/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libgomp/.libs:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/./gcc:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/./prev-gcc
> CLASSPATH is
> .:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/src/gcc-4.3.4/libjava/testsuite/libjava.lang:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libjava/testsuite:/gnu/gcc/releases/4.3.4-1/gcc4-4.3.4-1/build/i686-pc-cygwin/libjava/testsuite/../libgcj-4.3.4.jar
> board_info target needs_status_wrapper
Copy-paste those assignments to LD_LIBRARY_PATH and CLASSPATH into your
shell, export them both, and you can then cut and paste build commands from
the log and they'll work.
(Although note that I always install the compiler to a DESTDIR and put the
.../bin dir at the very front of my PATH, and that may be a necessary step, I
haven't tried it without yet. I do this to make completely sure that the
windows DLL search path algorithms pick up the newly-built DLLs; it might be
superfluous on other platforms.)
cheers,
DaveK
