> Does the JDK still build properly if you installed X11 and do not have your
> own copy of libfreetype? I think that having the option of building with a
> non-system-provided libfreetype.dylib is a good idea, but the main nightly
> builds will continue to use X11 or XQuartz' library for the t
finally getting some attention.
>
> Regards,
> Mike Swingler
> Apple Inc.
>
> On Oct 15, 2012, at 12:53 AM, Henri Gomez wrote:
>
>> If you didn't get patch, it's available on openjdk-osx-build SVN :
>>
>> http://openjdk-osx-build.googlecode.
If you didn't get patch, it's available on openjdk-osx-build SVN :
http://openjdk-osx-build.googlecode.com/svn/trunk/patches-jdk7u-osx/freetype-osx.patch
Cheers
2012/10/15 Henri Gomez
>
> Here is a second patch.
>
> This patch a stock libfreetype.dylib (aka without
ttp://openjdk-osx-build.googlecode.com/files/OpenJDK-OSX-1.7-universal-u-jdk-u10-b09-20121015.dmg>
Thanks for new patch review
2012/10/14 Henri Gomez
> Hi to all,
>
> libfontmanager requires freetype.
> In SnowLeopard and Lion, Freetype is and since Mountain Lion
> Here's a p
Hi to all,
libfontmanager requires freetype.
In SnowLeopard and Lion, Freetype is and since Mountain Lion
Here's a patch for OpenJDK 7 and OSX to embed FreeType in build when
ALT_FREETYPE_LIB_PATH is defined.
Patch will get libfreetype.dylib under ALT_FREETYPE_LIB_PATH and copy it in
jre/lib and
> HI Henri,
>
> I recommend you try this:
>
> - for jdk8 use the "current/old" build system until jdk8 officially switches
> over to the new build system and deprecates the old one.
> - for jigsaw use the "current/old" build system until jigsaw does a merge
> from jdk8 with the new build system
>> No policy or recommendation ?
>
> I'm not sure what you are asking. Projects involving significant build
> support are moving to, or already using, the new build as that is the
> future.
I'm discussing about official recommendation by project to select new
build instead of old one.
Project by p
> Hi Henri,
>
> I don't know of any "official" policy here. The projects adding new features
> to JDK are gradually moving to the new build system in anticipation of it
> becoming the default for JDK8 "real soon now". This is true for lambda, and
> I think Jigsaw (even though no longer targeted to
Hi to all,
Yesterday I detected a build failure on latest Lambda trunk and send a
mail about problem to lambda-dev list.
Mike replied that problem is in old build system not updated to new
changes and lambda team is now using new build system.
I didn't recall seeing an official announce about de
You're right, problem appears in lambda not jdk8.
Le 16 sept. 2012 à 16:04, Alan Bateman a écrit :
> On 16/09/2012 13:39, Henri Gomez wrote:
>> For some days, I got OOM in Javadoc stages for jdk8 and lambda on Linux
>>
>> I think others build OpenJDK 8 on 32bit
For some days, I got OOM in Javadoc stages for jdk8 and lambda on Linux
I think others build OpenJDK 8 on 32bits systems could be in same
trouble and I suggest to raise it from 612m to 768m.
--- jdk/make/docs/Makefile.orig 2012-09-16 14:38:19.714697484 +0200
+++ jdk/make/docs/Makefile 2012-
I started a new site who provide OpenJDK 7/8/Lambda & Sigsaw packages
for Linux as I do allready for OSX.
http://obuildfactory.hgomez.net
These packages are built on CentOS 5/6, Fedora 16/17 and openSUSE
12.x/SLES 11.x, in 32 and 64bits to ensure compatibility.
I hope to be able to provide soon D
My build script download and install latest Ant (1.8.4) so I don't
depends on Fedora pre-requirements.
It works now that I set ALT_BOOTDIR point to a dir where there is a
Java 1.7 installed :)
2012/8/30 Andrew Hughes :
>
>
> - Original Message -
>> Hi to all,
>>
>> I could build (using ol
More on this.
Fedora 17 box missed Java 1.7 requirement but error was reported for
Ant (and not ALT_BOOT
Sorry for the noise
2012/8/30 Henri Gomez :
> Hi to all,
>
> I could build (using old build system), jdk8 on CentOS 5/6, OpenSuse
> 12.1 but it fail on Fedora 17.
>
> S
Hi to all,
I could build (using old build system), jdk8 on CentOS 5/6, OpenSuse
12.1 but it fail on Fedora 17.
Strange error where sanity report invalid ant version whereas ant
1.8.4 is installed and added to PATH.
---
UNIXCOMMAND_PATH = /bin/
ALT_UNIXCOMMAND_PATH =
COMPILER_PATH = /usr/
> The legacy build does not support building 32-bit on a 64-bit host on Linux.
> As OSX was primarily copied from linux I believe it will have the same
> problems.
>
> The new build does support building 32-bit on 64-bit (--with-data-model=32
> if I recall correctly).
New Build Infra ?
Now its --w
> Yes I fixed it :) I threw it in there because it was an issue you would have
> been familiar with. (sparcv9 already special-cased it). The general problem
> hasn't been fixed because the new build already handles it.
For OSX, I'm still using the old one for OpenJDK7 and various OpenJDK8
(lambda,
Hi to all,
I notice a strange error report on building OSX versions of OpenJDK 8,
Lambda and Jigsaw.
It seems fdlibm is built in 64bits mode :
/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc
-fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses
-pipe -m64
But linker expe
> No I haven't signed an OCA - although I'm happy to do so (or someone with an
> OCA can independently create the same changeset - it's not exactly complex).
I've got OCA signed for almost a year now :)
> WIth regards to binutils - I think you're misunderstanding things here -
> hsdis is static
nutils/libiberty/xmalloc.c
> --- binutils-2.22/libiberty/xmalloc.c 2005-05-24 17:01:33.0 -0400
> +++ binutils/libiberty/xmalloc.c 2012-04-21 18:22:02.0 -0400
> @@ -93,6 +93,11 @@
> # endif /* HAVE_STDLIB_H ... */
> #endif /* VMS */
>
> +#ifdef __APPLE__
>
> Yes, please have a look here:
> http://openjdk.java.net/projects/build-infra/guide.html
> for detailed instructions.
I took a look this afternoon.
I'll experiment it soon.
thanks
> If my understanding is correct (and I may well be wrong!) contributing the
> patch back in to binutils is most likely a no go - binutils itself builds
> fine on Mac OS because all the targets are executables, but hsdis is a
> dynamic library:
I was thinking contributing patch to OpenJDK (ie:
drik
>
> 2012/4/21 Martijn Verburg :
>> Hi Henri,
>>
>> I believe so yes, Fredrik does have a Mac after all ;-)
>>
>> Cheers,
>> Martijn
>>
>>
>> On 21 April 2012 12:34, Henri Gomez wrote:
>>>
>>> New build system has be
New build system has been tested allready on OSX ?
Le 21 avr. 2012 à 09:10, Fredrik Öhrström a écrit :
> For the new build you have to explicitly choose release,fastdebug or
> slowdebug.
> (--with-debug-level=release,fastdebug or slowdebug)
> So you do not need to turn off fastdebug, it default
easily be done manually with just a few commands but it
>> would be of course much better if you could provide a patch for the
>> Makefile:)
>>
>>
>> On Fri, Apr 20, 2012 at 6:52 PM, Henri Gomez wrote:
>>> I'll look into build logs (thanks Jenkins)
&g
gt; ALT_OUTPUTDIR= make jvmg
> ALT_BOOTDIR=
> ALT_OUTPUTDIR= make fastdebug
>
> for the debug and fastdebug case.
>
> Or you can try to find out why SKIP_FASTDEBUG_BUILD=false hasn't been
> properly propagated into the HotSpot make file:)
>
> Regards,
> Volk
To: "Rémi Forax"
>
> Cc:
> Subject: OpenJDK 8 and fastdebug
> Date: Fri, Apr 20, 2012 08:55
>
>
> PrintAssembly is available in product builds, too. You'll just need to set
> -XX:+UnlockDiagnosticVMOptions before setting -XX:+PrintAssembly.
>
> On the oth
> Just set
>
> SKIP_FASTDEBUG_BUILD=false
>
> (I don't know what role DEBUG_NAME plays)
>
>
>> Relative question, how can I check a java exec is in fastdebug mode ?
>
>
> Check "java -version", it will show it is fastdebug.
It seems good
(http://openjdk-osx-build.googlecode.com/files/OpenJDK-OSX-
Hi to all,
I'd like to activate fast debug for some of OSX packages produced for
Java 8, jigsaw and lambda.
What's correct way to do it at make time ?
DEBUG_NAME=something SKIP_FASTDEBUG_BUILD=false ?
Relative question, how can I check a java exec is in fastdebug mode ?
Thanks
on macosx!! I'm waiting for the jprt job to complete the
> sanity checks on all platforms including OSX. Then I will sponsor and push
> the changesets to jigsaw for Michael.
>
> Mandy
>
>
> On 4/5/2012 1:07 PM, Henri Gomez wrote:
>>
>> Did there is plan to
> This was a notification that the HotSpot component integrated
> for jdk8-b33. HotSpot is only one of many repos that make up
> the OpenJDK...
Yep I know :)
Did there is plan to merge current jdk8 to jigsaw branch ?
I know some OSX users waiting it to experiment with modules :)
Cheers
ok, it wasn't clear
2012/4/5 Daniel D. Daugherty :
> That's because jdk8-b33 hasn't promoted yet...
>
> Dan
>
>
>
> On 4/5/12 1:43 PM, Henri Gomez wrote:
>>
>> hg tags still return jdk8-b32.
>>
>> tip
hg tags still return jdk8-b32.
tip 417:42f275168fa5
jdk8-b32 416:88176171e940
jdk8-b31 415:0b66f43b89a6
jdk8-b30 414:6cea54809b51
jdk8-b29 410:41460de04258
2012/4/4 John
For OSX, It's available on openjdk-osx-build site :
http://openjdk-osx-build.googlecode.com/files/OpenJDK-OSX-8-x64-jdk-b32-20120330.dmg
http://openjdk-osx-build.googlecode.com/files/OpenJDK-OSX-8-x64-jre-b32-20120330.dmg
JDK8 with Lambda also available there
2012/3/30 Roger Yeung :
> Hi Dav
35 matches
Mail list logo
