Skip to main content

wired build process for JDK5

3 replies [Last post]
neojia
Offline
Joined: 2006-07-11

hi,

I have made some changes on jdk5 but the build takes about 3-4 hours on my Intel P4 FC3 machine. I think the init. build should need that much of time. After the init build, when I change a header file, the build will take again for 3 hours, which is correct also. But the most wired thing happens after running the generated binary, my modification does not show up ... So, I have to touch the header file again and rebuild it.

Is there anybody who have encountered the same problem? Is there any workaround?

Thanks,
Neo

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
trembovetski
Offline
Joined: 2003-12-31

One workaround is that you can build only part you've touched. Say, if the change was in sun.awt, you'd do:
[code]
#> cd j2se/make/sun/awt
#> gnumake
[/code]

or, if the change was to public code (java.awt.*)
[code]
#> cd j2se/make/java/awt
#> gnumake
[/code]

Unfortunately there's no good mapping between the code
and the make directories which the code is built from -
at least, not always.

Another thing is that if the change was java-only, you can compile the class you changed and then prepend it to the boot class path (-Xbootclasspath/a).

Dmitri

neojia
Offline
Joined: 2006-07-11

Most of my changes are inside the hotspot instead of the java classes.

nepalese
Offline
Joined: 2006-04-04

make hotspot