This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: build macros and includes


>>>>> "Ray" == Ray Auge <rayauge@doublebite.com> writes:

Ray> So, I'm stuck with a kludge. There wouldn't happen to be a script
Ray> or a call I can make to gcj to locate libgcj's jni.h?

Nope.  We install it where gcc can find it.

Ray> Debian /usr/include/jni.h
Ray> Mandrake /usr/include/libgcj-${version}/jni.h
Ray> FC/RedHAt /usr/lib/gcc-lib/${arch}-redhat-linux/${version}/include/jni.h

If just plain old "#include <jni.h>" doesn't work, then it is probably
a distro bug.  It looks like you ought to be ok on at least Debian and
RH.  Mandrake, I don't know.

If there's an alternative that makes sense, we're open to it.

One potential problem here is that from a gcc point of view, it makes
sense to create an install tree that is self-contained, i.e. where
jni.h is found by gcc without any special tweaking.  But, this might
not always make sense for a distro.

Ray> PS: It's my first time putting this much consideration into a build. I
Ray> hope I'm not being a pest.

Not at all.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]