On 31-05-2015 07:51, Pierre Labastie wrote:
> Hi all,
> 
> I built OpenJDK with gcc-5 on LFS SVN-20150515 (uses linux-4.0.3).
> 
> As said in another post, there was a minor problem with the OS not recognized.
> But then, I used the newly built JVM to compile icedtea-web, and that was very
> slow. Also, top showed that sometimes, the JVM allocated more than 16Gb of
> memory, leading to heavy disk usage, because of swapping.
> 
> So I went back to rebuilding OpenJDK with itself, and got the same behavior:
> slow and high use of memory. Actually, it even allocated the full swap space
> and failed while building in the jdk subdirectory.
> 
> Note that the binary JVM downloaded from anduin runs well. That binary was
> compiled from the same sources, but with gcc-4.9.2.
> 
> Actually, there is a patch:
> http://cr.openjdk.java.net/~sgehwolf/webrevs/JDK-8078666/webrev.02/hotspot.patch
> 
> Will try to make a sed.

Thanks for that post.

I did build book's version, noticed the problem, then built 8u60-b14,
same problem. Was going to ask help in support, but many things to do,
delayed until now. Don't remember any longer all details.

Thought it could be a problem in my system or with using gcc5 (which is
almost the same thing: problem with the system using gcc5), used
upstream proprietary to bootstrap, was going to download again your
binary to test...

jdk8u60-b14-2015.05.11-18h25m19s.log.xz

jdk8u45-b14-2015.05.11-21h04m42s.log.xz

At that time, I was still using linux-3.19.3, so, now, I almost sure in
blaming gcc5, not linux-4, after your post.

Will try to build after your fixes, as soon as I find time.

OT: IDEA WHEN WAS HAVING THOSE PROBLEMS

Following is not a complaint, I, myself, used the same as you, when was
maintaining the page.

One thing I noticed, as you wrote in the OJDK page, all the source
packages are named after OJDK itself:

{{{
The following files may be downladed from the OpenJDK mercurial
repository using the addresses
http://hg.openjdk.java.net/jdk8u/jdk8u/<component>/archive/jdk8u45-b14.tar.bz2,
where <component> is the name of the JVM component (corba, hostspot, and
so on), but that involves renaming the downloaded files, and renaming
the extracted directories. For convenience, the BLFS editors have made
the files available in an LFS website.
}}}

I would like to propose changes for the page, for the *next* release,
only, jdk8u60-bSomeBuildNumber.

Hope you don't mind for my suggestions, and of course, you can just
ignore them.

In my build script, I am using the upstream files, then download with:

{{{
  package=jdk8u45-b14.tar.bz2 &&
  URL=http://hg.openjdk.java.net/jdk8u/jdk8u &&
  URL_END=archive/$package &&
  wget -c $URL/$URL_END &&
  md5sum $package > OpenJDK-1.8.0.45-b14.md5 &&
  for additional in corba hotspot jaxp jaxws langtools jdk nashorn
  do
    wget -c $URL/$additional/$URL_END -O $additional-$package &&
    md5sum $additional-$package >> OpenJDK-1.8.0.45-b14.md5
  done &&
}}}

Of course this could be still further simplified.

This suggests to me that we could use the same stile as in Xorg libs and
other Xorg pages (names, below are not well thought, just examples).
Bruce is adopting same convention for KDE Frameworks (forgot the exact
name):

{{{
cat > jdk8u45-b14.md5 << "EOF"
jdk8u45-b14.tar.bz2  <jdk8u45-b14.tar.bz2 md5sum>
...

nashorn-jdk8u45-b14.tar.bz2  <nashorn-jdk8u45-b14.tar.bz2 md5sum>
EOF

wget ... &&

md5sum jdk8u45-b14.md5 &&

tar -xf jdk8u45-b14.tar.bz2 &&
cd jdk8u45-b14 &&

for additional in corba hotspot jaxp jaxws langtools jdk nashorn
do
  tar -xf ../$additional-jdk8u45-b14.tar.bz2 &&
  mv -v $additional-jdk8u45-b14 $additional
done; unset additional &&

...

}}}

Instead of mv, perhaps it could be ln -sv?

Well, these can also be simplified, but I wanted only to give the idea
for your consideration, I am sure that if you accepted the idea, your
final layout would be much simpler than mine.

Sorry to bother you with this.

-- 
[]s,
Fernando
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to