Messages in the build log

Project:JNode Builder
Component:Code
Category:bug report
Priority:minor
Assigned:Unassigned
Status:won't fix
Description

Why can the following classes be found ? They seem to be present in the core/src/openjdk/** hierarchy though.


[bootimage] JNode class not found sun.security.jgss.SunProvider
[bootimage] JNode class not found sun.security.rsa.SunRsaSign
[bootimage] JNode class not found com.sun.crypto.provider.SunJCE
[bootimage] JNode class not found sun.security.provider.Sun
[bootimage] JNode class not found com.sun.security.sasl.Provider
[bootimage] JNode class not found org.jcp.xml.dsig.internal.dom.XMLDSigRI
[bootimage] JNode class not found sun.security.smartcardio.SunPCSC
[bootimage] JNode class not found com.sun.net.ssl.internal.ssl.Provider

#1

Submitted by brihaye on Mon, 04/13/2009 - 08:03.

Another possibly annoying issue :


[asm] /home/jnode/robot/svnwork/jnode/core/src/native/x86/mm64.asm:201: warning: value does not fit in 32 bit field
[asm] /home/jnode/robot/svnwork/jnode/core/src/native/x86/mm64.asm:201: warning: value does not fit in 32 bit field
[asm] /home/jnode/robot/svnwork/jnode/core/src/native/x86/mm64.asm:274: warning: value does not fit in 32 bit field
[asm] /home/jnode/robot/svnwork/jnode/core/src/native/x86/mm64.asm:274: warning: value does not fit in 32 bit field

Line 201 : and eax,~CR0_PG
Line 274 : and eax,~CR0_PG

... and in i386.h :

Line45 : CR0_PG equ 0x80000000 ; Paging enabled

#2

Submitted by Stephen Crawley on Mon, 04/13/2009 - 10:25.
Category:support request» bug report
Status:active» won't fix

Thanks for bringing this to our attention, but at this stage in JNode's development, warnings/errors in the build log are not worth reporting as issues .... unless they indicate that some aspect of the build is not working at all.

Marking this issue as 'wont fix'.

#3

Submitted by brihaye on Mon, 04/13/2009 - 13:55.

I don't consider them as issues, rather as questions Smiling

Recent discussions on the IRC channel tend to show that there are still some known issues of this kind (alignment) in the low level code. Just wondering if these warnings are related.

#4

Submitted by Stephen Crawley on Mon, 04/13/2009 - 14:15.

Ummm ... in comment #1 you said (and I quote):

"Another possibly annoying issue"

If you are simply asking questions, I suggest that 1) you don't call them issues, and 2) you don't ask then in the issue tracker. There are better places, like on IRC or in a forum discussion.

#5

Submitted by Peter on Mon, 04/13/2009 - 15:58.

I still have to comment on that now even if unrelated to the original issue.
The issue brought up brihaye seems to be a serious issue. I don't know how yasm handles that, but it should be clearly rax instead of eax.
Anyway, as the 64bit build is at least runtime-broken (and on my local setup build-broken, too) I wonder if we should keep the 64bit nightly build.

I created a separate thread for the nightly build.

Either brihaye opens a separate issue for his question or I will depending on the comments regarding nightly build.

#6

Submitted by brihaye on Tue, 04/14/2009 - 08:16.

So, it's an issue.

Well, I'm still unsure about how to interact with the JNode project (I'm rather used to mailing-lists rather than web forums or IRC channels ; 90s style, I know) and I still don't have enough background to know if these warnings have some consequences on currents build(s), if they are known by the development team, postponed or whatever...

I've also been alerted by some IRC logs where serious issues are mentionned, especially this one :
http://echelog.matzon.dk/logs/browse/jnode.org/1238108400

Also, is it wise to build JNode with the -Xlint:unchecked flag ? I guess it would bring some reliabilty to get rid of uchecked/unsafe operations. Well... i don't know.

Anyway, I wouldn't report anything if I knew how the build process is supposed to work and what is the general agreement about it.

In the meanwhile, I think that opening specific issues in the tracker is a good solution indeed.

#7

Submitted by Stephen Crawley on Tue, 04/14/2009 - 09:28.

Fair enough.

I'll leave it to others on the team to respond to your issues ... or not, as they see fit.

#8

Submitted by Peter on Tue, 04/14/2009 - 11:16.

I opened a separate bug report here.

I can see that this is not so easy to see if something is a bug at all or not. And actually I saw those warnings before but never thought about them. Now where you "asked" about them I thought, that it's a bug or at least bad coding style. On the other hand your first finding is imho just a "Informational output" by the bootimagebuilder and not serious at all.

I might be wrong with both, so imho it is a good idea to report stuff like that or ask on IRC. Anyway, if you find more bugs (like your first comment), I'd prefer that you open a separate issue instead. It's easy to set a issue to "won't fix", fix it or whatever, but it gets harder if you have to track multiple bugs in one issue (which is why I moved your report).

The original issue should stay "won't fix" right now.

Regarding the -Xlint:unchecked, I like that idea, but again, I'd open it in a separate issue as a feature request. (Due to general time problems (and you probably already know the game), I'd like to point out, that it is much likely that you'll get a "Where's the patch?" answer on stuff like that Eye-wink)
Anyway, I'm encouraging you to continue, and best to also submit patches Smiling