FreeBSD 5.2.1. - JDK 1.4 installation from ports collection

[Christian Hofer]

David Pullara wrote:

>As I understand it you need the linux jdk to build the native one.
>I noticed I got that same "can't detect" error when running the linux
>java before I switched to the native one.  However, before I switched
>I found these instructions either from this mailing list or with a
>google search:
>
>   # kldload linprocfs
>   # mount -t linprocfs linprocfs /compat/linux/proc
>
>Once I did that I didn't get that warning anymore.
>
>  
>
The second time I tried the installation (after getting the error the 
first time), I got explicit instructions to load the kernel module and 
mount the linproc pseudo filesystem as described. But if this is the 
source of the bug, then it has already been to late: the 
CurrencyData-File was already corrupted by the error message. So I had 
to manually delete it.

It would actually be two bugs then:
1. It seems strange that a compiler warning is inserted in the beginning 
of a java file, causing the failing to parse this file later, and 
resulting in a strange "can't detect" error.
2. The port's Makefile has to check, if linprocfs is mounted, already 
the first time, that "make install" is done, not only in the second attempt.

But the actual behaviour (to check only the second time) seems to be 
rather strange. Thus, my impression was, that the non-mounted Linux proc 
filesystem is not the cause of the error. I thought that the mounting of 
this pseudo file system happens automatically the first time you run 
"make install", and is only forgotten the second time, causing the above 
message. My explanation would be, that only the warning, which normally 
would be ignored, is misdirected into the file. But this is only 
speculation and somebody competent should check it.

Chris

>So if I'm understanding this correctly and after looking at the
>file, CurrencyData.java seems to be generated by a java program;
>maybe they redirect the output to a file, hence that warning
>showing up in the source.  So maybe the solution is to do the
>above commands before building the native jdk?  (Maybe the build
>scripts can check for that, if that is a good idea?)
>
>d
>  
>