From: "T.J. Mather" <tjmather@maxmind.com>
To: "H. Kemal Gürsoy" <hkgursoy@SoftHome.net>
Cc: <rhug-rhats@sources.redhat.com>
Subject: Re: gnu.readline compile problem
Date: Wed, 10 Jul 2002 16:26:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0207102012510.7435-100000@knut.anidea.com> (raw)
In-Reply-To: <20020711022401.I17310@localhost>
Hi,
I ran into the same problem and was able to fix it by appending ":." to
the classpath in Makefile.am. I checked in the change, so it should be there
if you do a cvs update:
Here's the patch:
===================================================================
RCS file: /cvs/rhug/rhug/gnu.readline/Makefile.am,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Makefile.am 29 May 2002 06:27:39 -0000 1.8
+++ Makefile.am 9 Jul 2002 03:10:54 -0000 1.9
@@ -107,7 +107,7 @@
# There's probably a cleaner generic way to handle this situation
org_gnu_readline_Readline.h: $(lib_org_gnu_readline_la_DEPENDENCIES)
- $(GCJH) --classpath=upstream/src -jni `echo $(lib_org_gnu_readline_la_DEPENDENCIES) | sed 's/\.class//g'` -o $@
+ $(GCJH) --classpath=upstream/src:. -jni `echo $(lib_org_gnu_readline_la_DEPENDENCIES) | sed 's/\.class//g'` -o $@
./upstream/src/native/org_gnu_readline_Readline.c: org_gnu_readline_Readline.h
# Building the tests
-TJ
http://maxmind.com
On Thu, 11 Jul 2002, [iso-8859-9] H. Kemal Gürsoy wrote:
<snip>
>
> the compilation stops just at the beginnig with the following message :
>
> gcjh --classpath=upstream/src -jni 'echo
> upstream/src/org/gnu/readline/Readline.class | sed 's/\.class//g'' -o
> org_gnu_readline_ReadLine.h
> upstream/src/org/gnu/readline/ReadLine: no such class
> make: *** [org_gnu_readline_ReadLine.h] Error 1
next prev parent reply other threads:[~2002-07-10 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 16:20 H. Kemal Gürsoy
2002-07-10 16:26 ` T.J. Mather [this message]
2002-07-11 6:53 ` Anthony Green
2002-07-11 11:14 H. Kemal Gürsoy
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=Pine.LNX.4.33.0207102012510.7435-100000@knut.anidea.com \
--to=tjmather@maxmind.com \
--cc=hkgursoy@SoftHome.net \
--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).