[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: trouble getting kissme to work with gcp
From: |
Giannis Georgalis |
Subject: |
Re: trouble getting kissme to work with gcp |
Date: |
31 Aug 2002 00:07:06 +0300 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 |
Stephen Crawley <address@hidden> writes:
Hello Stephen,
> Giannis,
>
> First, this email would be better directed to the kissme mailing list:
>
> address@hidden
>
> I've cc'ed that list. If you reply to this email, please remove
> address@hidden from the cc: list.
I sent it to the classpath group, because I want to contribute to GNU
classpath. I was advised by cbj to setup a development environment by
making GNU classpath work with kissme. Anyway, I found what was wrong and
I'm cc'ing to gnu-classpath mailing list also just to close this thread.
(sorry Stephen).
> Your best bet for getting Kissme to work is to read the kissme/docs/
> BUILDING file carefully, and follow the instructions therein. I've
> also included some hints below.
I've done this (of-course, I'm an RTFM believer :)). The solution seems
to me very strange though.
> It is not necessary to give "--with-java=kissme" or "--with-classpath"
> when configuring Classpath. I'd remove them because they >>might<<
> cause problems.
>
> We (the kissme developers) haven't put any of the kissme-specific java
> code into the Classpath tree. The Classpath build and install process
> doesn't need to know anything about Kissme.
Well I've tried ALL possible configure combinations ... that was the latest
version :). I could understand they were uneeded, but I was desperate.
> That makes sense. Your effective classpath should look like this:
>
> .../kissme/classes.zip:.../glibj.jar:..../kissme
>
> i.e. classes.zip file MUST be before glibj.jar in the effective classpath.
Yes, that's what I meant; my CLASSPATH was right from the beggining.
> It looks like the kissme jvm is not picking up the Classpath shared
> libraries.
> You probably need to add the directory wher the libs are installed to
> the LD_LIBRARY_PATH environment variable.
Ok, now this is *very* strange. I thought that was the last thing I had to look,
as I had put right from the beggining in "/etc/ld.so.conf" the path of the
GNU classpath libraries. Everything seemed right as "ldconfig -v" would say:
<snip>
/home/jgeorgal/JDE/lib/classpath:
libgtkpeer.so.0 -> libgtkpeer.so.0.0.0
libjavautil.so.0 -> libjavautil.so.0.0.0
libjavanet.so.0 -> libjavanet.so.0.0.0
libjavalangreflect.so.0 -> libjavalangreflect.so.0.0.0
libjavalang.so.0 -> libjavalang.so.0.0.0
libjavaio.so.0 -> libjavaio.so.0.0.0
<snip>
...so no need for LD_LIBRARY_PATH (I thought). In fact setting LD_LIBRARY_PATH
to /path/to/lib/classpath, made ALL my problems disappear...
Well, it can't be ldconfig's fault as I had not any problems before.
Can it be kissme's problem?
anyway,
Thank you very much Stephen and John for your help,
Giannis
--
Let him choose out of my files, his projects to accomplish.
-- Shakespeare, "Coriolanus"