> It is consistent with other porting code (ex. Windows). So it have
> no problem only load_add_on.
Ah, yes. It is a result of my inconsistent opinion on how to write
autoconf scripts.
What do others think? Should one test for all the functions used, or
only one indicator to test for the API?
On one hand, testing every function needed makes it simpler to
discover strange platforms by looking at the ./configure output. On
the other hand, it is a complete waste of time if the family of
functions detected by the indicator, only comes as a group.
> My current build is working fine!.
Sounds marvelous. :-) Have you done a mauve test to check for
problems? <URL:http://sourceware.cygnus.com/mauve/>
> But It need change lib/libnative/java.net and lib/libnative/java.io
> etc...
Send more patches. :-) Maybe you should try to use Classpath instead
of JDK classes?
BTW: Are you on the Japhar mailing list, or do I need to keep sending
replies directly to you? I'm on the list, so you don't have to send
me two copies. :-)
--
##> Petter Reinholdtsen <## | [EMAIL PROTECTED]
O- <SCRIPT Language="Javascript">window.close()</SCRIPT>
http://www.hungry.com/~pere/ | Go Mozilla, go! Go!
