Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-06 Thread Christian Lohmaier
Hi *, On Mon, Dec 6, 2010 at 2:21 PM, Wols Lists wrote: > On 06/12/10 12:57, Norbert Thiebaud wrote: > > The problem as I saw it was making sure Mac still went through the old > path first, because findhome is successful but returns a dud path. Yes - having the Mac check first is perfectly fine,

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-06 Thread Norbert Thiebaud
Ok, I pushed a new version that should be doing 'The Right thing(tm)' on MacOS It is still doing the readlink stuf on other platforms... Norbert On Mon, Dec 6, 2010 at 7:21 AM, Wols Lists wrote: > On 06/12/10 12:57, Norbert Thiebaud wrote: >>> Hmm - but the result of the IRC-discussion was to u

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-06 Thread Wols Lists
On 06/12/10 12:57, Norbert Thiebaud wrote: >> Hmm - but the result of the IRC-discussion was to use (for Mac) >> > /usr/libexec/java_home where available (10.5 and newer), and the >> > hardcoded fallbackpath of either >> > /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home >> > or

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-06 Thread Norbert Thiebaud
On Mon, Dec 6, 2010 at 6:53 AM, Christian Lohmaier wrote: > Hi Norbert, *, > > On Mon, Dec 6, 2010 at 8:28 AM, Norbert Thiebaud wrote: >> On Sun, Dec 5, 2010 at 9:39 PM, Thorsten Behrens >> wrote: >>> Caolan McNamara wrote: IIRC I tried this before, and there was some cockup under MacOSX, s

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-06 Thread Christian Lohmaier
Hi Norbert, *, On Mon, Dec 6, 2010 at 8:28 AM, Norbert Thiebaud wrote: > On Sun, Dec 5, 2010 at 9:39 PM, Thorsten Behrens > wrote: >> Caolan McNamara wrote: >>> IIRC I tried this before, and there was some cockup under MacOSX, so if >>> someone on MacOSX could see what findhome says and if its c

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-06 Thread Caolán McNamara
On Mon, 2010-12-06 at 01:28 -0600, Norbert Thiebaud wrote: > Cloph, Wol and me have been working on it on IRC, resulting in > bootstrap:474e4b60fec1f859bc16f268d6340d7850c7874e Well, if it works it works. Still think that all the readlink stuff before trying findhome.java is fairly dubious and tha

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-05 Thread Norbert Thiebaud
On Sun, Dec 5, 2010 at 9:39 PM, Thorsten Behrens wrote: > Caolan McNamara wrote: >> IIRC I tried this before, and there was some cockup under MacOSX, so if >> someone on MacOSX could see what findhome says and if its correct/wrong >> vs what works correctly there, that'd be helpful. >> > About 4k

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-05 Thread Thorsten Behrens
Caolan McNamara wrote: > IIRC I tried this before, and there was some cockup under MacOSX, so if > someone on MacOSX could see what findhome says and if its correct/wrong > vs what works correctly there, that'd be helpful. > About 4k miles away from my MacBook currently - Norbert, Cloph, any chanc

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-05 Thread Wols Lists
On 05/12/10 20:40, Caolán McNamara wrote: > On Sun, 2010-12-05 at 17:24 +, Wols Lists wrote: >> Yup. findhome found the right place (or I assume it did). >> >> /opt/icedtea6-bin-1.9.1 > Yeah, so what I'd like to see is that findhome (or something like it) is > the normal way to get the jdk home

Re: [Libreoffice] Java build problem identified | findhome | MacOSX location ?

2010-12-05 Thread Caolán McNamara
On Sun, 2010-12-05 at 17:24 +, Wols Lists wrote: > Yup. findhome found the right place (or I assume it did). > > /opt/icedtea6-bin-1.9.1 Yeah, so what I'd like to see is that findhome (or something like it) is the normal way to get the jdk home when one is not set via the --with-jdk-home. And