Hi All
Just install Win 2008 and VS.NET 2008 this afternoon and try to build
JDK. There're 2 tiny issues:
1. cl.exe's version is 15., not recognized by Compiler-msvc.gmk.
Duplicate the MS.NET 2003 lines in the file to accept 15.
2. MSVCDIR is not defined in VS.NET 2008's vcvars.bat. I
I see no reason to build on Win 2008. Yes, someday it should work, but
anything you build is suspect because the official JDK7 builds will
eventually be done on Windows XP.
You could end up tracking down problems that are unique to building on
Win 2008 and have no value to the official JDK7 releas
Kelly O'Hair wrote:
I see no reason to build on Win 2008. Yes, someday it should work, but
anything you build is suspect because the official JDK7 builds will
eventually be done on Windows XP.
You could end up tracking down problems that are unique to building on
Win 2008 and have no value to the
Erik Trimble wrote:
As a followup to this: we're looking at moving to Windows XP w/ VS.Net
2008 as the new default Windows 32-bit build platform. Windows 2003 is
likely to remain the 64-bit Windows platform for quite some time. I do
expect that we will want to update the MS SDK on both
Erik Trimble wrote:
Also, Cygwin is the UNIX-ism platform of choice, and getting the JDK
to build solely with Cygwin (on both 32- and 64-bit, Win2k, WinXP, and
Win2003) would be a _huge_ deal.
I.e. using the gcc provided by Cygwin and the 'posixy' libc it provides?
cheers,
dalibor topic
--
*
That would be interesting, but a very big rock.
---
I'm remembering a seminar I took a long time ago, the same one that
Harvey is talking about here:
http://www.harveymackay.com/columns/best/11.cfm
Although I remember it being a bucket, not a jar.
You need to put the big rocks in the bucket f
Dalibor Topic wrote:
Erik Trimble wrote:
Also, Cygwin is the UNIX-ism platform of choice, and getting the JDK
to build solely with Cygwin (on both 32- and 64-bit, Win2k, WinXP,
and Win2003) would be a _huge_ deal.
I.e. using the gcc provided by Cygwin and the 'posixy' libc it provides?
cheer
Erik Trimble wrote:
Dalibor Topic wrote:
Erik Trimble wrote:
Also, Cygwin is the UNIX-ism platform of choice, and getting the JDK
to build solely with Cygwin (on both 32- and 64-bit, Win2k, WinXP,
and Win2003) would be a _huge_ deal.
I.e. using the gcc provided by Cygwin and the 'posixy' lib
Porting OpenJDK to be an actual cygwin program,
rather than just being built using cygwin tools,
is an obvious target for open source porters.
The cygwinized OpenJDK would be available as part of the Cygwin
distribution. Obviously a porter would have to fight with
many assumptions currently being
I installed the Linux JREs for 6u10 b28,
(using java -jar jre..jar)
and was surprised to discover none of the
programs (like "bin/java") were executable.
I checked earlier 6u10 builds,
and they have the same problem.
I suspect the jdk7 builds also have this problem.
This seems like a P1 deploy
Hi Martin,
this is a known problem and it it noticed at the top of the download
page at http://download.java.net/jdk6/ :
"If you choose to download and install self-extracting JRE or DEBUG
Jar bundles then you need to change the file permission to be
executable in the bin directory after the inst
11 matches
Mail list logo
