From: Alexandre Petit-Bianco <apbianco@cygnus.com>
To: "Anthony Green" <green@redhat.com>
Cc: <rhug-rhats@sources.redhat.com>
Subject: Re: Jython dependencies...
Date: Fri, 19 Oct 2001 16:30:00 -0000 [thread overview]
Message-ID: <15312.46970.217609.225728@fencer.cygnus.com> (raw)
In-Reply-To: <000201c1578a$997e9e40$5be6b4cd@cygnus.com>
Anthony Green writes:
> Hmm... if you link lib-org-jython.la with -l-javax-servlet and
> -l-org-apache-oro and -l-org-gnu-readline, then there should be no
> need to put these in your dependencies list. Does lib-org-jython.la
> really refer to classes in these libraries? If so you'll need to
> modify lib_org_jython_la_LIBADD and then have lib-org-jython.la in
> your dependencies for the test programs. Things break pretty badly
> otherwise.
That's what I did. I'm about to check in the bits to let jython
build. But there's much work to do (see jython/TODO.)
One mystery is that this morning, my build yields to a test_jython
which core all the time. I just rebuilt with -static (and a re-build
of bhoem-gc sans -O) and I got the following stack trace:
xception in thread "main" java.lang.NullPointerException
at 0x080f8044: _Jv_ThrowSignal (/home/apbianco/src/egcs-devel/libjava/prims.cc:119)
at 0x080f8067: catch_segv(int) (/home/apbianco/src/egcs-devel/libjava/prims.cc:128)
at 0xbfffeb54: ?? (??:0)
at 0x0807000a: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x080da494: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x080da3ca: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x0808992f: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x08089597: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x08089262: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x080482d8: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x0817fccb: gnu.gcj.runtime.FirstThread.call_main() (/home/apbianco/src/egcs-devel/libjava/gnu/gcj/runtime/natFirstThread.cc:47)
at 0x08154028: gnu.gcj.runtime.FirstThread.run() (/home/apbianco/src/egcs-devel/libjava/gnu/gcj/runtime/FirstThread.java:55)
at 0x081163ae: _Jv_ThreadRun(java.lang.Thread) (/home/apbianco/src/egcs-devel/libjava/java/lang/natThread.cc:285)
at 0x080f967a: _Jv_RunMain(java.lang.Class, byte const, int, byte const, boolean) (/home/apbianco/src/egcs-devel/libjava/prims.cc:1025)
at 0x080f979f: JvRunMain (/home/apbianco/src/egcs-devel/libjava/prims.cc:1035)
at 0x0804822d: ?? (/usr/src/bs/BUILD/glibc-2.2.1/csu/init.c:0)
at 0x081c69ba: __libc_start_main (/usr/src/bs/BUILD/glibc-2.2.1/csu/../sysdeps/generic/libc-start.c:129)
at 0x08048101: _start (??:0)
Strange. test_SimpleEmbeddd works thoug. When I get this fixed, I'll
work on the make check.
./A
next prev parent reply other threads:[~2001-10-19 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 17:39 Alexandre Petit-Bianco
2001-10-17 18:30 ` Anthony Green
2001-10-17 18:42 ` Alexandre Petit-Bianco
2001-10-17 18:53 ` Tom Tromey
2001-10-17 19:03 ` Alexandre Petit-Bianco
2001-10-17 21:03 ` Anthony Green
2001-10-17 22:04 ` Alexandre Petit-Bianco
2001-10-19 16:30 ` Alexandre Petit-Bianco [this message]
2001-10-20 11:14 ` Tom Tromey
2001-10-20 21:57 ` Alexandre Petit-Bianco
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=15312.46970.217609.225728@fencer.cygnus.com \
--to=apbianco@cygnus.com \
--cc=green@redhat.com \
--cc=rhug-rhats@sources.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).