Re: strange build error

2008-04-16 Thread Roman Kennke
Hi, > I managed to successfully build jdk7 with your patches. No errors here. > A strange thing is that I have a class FontManager$5$1 instead of yours > FontManager$4$1 (I see from the zipfile you've sent us, that you have > both FontManager$4$1 and FontManager$5$1). You sure that your > envir

Re: strange build error

2008-04-16 Thread Maurizio Cimadamore
Hi again I managed to successfully build jdk7 with your patches. No errors here. A strange thing is that I have a class FontManager$5$1 instead of yours FontManager$4$1 (I see from the zipfile you've sent us, that you have both FontManager$4$1 and FontManager$5$1). You sure that your environmen

Re: strange build error

2008-04-16 Thread Maurizio Cimadamore
Hi Roman, just to ask, if you go in the langtools repository and type hg tip what's the output? Just to make sure that you have the latest langtools available Maurizio Roman Kennke wrote: Hi there, Unfortunately I wasn't able to build your workspace (even though I'm able to build the

Re: strange build error

2008-04-16 Thread Roman Kennke
Hi there, > Unfortunately I > wasn't able to build your workspace (even though I'm able to build the > latest full jdk) since when compiling the AWT I'm getting this error: > > awt_LoadLibrary.c:(.text+0x358): undefined reference to `AWTIsHeadless' > collect2: ld returned 1 exit status Whoops!

Re: strange build error

2008-04-14 Thread Roman Kennke
Hi Maurizio, > I had a look at your classfiles. What I can tel you for sure is that (as > you suspected) the classfile FontManager$4$1.class is generated > correctly. Its "enclosingMethod" attribute points to the constant pool > entry for FontManager$4.run() as it should be. At this point the p

Re: strange build error

2008-04-14 Thread Maurizio Cimadamore
Hi Roman I had a look at your classfiles. What I can tel you for sure is that (as you suspected) the classfile FontManager$4$1.class is generated correctly. Its "enclosingMethod" attribute points to the constant pool entry for FontManager$4.run() as it should be. At this point the problem seem

Re: strange build error

2008-04-11 Thread Roman Kennke
Hi Jon, > I find the ":" in "(sun/font:FontManager$4$1.class)" somewhat > strange. It might be worth checking CreateSymbols to see if that is > just an artifact of the error message, or if it is indicative of the > error. Hmm, I'm not sure where this string is created. > Have you tried us

Re: strange build error

2008-04-11 Thread Jonathan Gibbons
Roman, I find the ":" in "(sun/font:FontManager$4$1.class)" somewhat strange. It might be worth checking CreateSymbols to see if that is just an artifact of the error message, or if it is indicative of the error. Have you tried using javap or similar disassembler to see if they can rea

Re: strange build error

2008-04-11 Thread Mark Wielaard
Hi Roman, On Fri, 2008-04-11 at 10:36 +0200, Roman Kennke wrote: > while developing on my Innovators Challenge project, I came about the > following build error: > > http://kennke.org/~roman/build-error.txt It is easier if you at least include the error/warnings in the email: error: bad

Re: strange build error

2008-04-11 Thread Maurizio Cimadamore
Uhmm, could you please re-formulate why do you think this is a javac problem? I can't see any compilation errors on the log file Moreover the following code compiles with the latest snapshot of javac class Test { final Runnable fileCloserRunnable = new Runnable() { public void run() {

strange build error

2008-04-11 Thread Roman Kennke
Hi there, while developing on my Innovators Challenge project, I came about the following build error: http://kennke.org/~roman/build-error.txt I'm not sure what com.sun.tools.javac.sym.CreateSymbols does and why it fails. The classes all compile fine. A couple of notes: - This error only occur