On Oct 30, 2007, at 5:47 PM, Kelly O'Hair wrote:
The directory in ALT_JDK_IMPORT_PATH
(in your case /mounts/hel/disks/0/shared-data/njriley/openjdk/old)
should contain a jdk image, e.g. bin, lib, include, jre/bin, jre/
lib, lib/tools.jar,
jre/lib/rt.jar. etc...
Does it?
No, it only containe
Hello,
I came across an issue while building OpenJDK today. It seems that
some sources that existed in b19 have been removed in b20.
I realize some sources have been moved around since langtools were
introduced, but there are a few that do not exist anymore. This
problem isn't obvious when b
A FULL jdk control build involves having the following directories:
control langtools corba jaxp jaxws hotspot j2se
And you are right, you should not need to set ALT_JDK_IMPORT_PATH when doing
a full control build.
The ALT_JDK_IMPORT_PATH should just be used when the build detects one
of the
Lillian Angel wrote:
Hello,
I came across an issue while building OpenJDK today. It seems that some
sources that existed in b19 have been removed in b20.
I realize some sources have been moved around since langtools were
introduced, but there are a few that do not exist anymore. This probl
Kelly O'Hair wrote:
Lillian Angel wrote:
Hello,
I came across an issue while building OpenJDK today. It seems that
some sources that existed in b19 have been removed in b20.
I realize some sources have been moved around since langtools were
introduced, but there are a few that do not ex
Experimental openjdk repositories!
http://hg.openjdk.java.net
-kto
To get the Mercurial Forest Extension:
hg clone http://www.terminus.org/hg/hgforest hgforest
Then I copy hgforest/forest.py to the hgext directory of my Mercurial
intallation area, and add this to your ~/.hgrc file:
[extensions]
hgext.forest =
But you can put forest.py anywhere you w
The Mercurial Book at http://hgbook.red-bean.com/ provides an excellent
description of how Mercurial works in the first few chapters.
I highly recommend people look at this book.
-kto
On Oct 31, 2007, at 11:03 AM, Kelly O'Hair wrote:
A FULL jdk control build involves having the following directories:
control langtools corba jaxp jaxws hotspot j2se
And you are right, you should not need to set ALT_JDK_IMPORT_PATH
when doing
a full control build.
The ALT_JDK_IMPORT_PATH
This seems strange. The first thing it should do is build langtools, not
corba. ahh you cut out part of the log...
Once langtools is built, all other java compilations should run the BOOT jdk
with the javac.jar from the langtools build.
The trigger for this is that the corba, jaxp, jaxws, and jd
There may be a bug in the corba Makefiles.
I think the file corba/make/common/shared/Defs.gmk is missing the lines
ifdef ALT_LANGTOOLS_DIST
LANGTOOLS_DIST :=$(call FullPath,$(ALT_LANGTOOLS_DIST))
else
LANGTOOLS_DIST =
endif
But I haven't verified that 100% yet. I suspect the control Makefil
11 matches
Mail list logo
