From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Richard Henderson <rth@redhat.com>, GCC <gcc@gcc.gnu.org>
Subject: Re: [ada] help debugging acats failure
Date: Mon, 07 Sep 2009 01:15:00 -0000 [thread overview]
Message-ID: <4AA4605D.2020701@gmail.com> (raw)
In-Reply-To: <84fc9c000909040247s71e4ebe1p48aff5ad60ac5e2@mail.gmail.com>
Richard Guenther wrote:
> On Fri, Sep 4, 2009 at 1:00 AM, Richard Henderson<rth@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
next prev parent reply other threads:[~2009-09-07 1:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A9F1A8D.5080501@redhat.com>
2009-09-03 23:00 ` Richard Henderson
2009-09-04 1:34 ` Dave Korn
2009-09-04 2:24 ` Geert Bosch
2009-09-04 6:44 ` Arnaud Charlet
2009-09-04 9:47 ` Richard Guenther
2009-09-07 1:15 ` Dave Korn [this message]
2009-09-04 9:51 ` Eric Botcazou
2009-09-05 16:11 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AA4605D.2020701@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).