× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I just tried a quick compile and it worked OK for me in terms of
correctly processing the #include (which was pretty much all I had in
my test source).  Is the symbolic link QJAVA/H/JNI mapping correctly
on your system?

You are correct about not being able to change the QSYSINC source.  This
is so that IBM can replace the source by way of a PTF or a new release
and not inadvertently back out your modifications.  What you can do is
copy the source member to another file, make the modifications there,
and create any necessary symbolic links/INCLUDE environment variable
customizations.

Bruce

>
>Hello,
>
>when I try compile a C module that includes jni.h always fails because
>the qsysinc jni.h (QSYS.LIB/QSYSINC.LIB/H.FILE/JNI.MBR) has a relative
>path include to QJAVA/H/JNI that the compiler never found.
>
>I think that the path must be absolute (/QJAVA/H/JNI), but I can
>change the qsysinc jni.h source.
>
>Anybody have compiled successfully a java native interface module?
>regards
>
>Adolfo
>


+---
| This is the C/400 Mailing List!
| To submit a new message, send your mail to C400-L@midrange.com.
| To subscribe to this list send email to C400-L-SUB@midrange.com.
| To unsubscribe from this list send email to C400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: bob@cstoneindy.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.