openjdk-osx-build

[Henri Gomez]

> I think I used yours before for a little while. Usually I have used ones I've built. I think I have for the most part stayed away from the system directory instead placing the bundle in the user one. ~/Library/Java/JavaVirtualMachines/1.7.0.jdk

It could be on /Library/Java/JavaVirtualMachines/1.7.0.jdk or
~/Library/Java/JavaVirtualMachines/1.7.0.jdk

> Incidentally, since Java Preferences is supposed to provide support for multiple jds's a little while back I tried having two there. One renamed something like current_1.7.0.jdk but it didn't get picked up in Java Preferences that i saw.

Hum, I never tried to rename a folder to see if JavaPrefs take care of it.

> For yours I just tried running the installer indicating single user. It didn't appear to replace the one I had there. Unless Finder just wasn't updating the file information. I finally deleted or moved the one I had there, ran your installer and then appeared to get it.

Did you select install for the user or all users ?

>>>> - OS/X 10.6.7 in 64bits mode (Darwin imac-hgomez-exo 10.7.0 Darwin
>>
> Mine is a build I've had to tweak to get to run in 32 bit mode. I also hacked it to get around some symlink problems pointed out by the jobjc changeset  Missing the current Developer tools apparently.
> 10.6.6 until I noticed you had 10.6.7 and ran Software Update to get that.
> XCode 3.2.6 since the symlink problem, 3.2.1 previously I think
> Java 1.6.0_24 since available.
> 32 bit Core Duo MacBook.

What's the tweaks for build on 32bits mode ?

> I mean when I tried compiling with my own last build I got 100+ compile errors. Unusable.
> Unfortunately when I tried yours it still got two compile errors. I thought with a quck look yesterday morning that these were normal ones I could deal with. But, looking closer one I had seen before with a prior build, which is why I tried swapping to the jobjc build jdk - which was worse. I posted the information for that in a "Strange compile error" post yesterday.
> At least the fact I got the same error reproduced with your build sort of eliminates it being just my own build messed up somehow. I might guess a 32 bit thing since I think most people aren't using that. Given no further suggestions on how to proceed with that I will just bug report it I guess. Also unfortunately that one compile error is probably enough to make the current build unusable for development. I will when I get a chance maybe see if I can backout to a earlier one that works or try switching back to the bsd-port to get one to work with.

Could you provide the build errors ?

> I just wanted to give you some notification that your installer seemed to not work the way that I am sort of used to them functioning. As it was it appeared to do nothing without giving any messages that it didn't succeed.

Very strange. What installation did you select ? User or All Users ?