java-gnome-developer — For people using the bindings to write their own applications

RE: [Java-gnome-developer] Unsatisfied link error - Please help..

[Jeffrey M. <Jef...@Br...>]

The fix is in CVS now.  I will be generating a new
rpm within the next two hours.  

-Jeff

> -----Original Message-----
> From: Raj Kumar [mailto:cha...@ya...]
> Sent: Thursday, August 16, 2001 9:04 AM
> To: jav...@li...
> Subject: [Java-gnome-developer] Unsatisfied link error - Please help..
> 
> 
> Hi..
> 
> I downloaded this package and installed it on my
> computer (RH7.0 with JDK1.3.0_02)..
> 
> And when I'm trying to run the test propgram
> 'GnomeTest' I get the following error..
> 
> Exception in thread "main"
> java.lang.UnsatisfiedLinkError:
> /home/mobile/Rajit/java-gnome-0.6.1/test/libGTKJava.so:
> undefined symbol : gtk_ctree_get_row_data
>         at
> java.lang.ClassLoader$NativeLibrary.load(native
> Method)
>         at
> java.lang.ClassLoader.loadLibrary()(ClassLoader.java:1382)
>         at
> java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
>         at
> java.lang.Runtime.loadLibrary()(Runtime.java:749)
>         at
> java.lang.System.loadLibrary(System.java:820)
>         at GnomeTest.<clinit>(GnomeTest.java:16)
> 
> I'm sure I have gtk.jar and gnome.jar in myclasspath
> and I have libGTKJava.so and libGNOMEJava.so in my
> LD_LIBRARY_PATH env variable..
> 
> Immediate help would be greatly appreciated,
> Thanx in advance..
> regards,
> Rajit.
> 
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with 
> Yahoo! Messenger
> http://phonecard.yahoo.com/
> 
> _______________________________________________
> java-gnome-developer mailing list
> jav...@li...
> http://lists.sourceforge.net/lists/listinfo/java-gnome-developer
> 

[Java-gnome-developer] FAQ item #15 - Variable arguments

[Ryan G. <rya...@ho...>]

Hey all,

Just joined the list, reading over the documentation getting familar with 
things.  Considering looking into the gnome-postal app, we'll see.

Anyway, looking at the FAQ.  Not sure how dated it is.  But item #15, I had 
a general suggestion for enhancing the text, add the following:

--- start ---

In general, check the javadoc API to see if there is an overloaded method 
version that takes an array type.  If so, array constructor intialization 
allows you to use any number of parameters with very minor modifications to 
your code.  For example, instead of the GnomeMessageBox constructor:

   new GnomeMessageBox(message, messagebox_type,
         button1, button2, button3, button4);

You could use:

   new GnomeMessageBox(message, messagebox_type,
         new String[]{button1, button2, button3,
         button4});

--- end ---


This got me thinking.

I've not delved into the parser code, or the .defs files to examine how 
java-gnome deals with variable argument functions from Gnome/GTK, but one 
could define Java equivalents in you really wanted.

For example, given an argument list for gnome_message_box as taken from the 
.h on my system:

   GtkWidget* gnome_message_box_new(
         const gchar * message,
         const gchar * messagebox_type,
         ...);

But, this could be minimally generated as the constructor set:

   // Full vararg version
   GnomeMessageBox(String message,
         String messagebox_type, Object[] varargs);

   // Enumerated versions...
   GnomeMessageBox(String message,
         String messagebox_type, Object vararg1);

   GnomeMessageBox(String message,
         String messagebox_type, Object vararg1,
         Object vararg2);

   ...

And with proper hints in the .defs file, I suppose we could go even further 
and do it as:

   // Full vararg version
   GnomeMessageBox(String message,
         String messagebox_type, String[] buttons);

   // Enumerated versions, which are just wrappers
   // to call on full version.
   GnomeMessageBox(String message,
         String messagebox_type, String button1)
   {
      this(message, messagebox_type,
            new String[]{button1});
   }

   GnomeMessageBox(String message,
         String messagebox_type, String button1,
         String button2)
   {
      this(message, messagebox_type,
            new String[]{button1, button2});
   }

   ...

Where the hints we need for the variable arguments are:

   1) Type information.  For now, just assume an array of same typed objects 
to keep it simple.  For the above the hint would be "String".
   2) Suggested variable name.  Here we'd use "button".
   3) Maximum number of enumerated overloads.  Default to 10.

My preference is to keep the overloads short, maybe 2 or 3, anymore is 
bloat, use the array version in such cases.


Anyway, just some quick comments.  Sorry if this is a rehash of solved 
problems. =)

Later,
Ryan

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

[Java-gnome-developer] Unsatisfied link error - Please help..

[Raj K. <cha...@ya...>]

Hi..

I downloaded this package and installed it on my
computer (RH7.0 with JDK1.3.0_02)..

And when I'm trying to run the test propgram
'GnomeTest' I get the following error..

Exception in thread "main"
java.lang.UnsatisfiedLinkError:
/home/mobile/Rajit/java-gnome-0.6.1/test/libGTKJava.so:
undefined symbol : gtk_ctree_get_row_data
        at
java.lang.ClassLoader$NativeLibrary.load(native
Method)
        at
java.lang.ClassLoader.loadLibrary()(ClassLoader.java:1382)
        at
java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
        at
java.lang.Runtime.loadLibrary()(Runtime.java:749)
        at
java.lang.System.loadLibrary(System.java:820)
        at GnomeTest.<clinit>(GnomeTest.java:16)

I'm sure I have gtk.jar and gnome.jar in myclasspath
and I have libGTKJava.so and libGNOMEJava.so in my
LD_LIBRARY_PATH env variable..

Immediate help would be greatly appreciated,
Thanx in advance..
regards,
Rajit.

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

[Java-gnome-developer] Java-GNOME release 0.6.1

[Jeffrey M. <Jef...@Br...>]

I am pleased to announce the next release of the 
Java-GNOME bindings.  This release has focused
primarily on bug fixes and adding enhancements
to the class library.  Also, signal handling
and object creation have been enhanced to provide
greater stability.

Also with this release you will notice the inclusion
of two applications.  These applications have
been include to demonstrate the usage of
the bindings.  I am looking for developers to
take ownership of these applications and
possibly split them into separate projects
over time.  

The first application is CroMagnon.  CroMagnon
is a crontab editor that was originally 
written in C by Aldy Hernandez.  Thanks to
Aldy for letting us reimplement this app in Java.
The Java-GNOME version of CroMagnon uses
the glade files from the original project.
This application is far from complete and is
waiting for a developer to complete.  You
can see a screenshot on the Java-GNOME web site.

The second application is gnome-postal.  This
application is an IMAP email client.  It is
built upon the work of Jim Frost in his
"Java Class" series in the Server/Workstation
Expert magazine.  The original app written
in the series uses Swing and the JavaMail
API.  Jim was very gracious in allowing us
to add a Gnome user interface to his work.
In anybody is interested in learning how to
use the JavaMail API I would strongly recommend
this series.  Again, there is much work to 
complete on this application.  A screenshot 
is available on the Java-GNOME web site.

The 0.7 release of Java-GNOME will be 
delivered very shortly.  The new release
will provide support for native compilation
utilizing the gcj compiler.  

---
------------------------------------
Jeffrey S. Morgan
Email: jef...@br...

RE: [Java-gnome-developer] troubles compiling gnome-java

[Jeffrey M. <Jef...@Br...>]

There have been several requests to make this happen.  
My primary focus has been on making the bindings as
robust as possible in there present form.  Currently there
is an incredible shortage of development resources on
this project (I am currently the only developer working
on the project) and am not sure when I will get a chance
to address this request.

		-----Original Message-----
		From:	Damien [mailto:da...@ca...]
		Sent:	Wednesday, August 08, 2001 9:17 AM
		To:	jav...@li...
		Subject:	Re: [Java-gnome-developer] troubles
compiling gnome-java

		On 08 Aug 2001 12:46:57 +0100, Bastien Nocera wrote:
		> On 08 Aug 2001 13:11:02 +0200, Damien wrote:
		> > On 08 Aug 2001 11:56:41 +0100, Bastien Nocera wrote:
		> > > Hi,
		> > > 
		> > > I just wanted to try out Gnome-Java. After a bit of
hacking to get the
		> > > Makefiles to point to the right javac (they're
insisting that my javac
		> > > binary be in /usr/bin/javac or something like that), I
hit the wall when
		> > > it gets to compiling src/other/callback_dispatcher.c
		> <snip>
		> > > The piece of code if first chokes on is (at line 57):
		> > > JNIEXPORT jobject JNICALL
		> > > Java_Gtk_Object_get(JNIEnv *env, jobject obj, jstring
str)
		> > > {
		> > >     return NULL;
		> > > }
		> > > 
		> > > I'm using Sun's JDK Version 1.3.0 FCS for Linux, on a
Debian/x86
		> > > unstable system.
		> > > 
		> > > Any ideas ?
		> > > 
		> > > Cheers
		> > 
		> > Have you installed GCJ ?? because it's seem like Sun and
GCJ jni.h are
		> > conflicting. I had the same problem wich I resolve by
removing GCJ ...
		> 
		> Oh, yes I had, works much better now ;) Thanks a whole lot
		> 
		> Does any of you know if gnome-java a) is supposed to work
b) might be
		> working c) will never be working with gcj ?
		> 
		> Cheers
		> 
		> 
		There is one project: http://gnome-gcj.sourceforge.net , but
it seems to be in early development stage ...

		Dam


		_______________________________________________
		java-gnome-developer mailing list
		jav...@li...
	
http://lists.sourceforge.net/lists/listinfo/java-gnome-developer

Re: [Java-gnome-developer] troubles compiling gnome-java

[Damien <da...@ca...>]

On 08 Aug 2001 12:46:57 +0100, Bastien Nocera wrote:
> On 08 Aug 2001 13:11:02 +0200, Damien wrote:
> > On 08 Aug 2001 11:56:41 +0100, Bastien Nocera wrote:
> > > Hi,
> > > 
> > > I just wanted to try out Gnome-Java. After a bit of hacking to get the
> > > Makefiles to point to the right javac (they're insisting that my javac
> > > binary be in /usr/bin/javac or something like that), I hit the wall when
> > > it gets to compiling src/other/callback_dispatcher.c
> <snip>
> > > The piece of code if first chokes on is (at line 57):
> > > JNIEXPORT jobject JNICALL
> > > Java_Gtk_Object_get(JNIEnv *env, jobject obj, jstring str)
> > > {
> > >     return NULL;
> > > }
> > > 
> > > I'm using Sun's JDK Version 1.3.0 FCS for Linux, on a Debian/x86
> > > unstable system.
> > > 
> > > Any ideas ?
> > > 
> > > Cheers
> > 
> > Have you installed GCJ ?? because it's seem like Sun and GCJ jni.h are
> > conflicting. I had the same problem wich I resolve by removing GCJ ...
> 
> Oh, yes I had, works much better now ;) Thanks a whole lot
> 
> Does any of you know if gnome-java a) is supposed to work b) might be
> working c) will never be working with gcj ?
> 
> Cheers
> 
> 
There is one project: http://gnome-gcj.sourceforge.net , but it seems to be in early development stage ...

Dam

[Java-gnome-developer] Re: troubles compiling gnome-java

[Jeffrey M. <Jef...@Br...>]

Bastien,

Are you using the code from CVS or the downloaded code from 
the website. I would recommend using the code from CVS. There
have been numerous bug fixes since the last release. If you don't 
have access to CVS then make sure you remove the config.cache
file and then run configure again. It should find the correct javac. 
I haven't heard of the problem you are having with
callback_dispatcher. After you try getting the latest code please 
let me know if you are still having this problem. I would also
be interested in which JDK and which c compiler and version 
you are using.

-Jeff



---------------------------------------
Hi,

I just wanted to try out Gnome-Java. After a bit of hacking to get the
Makefiles to point to the right javac (they're insisting that my javac
binary be in /usr/bin/javac or something like that), I hit the wall when
it gets to compiling src/other/callback_dispatcher.c

gcc -c -g -O2 -fPIC -Iother other/callback_dispatcher.c -o
other/callback_dispatcher.o -I/usr/include/gtk-1.2
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include
-DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include \
-I/usr/include/gnome-xml -I/usr/include/gtk-1.2
-I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/local/jdk-1.3//include -DGNOME
other/callback_dispatcher.c:57: syntax error before `jobject'
other/callback_dispatcher.c: In function `Java_Gtk_Object_get':
other/callback_dispatcher.c:60: warning: return makes integer from
pointer without a cast
other/callback_dispatcher.c: At top level:
other/callback_dispatcher.c:68: syntax error before `void'
other/callback_dispatcher.c: In function `jobject_signal_cb':
other/callback_dispatcher.c:149: warning: assignment makes integer from
pointer without a cast
other/callback_dispatcher.c:171: warning: assignment makes pointer from
integer without a cast
other/callback_dispatcher.c:174: warning: assignment makes integer from
pointer without a cast
other/callback_dispatcher.c:180: warning: assignment makes integer from
pointer without a cast
other/callback_dispatcher.c: In function `jobject_arg_signature':
other/callback_dispatcher.c:292: warning: assignment discards qualifiers
from pointer target type
other/callback_dispatcher.c: At top level:
other/callback_dispatcher.c:544: syntax error before `jint'
other/callback_dispatcher.c:556: syntax error before `jint'
other/callback_dispatcher.c:569: syntax error before `jint'
other/callback_dispatcher.c:582: syntax error before `jint'
other/callback_dispatcher.c:595: syntax error before `jint'
other/callback_dispatcher.c:607: syntax error before `jint'
other/callback_dispatcher.c:621: syntax error before `void'
other/callback_dispatcher.c:632: syntax error before `void'
other/callback_dispatcher.c:647: syntax error before `jint'
other/callback_dispatcher.c:659: syntax error before `jint'
other/callback_dispatcher.c:672: syntax error before `jint'
other/callback_dispatcher.c:685: syntax error before `jint'
other/callback_dispatcher.c:698: syntax error before `jint'
other/callback_dispatcher.c:710: syntax error before `jint'
other/callback_dispatcher.c:724: syntax error before `void'
other/callback_dispatcher.c:735: syntax error before `void'
make[1]: *** [other/callback_dispatcher.o] Error 1
make[1]: Leaving directory `/home/brn/src/java-gnome-0.6.0/src'
make: *** [gtk] Error 2

The piece of code if first chokes on is (at line 57):
JNIEXPORT jobject JNICALL
Java_Gtk_Object_get(JNIEnv *env, jobject obj, jstring str)
{
return NULL;
}

I'm using Sun's JDK Version 1.3.0 FCS for Linux, on a Debian/x86
unstable system.

Any ideas ?

Cheers


_______________________________________________
java-gnome-developer mailing list
jav...@li...
http://lists.sourceforge.net/lists/listinfo/java-gnome-developer

[Java-gnome-developer] troubles compiling gnome-java

[Bastien N. <br...@fr...>]

Hi,

I just wanted to try out Gnome-Java. After a bit of hacking to get the
Makefiles to point to the right javac (they're insisting that my javac
binary be in /usr/bin/javac or something like that), I hit the wall when
it gets to compiling src/other/callback_dispatcher.c

gcc -c -g -O2 -fPIC -Iother other/callback_dispatcher.c -o
other/callback_dispatcher.o -I/usr/include/gtk-1.2
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include
-DNEED_GNOMESUPPORT_H -I/usr/lib/gnome-libs/include
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include \
    -I/usr/include/gnome-xml -I/usr/include/gtk-1.2
-I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/local/jdk-1.3//include -DGNOME
other/callback_dispatcher.c:57: syntax error before `jobject'
other/callback_dispatcher.c: In function `Java_Gtk_Object_get':
other/callback_dispatcher.c:60: warning: return makes integer from
pointer without a cast
other/callback_dispatcher.c: At top level:
other/callback_dispatcher.c:68: syntax error before `void'
other/callback_dispatcher.c: In function `jobject_signal_cb':
other/callback_dispatcher.c:149: warning: assignment makes integer from
pointer without a cast
other/callback_dispatcher.c:171: warning: assignment makes pointer from
integer without a cast
other/callback_dispatcher.c:174: warning: assignment makes integer from
pointer without a cast
other/callback_dispatcher.c:180: warning: assignment makes integer from
pointer without a cast
other/callback_dispatcher.c: In function `jobject_arg_signature':
other/callback_dispatcher.c:292: warning: assignment discards qualifiers
from pointer target type
other/callback_dispatcher.c: At top level:
other/callback_dispatcher.c:544: syntax error before `jint'
other/callback_dispatcher.c:556: syntax error before `jint'
other/callback_dispatcher.c:569: syntax error before `jint'
other/callback_dispatcher.c:582: syntax error before `jint'
other/callback_dispatcher.c:595: syntax error before `jint'
other/callback_dispatcher.c:607: syntax error before `jint'
other/callback_dispatcher.c:621: syntax error before `void'
other/callback_dispatcher.c:632: syntax error before `void'
other/callback_dispatcher.c:647: syntax error before `jint'
other/callback_dispatcher.c:659: syntax error before `jint'
other/callback_dispatcher.c:672: syntax error before `jint'
other/callback_dispatcher.c:685: syntax error before `jint'
other/callback_dispatcher.c:698: syntax error before `jint'
other/callback_dispatcher.c:710: syntax error before `jint'
other/callback_dispatcher.c:724: syntax error before `void'
other/callback_dispatcher.c:735: syntax error before `void'
make[1]: *** [other/callback_dispatcher.o] Error 1
make[1]: Leaving directory `/home/brn/src/java-gnome-0.6.0/src'
make: *** [gtk] Error 2

The piece of code if first chokes on is (at line 57):
JNIEXPORT jobject JNICALL
Java_Gtk_Object_get(JNIEnv *env, jobject obj, jstring str)
{
    return NULL;
}

I'm using Sun's JDK Version 1.3.0 FCS for Linux, on a Debian/x86
unstable system.

Any ideas ?

Cheers

[Java-gnome-developer] (no subject)

[<dg...@we...>]

Hello,

Just to let you know www.webcamgo.com is open Now !
Make around Trip Live Around the World with all the Webcams.

It's fun ! http://www.webcamgo.com

Thanks and have a nice visite on www.webcamgo.com


we apologize for any email you may have inadvertently received.
Please send back this email.

[Java-gnome-developer] Hello, your friend recommended openxxx to you

[<fr...@op...>]

You have been invited to check out this adult site
by one of your friends who visited us.

our URL is http://www.openxxx.net/
enjoy,
OpenXXX TEAM 2001

[Java-gnome-developer] Compiling on RedHat 7.1 & IBM jdk 1.3.0

[Philip A. C. <the...@be...>]

Because RedHat 7.1 has gcj installed with jni.h in /usr/include, 
java-gnome does not compile correctly.  instead of including the jdk's 
jni.h, gcj's version is included.  To fix this, I changed the order of 
the -I parameters to gcc in java-gnome/src/Makefile.in.  Here is the diff:

48,49c48,49
< 	gcc -c $(CFLAGS) $< -o $@ $(GTK_CFLAGS) $(GNOME_CFLAGS) \
< 	    $(LIBGLADE_CFLAGS) $(JAVA_INCLUDES) -D@MACRO_FLAG@
---
 > 	gcc -c $(CFLAGS) $< -o $@ $(JAVA_INCLUDES) $(GTK_CFLAGS) \
 > 	    $(GNOME_CFLAGS) $(LIBGLADE_CFLAGS) -D@MACRO_FLAG@

The orginal Makefile.in is the first file, my change is in the second file.

[Java-gnome-developer] Gnome Panel Applet Support?

[tom p. <tpa...@ac...>]

Hello.  I'm new to the list and in fact new to Java Gnome.  I found
the project last week and have been really enjoying working with it.
While poking through the Javadocs and sample code on the project home
page I could not find and pointers to developing Gnome Panel Applets.
My question is two-fold:
1.  Is there support for Panel Applets?
2.  Is there any sample code out there for this?

Thanks in advance for any help.

t.

[Java-gnome-developer] A question ....

[Dam <da...@ca...>]

Thank you for fixing the bug so rapidly :)

I got another question: how do I get the List widget of my combo box ?
because the function mycombo.getList() return a GtkWidget, and if I use

GtkList mylist = (GtkList) mycombo.getList()

I get a ClassCastException ....

Thanks for your help ....

Dam

[kuzman@neo.rr.com: Re: [Java-gnome-developer] Problem with GtkCombo]

[Jeffrey M. <ku...@ne...>]

The reason you cannot see it in the but list is because the status
has been changed to closed.  If you change the option on the bug query
you can view all open and closed bugs.  I actually fixed this
problem this morning and checked the fix into CVS.  If you get
the latest from CVS this problem will be fixed.

I would like to thank you for taking the time to report this problem.
Please don't hesitate reporting any other problem you encounter.

-Jeff

On 2001.07.02 14:09:05 -0400 Dam wrote:
> Hi,
> 
> I submitted this bug to sourceforge but it get removed.
> 
> I cannot set entries in the list in a GtkCombo. When I launch TestGTK
> from the test dir in the source tree of java-gnome, I get this error
> 
> Gtk-CRITICAL **: file gtkcombo.c: line 849
> (gtk_combo_set_popdown_strings): assertion `strings != NULL' failed.
> 
> I'm using debian unstable with gnome 1.4 and the latest cvs from
> java-gnome.
> 
> Thanks for these binding, it's great to be able to use GTK with java
> ....
> 
> Bye
> 
> Dam
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
> <HTML>
> <HEAD>
>   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
>   <META NAME="GENERATOR" CONTENT="GtkHTML/0.9.99.0">
> </HEAD>
> <BODY>Hi,<br>
> <br>
> I submitted this bug to sourceforge but it get removed.<br>
> <br>
> I cannot set entries in the list in a GtkCombo. When I launch TestGTK
> from the test dir in the source tree of java-gnome, I get this error<br>
> <br>
> Gtk-CRITICAL **: file gtkcombo.c: line 849
> (gtk_combo_set_popdown_strings): assertion `strings != NULL' failed.<br>
> <br>
> I'm using debian unstable with gnome 1.4 and the latest cvs from
> java-gnome.<br>
> <br>
> Thanks for these binding, it's great to be able to use GTK with java
> ....<br>
> <br>
> Bye<br>
> <br>
> Dam</BODY>
> </HTML>
> 

[Java-gnome-developer] Problem with GtkCombo

[Dam <da...@ca...>]

Hi,

I submitted this bug to sourceforge but it get removed.

I cannot set entries in the list in a GtkCombo. When I launch TestGTK
from the test dir in the source tree of java-gnome, I get this error

Gtk-CRITICAL **: file gtkcombo.c: line 849
(gtk_combo_set_popdown_strings): assertion `strings != NULL' failed.

I'm using debian unstable with gnome 1.4 and the latest cvs from
java-gnome.

Thanks for these binding, it's great to be able to use GTK with java
....

Bye

Dam

[Java-gnome-developer] Compiling 0.14.0 on RedHat 7.1

[Philip A. C. <the...@be...>]

I'm having trouble compiling gnome-gcj 0.14.0.  I'm running RedHat 7.1. 
I've installed gcc 3.0 in /usr/local/gcc-3.0 and I've exported the 
LD_LIBRARY_PATH environment variable:

[wyvern@red_dragon gnome-gcj-0.14.0]$ echo $LD_LIBRARY_PATH
/usr/local/gcc-3.0/lib


I've altered PATH so that gcj 3.0 is used:

[wyvern@red_dragon gnome-gcj-0.14.0]$ gcj --version
3.0


When running configure, I get the following error:

checking version of gcj and gcjh... earlier than 2.96
*** GCJ is too old. 2.96 or later is required.
configure: error: GCJ was not found


Knowing that I have 2.96 or greater, I copy configure to onfigure_local, 
and edit it.  I take out the portion of the configure file which tests 
the version of gcj:

<BEGIN cut portion of script>
else
     echo $ac_n "checking version of gcj and gcjh""... $ac_c" 1>&6
echo "configure:2044: checking version of gcj and gcjh" >&5
     gcj_fullver=`$GCJH --version | head -1 | sed 's/gcjh //'`

     case "$gcj_fullver" in
     *experimental*)
       # Probably 2.96 or later
       gcj_date=`echo $gcj_fullver | sed 's/(\(.*\) \(.*\) 
(experimental))/\2/'`
       echo "$ac_t""2.96 from $gcj_date" 1>&6
       if test "20000501" = "" -o "$gcj_date" -ge "20000501"; then
	:

       else
         echo "*** GCJ is too old. A 2.96 snapshot from 20000501 or 
later is required."
         { echo "configure: error: GCJ was not found" 1>&2; exit 1; }
       fi
       ;;
     *0.0|*)
       # Probably 2.95.x or earlier
       echo "$ac_t""earlier than 2.96" 1>&6
       if test "20000501" != ""; then
         echo "*** GCJ is too old. 2.96 or later is required."
         { echo "configure: error: GCJ was not found" 1>&2; exit 1; }
       else
	:

       fi
       ;;
     esac
<END Cut>


It gets past the version test (since it no longer exists), but gives me 
an error linking against libgcj:

checking for libgcj library... found in /usr
*** I could not compile and/or run a program with GCJ. It may be that
*** you haven't set your LD_LIBRARY_PATH. See the file config.log for
*** more details.
configure: error: libgcj was not found


Interesting since I do have LD_LIBRARY_PATH set (see above) and even the
version of libgcj which comes with RedHat's bundled gcc 2.96 doesn't 
reside in /usr.  So, I use the command line option 
--with-libgcj=/usr/local/gcc-3.0/lib
Still, even though it uses the correct directory, it still cannot link 
against libgcj:

checking for libgcj library... found in /usr/local/gcc-3.0/lib
*** I could not compile and/or run a program with GCJ. It may be that
*** you haven't set your LD_LIBRARY_PATH. See the file config.log for
*** more details.
configure: error: libgcj was not found


I would *REALLY* appreciate any help at all in solving this issue.  If 
any other information is needed, please email me and I'll be glad to 
supply it.

Thanks

Re: [Java-gnome-developer] RedHat 7.0 compile problem (solution - lack of)

[Bo J. <bj...@oa...>]

Quoting "Ian D . Stewart" <ids...@so...>:

> 
> On 2001.04.17 08:21:54 -0400 Jean van Wyk wrote:
> > Hi there,
> > 
> > The bad news is that it has now been verified three times with
> different
> > people that RedHat 7.0 with the latest gcc / libstdc++ RPMs from
> RedHat
> > has a problem with compiling (the java-gnome) JNI code.
> > 
> > The only way that I could fix it previously was by uninstalling the
> > offending gcc rpms and re-install the old versions.  As of yet I am
> not
> > aware of any other patch / solution for this problem.  If someone has
> > found a solution or has contacted RedHat over this problem, please let
> > us know.
> > 
> > I would like to stress that as far as I know this only happens with
> the
> > when the following RPMS are installed on a RedHat system
> > 
> > > RedHat 7.0
> > > gcc 2.96-69
> > > cpp 2.96-69
> > > glibc-devel 2.2-12
> > > libstdc++-devel 2.96-69
> 
> FWIW, 2.96 is a development release.  Anyone shipping this RPM's with a
> production system should be thrashed thoroughly about the head and
> shoulders.
> 
> The latest stable release is 2.95.3 (released last month).
> 
> 
> Regards,
> Ian

gcc/cpp 2.96-69 are the latest RedHat 7.0 "update" RPMs available, at least 
according to my mirror.  To the best of my knowledge, these are "official" 
RedHat updates.  FYI, 2.96-81 is included in the new 7.1 release.

Robert (Bo) Jordan
bj...@oa...   919.362.1205(w)
http://bo.cornbreadtree.org    919.362.1301(f)    

Re: [Java-gnome-developer] RedHat 7.0 compile problem (solution - lack of)

[Ian D . S. <ids...@so...>]

On 2001.04.17 08:21:54 -0400 Jean van Wyk wrote:
> Hi there,
> 
> The bad news is that it has now been verified three times with different
> people that RedHat 7.0 with the latest gcc / libstdc++ RPMs from RedHat
> has a problem with compiling (the java-gnome) JNI code.
> 
> The only way that I could fix it previously was by uninstalling the
> offending gcc rpms and re-install the old versions.  As of yet I am not
> aware of any other patch / solution for this problem.  If someone has
> found a solution or has contacted RedHat over this problem, please let
> us know.
> 
> I would like to stress that as far as I know this only happens with the
> when the following RPMS are installed on a RedHat system
> 
> > RedHat 7.0
> > gcc 2.96-69
> > cpp 2.96-69
> > glibc-devel 2.2-12
> > libstdc++-devel 2.96-69

FWIW, 2.96 is a development release.  Anyone shipping this RPM's with a
production system should be thrashed thoroughly about the head and
shoulders.

The latest stable release is 2.95.3 (released last month).


Regards,
Ian

-- 
A kind word need not cost much,
The price of praise can be cheap:
With half a loaf and an empty cup
I found myself a friend.
--Havamal, St. 52

[Java-gnome-developer] RedHat 7.0 compile problem (solution - lack of)

[Jean v. W. <jv...@Af...>]

Hi there,

The bad news is that it has now been verified three times with different
people that RedHat 7.0 with the latest gcc / libstdc++ RPMs from RedHat
has a problem with compiling (the java-gnome) JNI code.

The only way that I could fix it previously was by uninstalling the
offending gcc rpms and re-install the old versions.  As of yet I am not
aware of any other patch / solution for this problem.  If someone has
found a solution or has contacted RedHat over this problem, please let
us know.

I would like to stress that as far as I know this only happens with the
when the following RPMS are installed on a RedHat system

> RedHat 7.0
> gcc 2.96-69
> cpp 2.96-69
> glibc-devel 2.2-12
> libstdc++-devel 2.96-69

This has been verified with:
1) Sun JDK 1.3
2) IBM JDK 1.3
3) IBM JDK 1.1.8

If anyone on a non RedHat distribution has this error can you please let
us know.

Unfortunately this is a problem that we can do not have any control
over.  Hopefully this will be solved soon by RedHat or some RPMS.

Regards
Jean

[Java-gnome-developer] macro compile problem

[Darren S. <dar...@e-...>]

Hi,

I'm new to the list and very interested in java-gnome. I'm a keen Java
coder and
would love to do some Gnome apps, but I don't have time to learn c++ so
this
project is a godsend. Well done folks!

I installed the 0.5.0 binary rpm which seems to work ok, but I'd really
like to
try 0.6.0 or later for the Glade support (mmmm...). The trouble is, I'm
having
problems compiling.

The compilor (or preprocessor) seems to have problems with the JNIEXPORT
macro.
Wherever it appears, I get "syntax error before `jint'". The path to my
jni.h
and jni_md.h are definately given correctly in the gcc commandline, and my
jni_md.h gives this...

#define JNIEXPORT
#define JNICALL

I don't know much (any) about gcc or macros or much, so sorry that this
isn't 
specifically a java-gnome issue, but I'd appreciate any help to get this
thing
working. Alternatively, a binary RPM of 0.6.0 would go down well (...)

My system:

RedHat 7.0
IBM SDK 1.1.8
gcc 2.96-69
cpp 2.96-69
glibc-devel 2.2-12
libstdc++-devel 2.96-69

Don't know what else you might want to know...

Thanks,

Darren Scott
e-xentric (uk) ltd

[Java-gnome-developer] CVS: Fixes, fixes, fixes

[Santeri P. <sa...@ik...>]

Attached is a patch against current CVS head, as well as well as four new
files (src/code/glue/GdkWindow.[ch], src/code/java/GdkWindow.java,
tools/StructConstructorSpec.java).

These things have been changed (not all documented, though):

- Added (object) argument to argspec, look for example the gdk_color_parse
  routine which takes the GdkColor* as _second_ argument, not the first
  one.. now it is converted satisfyingly into a object method parse().

  See also gdk_draw_* which now are associated with GdkWindow as
  methods, not static routines! (BTW: Shouldn't they be associated
  with GdkDrawable, and not GdkWindow?)

  This required changes in ArgumentSpec and ArgumentList handling. The
  first argument is no longer special in the argument list
  (withoutFirst() is removed), and the getIsObject() and
  getExplicitObject() [maybe these should be renamed?] determine the
  actual object argument of the functions.

- Added (struct-constructor) as optional fourth field into
  (define-object). This has the effect of creating a g_malloc0()
  constructor for the type. This is usable for object types which do not
  sport a "natural" constructor (_new), and are used in Glib as normal
  structs. This allows allocation and manipulation of such types. See
  (define-object GdkColor) as an example.

  The StructConstructorSpec.java is part of this change. There's
  probably cleaner way my using existing classes, but I couldn't and
  didn't want to check how that could've been done.

- Fixed type conversion problems in getters.. these might not be the most
  beautiful way of doing them, but at least I got rid of tons of type
  problems in C. Mostly the problem was associated with the getter layout
  of:

    JNIEXPORT jobject JNICALL Java_gnu_gdk_GdkEventExpose_getWindow (
        JNIEnv *env, jobject obj)
    {
        GdkEventExpose *cptr = peerOfBaseObject (env, obj);
        {
            jclass result_jc = (*env)->FindClass (env, "gnu/gdk/GdkWindow");
            jobject result = makeBaseObjectSubclass (env, result_jc, (
                    GdkEventExpose_get_window (cptr)));
            return result;
        }
    }

    GdkWindow * GdkEventExpose_get_window (GdkEventExpose * cptr)
    {
        return cptr->window;
    }


  Previously the return type of GdkEventExpose_get_window was jobject,
  not GdkWindow *. I think it's better to keep the C routines with
  their "natural" types, and let the JNI wrapper perform the casting
  (as it currently does anyway).

- Added dependencies for the generated files also on the converter
  classes, so if you change the generator code the generated code will
  be generated automatically.

- Changed some object fields to (read-write), since they're that. This
  was done only on the object types that I happened to need to have
  settable fields, so the results are not complete.

- Added some misc. static GDK routines.

- LibGlade.java and LibGladeGnome.java tried to use type named "Map"
  to store Hashtables. Changed to use "Hashtable" instead.

- Changed FileEmitter to modify the target java/c/header file only if
  the "new" version differs from the old one (sans the "Generation
  date:" part). Very useful, since only those files that are really
  modified are touched, and thus files not really modified are not
  recompiled at all. Saves a lot of time.

Indentation of the changes is totally out of style wrt/ to the style
used in the current sources, since I could not figure out which
c-style (in emacs) it would be equivalent to.

With these changes I can now successfully make something like the
following:

	GdkColor c = new GdkColor();
	c.parse("red");
	getColormap().allocColor(c);

	gc.setForeground(c);
	getWindow().drawRectangle(...);

Okay. I hope I remembered to include all necessary files etc..

--
sa...@ik...                    I have become death, destroyer of the worlds.

Re: [Java-gnome-developer] problem installing the bindings

[manyoso <ma...@ya...>]

OK, here is the full output when I type make and then make install:

On 01 Apr 2001 14:42:50 -0400, manyoso wrote:
> I'm sorry.  The makeERROR file I attached did not have any errors as you
> said...  However, when I ran "make > makeERROR"  their were lot's of
> errors but they did not output to the makeERROR.  I will try all of this
> again and email the actual errors.
> 
> On 01 Apr 2001 10:58:44 +0200, Philipp Haller wrote:
> > I had kind of the same problem. I had installed Sun jdk1.3 and set my $JAVA_HOME to /usr/java/jdk1.3. So Java-gnome detected my jdk. But, just as with your configuration it searched in /usr/java/bin for javac, jar and javadoc. I just put an symlink with ln -s /usr/java/jdk1.3/bin /usr/java/bin before the make. So everything worked fine from then on.
> > 
> > You attached a file "makeERROR" that contains output from your make.
> > I can't see any errors in it!
> > It just compiles all .java and .c files, creates a jar and a lib and that's all, basicly.
> > 
> > You should try compiling and running some examples, I should work! You just have to tell Java-gnome where to look for the libraries. So you need to do something like this (after make install the libs are in /usr/local/lib):
> > $ java -Djava.library.path=/usr/local/lib class
> > 
> > I didn't figure out why you need this command line switch if /usr/local/lib is in LD_LIBRARY_PATH...
> > Can somebody explain this?
> > 
> > 
> > On 31 Mar 2001 15:30:14 -0500
> > manyoso <ma...@ya...> wrote:
> > 
> > > I am having a hell of a time installing the Java-Gnome bindings.  I am
> > > running a RedHat 7.0 system with Ximian Gnome 1.4 beta (from the
> > > red-carpet channel ;) and I have three different JDK's installed.
> > > IBM1.3 and Kaffe (from the rpm) and Sun's JDK1.3
> > > 
> > > Here is my $PATH:
> > > 
> > >     /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/manyoso/bin: No
> > >     such file or directory
> > > 
> > > The Kaffe tools are installed in /usr/bin and the IBM and SUN JDK's are
> > > installed in /usr/java/IBMJava2-13 and /usr/java/jdk1.3 respectively.  I
> > > did not have the JAVA_HOME variable set nor the CLASSPATH.  I downloaded
> > > the src.rpm and installed.  Then i took the tar file and put it in my
> > > home directory.
> > > 
> > > I untarred java-gnome into my home directory and cd into that directory.
> > > Then I ran ./configure --libdir=/usr/lib as the INSTALL file said.  This
> > > was the output:
> > > 
> > >     loading cache ./config.cache
> > >     checking for gcc... (cached) gcc
> > >     checking whether the C compiler (gcc  ) works... yes
> > >     checking whether the C compiler (gcc  ) is a cross-compiler... no
> > >     checking whether we are using GNU C... (cached) yes
> > >     checking whether gcc accepts -g... (cached) yes
> > >     checking for a BSD compatible install... (cached) /usr/bin/install
> > >     -c
> > >     checking for java... (cached) /usr/java/bin/java
> > >     checking for Java - version >= 1.1.7... no
> > >     ***
> > >     *** If you have Java installed and it is a newer version than 1.1.7,
> > >     either set
> > >     *** the JAVA_HOME variable or add the directory where the Java
> > >     binaries are to
> > >     *** the PATH.  Alternatively try "./configure
> > >     --with-java-prefix=<java_home>",
> > >     *** e.g. "./configure --with-java-prefix=/usr/jdk".
> > >     ***
> > >     *** Also make sure that configure does not find the wrong version of
> > >     Java by
> > >     *** looking at the output of "which java".
> > >     ***
> > > 
> > > I then set my JAVA_HOME variable to point to /usr/java/jdk1.3 and ran
> > > the ./configure script again.  This was the output:
> > > 
> > >     loading cache ./config.cache
> > >     checking for gcc... (cached) gcc
> > >     checking whether the C compiler (gcc  ) works... yes
> > >     checking whether the C compiler (gcc  ) is a cross-compiler... no
> > >     checking whether we are using GNU C... (cached) yes
> > >     checking whether gcc accepts -g... (cached) yes
> > >     checking for a BSD compatible install... (cached) /usr/bin/install
> > >     -c
> > >     Add /usr/java/IBMJava2-13/bin to path and check again.
> > >     checking for java... /usr/java/jdk1.3/bin/java
> > >     checking for Java - version >= 1.1.7... yes
> > >     checking for javadoc... (cached) /usr/java/bin/javadoc
> > >     checking for javac... (cached) /usr/java/bin/javac
> > >     checking for java... (cached) /usr/java/jdk1.3/bin/java
> > >     checking for jar... (cached) /usr/java/bin/jar
> > >     checking for main in -libs... (cached) no
> > >     checking for gtk-config... (cached) /usr/bin/gtk-config
> > >     checking for GTK - version >= 1.2.0... yes
> > >     checking for gnome-config... (cached) /usr/bin/gnome-config
> > >     checking for GNOME - version >= 1.2.0... yes
> > >     checking for libglade-config... (cached) /usr/bin/libglade-config
> > >     checking for libglade... yes
> > >     checking for working const... (cached) yes
> > >     checking how to run the C preprocessor... (cached) gcc -E
> > >     checking for working alloca.h... (cached) yes
> > >     checking for alloca... (cached) yes
> > >     updating cache ./config.cache
> > >     creating ./config.status
> > >     creating test/Makefile
> > >     creating src/Makefile
> > >     creating src/tools/Makefile
> > >     creating Makefile
> > >     creating java-gnome.spec
> > >     creating java-gtk.spec
> > > 
> > > Obviously, it detected my JAVA_HOME variable, but it set the path for
> > > javac and other tools to /usr/java/bin... I then ran make and it barfed
> > > when looking for javac.
> > > 
> > > I tooled around in the configure script looking for help, but i was
> > > lost.  I then made a symbolic link from /usr/java/bin to
> > > /usr/java/jdk1.3/bin and untarred everything and started over.  This
> > > time when I ran make, it detected my javac and everything, but it failed
> > > with all kinds of errors...  I've attached some of the output from the
> > > make command.  I am wondering if this is because I am using Gnome1.4
> > > beta from Ximian.
> > > 
> > > Any suggestions?
> > > 
> > 
> > 
> > -- 
> > http://www.javacraft.de - Programmieren in Java
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> java-gnome-developer mailing list
> jav...@li...
> http://lists.sourceforge.net/lists/listinfo/java-gnome-developer

Re: [Java-gnome-developer] problem installing the bindings

[manyoso <ma...@ya...>]

I'm sorry.  The makeERROR file I attached did not have any errors as you
said...  However, when I ran "make > makeERROR"  their were lot's of
errors but they did not output to the makeERROR.  I will try all of this
again and email the actual errors.

On 01 Apr 2001 10:58:44 +0200, Philipp Haller wrote:
> I had kind of the same problem. I had installed Sun jdk1.3 and set my $JAVA_HOME to /usr/java/jdk1.3. So Java-gnome detected my jdk. But, just as with your configuration it searched in /usr/java/bin for javac, jar and javadoc. I just put an symlink with ln -s /usr/java/jdk1.3/bin /usr/java/bin before the make. So everything worked fine from then on.
> 
> You attached a file "makeERROR" that contains output from your make.
> I can't see any errors in it!
> It just compiles all .java and .c files, creates a jar and a lib and that's all, basicly.
> 
> You should try compiling and running some examples, I should work! You just have to tell Java-gnome where to look for the libraries. So you need to do something like this (after make install the libs are in /usr/local/lib):
> $ java -Djava.library.path=/usr/local/lib class
> 
> I didn't figure out why you need this command line switch if /usr/local/lib is in LD_LIBRARY_PATH...
> Can somebody explain this?
> 
> 
> On 31 Mar 2001 15:30:14 -0500
> manyoso <ma...@ya...> wrote:
> 
> > I am having a hell of a time installing the Java-Gnome bindings.  I am
> > running a RedHat 7.0 system with Ximian Gnome 1.4 beta (from the
> > red-carpet channel ;) and I have three different JDK's installed.
> > IBM1.3 and Kaffe (from the rpm) and Sun's JDK1.3
> > 
> > Here is my $PATH:
> > 
> >     /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/manyoso/bin: No
> >     such file or directory
> > 
> > The Kaffe tools are installed in /usr/bin and the IBM and SUN JDK's are
> > installed in /usr/java/IBMJava2-13 and /usr/java/jdk1.3 respectively.  I
> > did not have the JAVA_HOME variable set nor the CLASSPATH.  I downloaded
> > the src.rpm and installed.  Then i took the tar file and put it in my
> > home directory.
> > 
> > I untarred java-gnome into my home directory and cd into that directory.
> > Then I ran ./configure --libdir=/usr/lib as the INSTALL file said.  This
> > was the output:
> > 
> >     loading cache ./config.cache
> >     checking for gcc... (cached) gcc
> >     checking whether the C compiler (gcc  ) works... yes
> >     checking whether the C compiler (gcc  ) is a cross-compiler... no
> >     checking whether we are using GNU C... (cached) yes
> >     checking whether gcc accepts -g... (cached) yes
> >     checking for a BSD compatible install... (cached) /usr/bin/install
> >     -c
> >     checking for java... (cached) /usr/java/bin/java
> >     checking for Java - version >= 1.1.7... no
> >     ***
> >     *** If you have Java installed and it is a newer version than 1.1.7,
> >     either set
> >     *** the JAVA_HOME variable or add the directory where the Java
> >     binaries are to
> >     *** the PATH.  Alternatively try "./configure
> >     --with-java-prefix=<java_home>",
> >     *** e.g. "./configure --with-java-prefix=/usr/jdk".
> >     ***
> >     *** Also make sure that configure does not find the wrong version of
> >     Java by
> >     *** looking at the output of "which java".
> >     ***
> > 
> > I then set my JAVA_HOME variable to point to /usr/java/jdk1.3 and ran
> > the ./configure script again.  This was the output:
> > 
> >     loading cache ./config.cache
> >     checking for gcc... (cached) gcc
> >     checking whether the C compiler (gcc  ) works... yes
> >     checking whether the C compiler (gcc  ) is a cross-compiler... no
> >     checking whether we are using GNU C... (cached) yes
> >     checking whether gcc accepts -g... (cached) yes
> >     checking for a BSD compatible install... (cached) /usr/bin/install
> >     -c
> >     Add /usr/java/IBMJava2-13/bin to path and check again.
> >     checking for java... /usr/java/jdk1.3/bin/java
> >     checking for Java - version >= 1.1.7... yes
> >     checking for javadoc... (cached) /usr/java/bin/javadoc
> >     checking for javac... (cached) /usr/java/bin/javac
> >     checking for java... (cached) /usr/java/jdk1.3/bin/java
> >     checking for jar... (cached) /usr/java/bin/jar
> >     checking for main in -libs... (cached) no
> >     checking for gtk-config... (cached) /usr/bin/gtk-config
> >     checking for GTK - version >= 1.2.0... yes
> >     checking for gnome-config... (cached) /usr/bin/gnome-config
> >     checking for GNOME - version >= 1.2.0... yes
> >     checking for libglade-config... (cached) /usr/bin/libglade-config
> >     checking for libglade... yes
> >     checking for working const... (cached) yes
> >     checking how to run the C preprocessor... (cached) gcc -E
> >     checking for working alloca.h... (cached) yes
> >     checking for alloca... (cached) yes
> >     updating cache ./config.cache
> >     creating ./config.status
> >     creating test/Makefile
> >     creating src/Makefile
> >     creating src/tools/Makefile
> >     creating Makefile
> >     creating java-gnome.spec
> >     creating java-gtk.spec
> > 
> > Obviously, it detected my JAVA_HOME variable, but it set the path for
> > javac and other tools to /usr/java/bin... I then ran make and it barfed
> > when looking for javac.
> > 
> > I tooled around in the configure script looking for help, but i was
> > lost.  I then made a symbolic link from /usr/java/bin to
> > /usr/java/jdk1.3/bin and untarred everything and started over.  This
> > time when I ran make, it detected my javac and everything, but it failed
> > with all kinds of errors...  I've attached some of the output from the
> > make command.  I am wondering if this is because I am using Gnome1.4
> > beta from Ximian.
> > 
> > Any suggestions?
> > 
> 
> 
> -- 
> http://www.javacraft.de - Programmieren in Java


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Java-gnome-developer] Patch to makeBaseObjectClass()

[Julian F. <z2...@ug...>]

Looks like you got your string comparisons backwards...

Patch included,

Julian

[Java-gnome-developer] problem installing the bindings

[manyoso <ma...@ya...>]

I am having a hell of a time installing the Java-Gnome bindings.  I am
running a RedHat 7.0 system with Ximian Gnome 1.4 beta (from the
red-carpet channel ;) and I have three different JDK's installed.
IBM1.3 and Kaffe (from the rpm) and Sun's JDK1.3

Here is my $PATH:

    /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/manyoso/bin: No
    such file or directory

The Kaffe tools are installed in /usr/bin and the IBM and SUN JDK's are
installed in /usr/java/IBMJava2-13 and /usr/java/jdk1.3 respectively.  I
did not have the JAVA_HOME variable set nor the CLASSPATH.  I downloaded
the src.rpm and installed.  Then i took the tar file and put it in my
home directory.

I untarred java-gnome into my home directory and cd into that directory.
Then I ran ./configure --libdir=/usr/lib as the INSTALL file said.  This
was the output:

    loading cache ./config.cache
    checking for gcc... (cached) gcc
    checking whether the C compiler (gcc  ) works... yes
    checking whether the C compiler (gcc  ) is a cross-compiler... no
    checking whether we are using GNU C... (cached) yes
    checking whether gcc accepts -g... (cached) yes
    checking for a BSD compatible install... (cached) /usr/bin/install
    -c
    checking for java... (cached) /usr/java/bin/java
    checking for Java - version >= 1.1.7... no
    ***
    *** If you have Java installed and it is a newer version than 1.1.7,
    either set
    *** the JAVA_HOME variable or add the directory where the Java
    binaries are to
    *** the PATH.  Alternatively try "./configure
    --with-java-prefix=<java_home>",
    *** e.g. "./configure --with-java-prefix=/usr/jdk".
    ***
    *** Also make sure that configure does not find the wrong version of
    Java by
    *** looking at the output of "which java".
    ***

I then set my JAVA_HOME variable to point to /usr/java/jdk1.3 and ran
the ./configure script again.  This was the output:

    loading cache ./config.cache
    checking for gcc... (cached) gcc
    checking whether the C compiler (gcc  ) works... yes
    checking whether the C compiler (gcc  ) is a cross-compiler... no
    checking whether we are using GNU C... (cached) yes
    checking whether gcc accepts -g... (cached) yes
    checking for a BSD compatible install... (cached) /usr/bin/install
    -c
    Add /usr/java/IBMJava2-13/bin to path and check again.
    checking for java... /usr/java/jdk1.3/bin/java
    checking for Java - version >= 1.1.7... yes
    checking for javadoc... (cached) /usr/java/bin/javadoc
    checking for javac... (cached) /usr/java/bin/javac
    checking for java... (cached) /usr/java/jdk1.3/bin/java
    checking for jar... (cached) /usr/java/bin/jar
    checking for main in -libs... (cached) no
    checking for gtk-config... (cached) /usr/bin/gtk-config
    checking for GTK - version >= 1.2.0... yes
    checking for gnome-config... (cached) /usr/bin/gnome-config
    checking for GNOME - version >= 1.2.0... yes
    checking for libglade-config... (cached) /usr/bin/libglade-config
    checking for libglade... yes
    checking for working const... (cached) yes
    checking how to run the C preprocessor... (cached) gcc -E
    checking for working alloca.h... (cached) yes
    checking for alloca... (cached) yes
    updating cache ./config.cache
    creating ./config.status
    creating test/Makefile
    creating src/Makefile
    creating src/tools/Makefile
    creating Makefile
    creating java-gnome.spec
    creating java-gtk.spec

Obviously, it detected my JAVA_HOME variable, but it set the path for
javac and other tools to /usr/java/bin... I then ran make and it barfed
when looking for javac.

I tooled around in the configure script looking for help, but i was
lost.  I then made a symbolic link from /usr/java/bin to
/usr/java/jdk1.3/bin and untarred everything and started over.  This
time when I ran make, it detected my javac and everything, but it failed
with all kinds of errors...  I've attached some of the output from the
make command.  I am wondering if this is because I am using Gnome1.4
beta from Ximian.

Any suggestions?