On 26 Oct 2014, at 14:07, Alexander Hansen <alexanderk.han...@gmail.com> wrote:
> On 10/26/14, 4:34 AM, Viv Kendon wrote: >> >> On 26 Oct 2014, at 01:13, Alexander Hansen <alexanderk.han...@gmail.com> >> wrote: >> >>> On 10/25/14, 3:16 PM, Viv Kendon wrote: >>>> >>>> On 25 Oct 2014, at 22:43, Viv Kendon <v...@trellick.net> wrote: >>>> >>>>>> <snip> >>>>> >>>>> On 25 Oct 2014, at 22:01, Alexander Hansen <alexanderk.han...@gmail.com> >>>>> wrote: >>>>>> >>>>>> The if-then that you fixed was _supposed_ to copy that over for 10.9 and >>>>>> later. As a workaround, maybe start a rebuild of octave364-atlas-x11, >>>>>> stop it after the patch phase, and manually do a >>>>>> >>>>>> sudo cp >>>>>> /sw/src/fink.build/octave-3.6.4-11/octave-3.6.4/liboctave/libcxx-fix.h >>>>>> /sw/include/octave-3.6.4/octave/ >>>>> >>>>> Many thanks, I did that, then restarted fink install bundle-octave-atlas. >>>>> It went through the oct364 packages in alphabetical order, so here is >>>>> how it dies for java: >>>>> >>>>> ans = >>>>> /sw/src/fink.build/java-oct364-1.2.9-3/bld/share/octave/3.6.4/packages >>>>> mkdir (/var/tmp/oct-l9vVbi) >>>>> untar (./java.tar, /var/tmp/oct-l9vVbi) >>>>> >>>>> Error while trying to install Java package: >>>>> JAVA_HOME environment variable does not properly point to a JDK >>>>> Hint: >>>>> JAVA_HOME should usually be set such that either: >>>>> (on *nix:) >>>>> <JAVA_HOME>/jre/lib/<arch>/client/ contains libjvm.so (file or symlink) >>>>> (on OSX:) >>>>> <JAVA_HOME>/../Libraries/ contains a file libclient.dylib >>>>> (on Windows:) >>>>> <JAVA_HOME>/jre/lib/<arch>/ contains a file jvm.cfg >>>>> (<arch> depends on your system hardware, can be i386, x86_64, alpha, >>>>> arm, ...) >>>>> >>>>> Use forward slashes as path separator, also on Windows >>>>> Aborting pkg install >>>>> error: called from 'pre_install' in file >>>>> /private/var/tmp/oct-l9vVbi/java/pre_install.m near line 115, column 5 >>>>> error: called from: >>>>> error: /sw/share/octave/3.6.4/m/pkg/pkg.m at line 827, column 5 >>>>> error: /sw/share/octave/3.6.4/m/pkg/pkg.m at line 383, column 9 >>>>> error: /sw/src/fink.build/java-oct364-1.2.9-3/java/octave-forge-comp at >>>>> line 4, column 1 >>>>> >>>>> I then manually verified that octcdf-nc4-oct364 now installs fine. >>>>> >>>>> Will I need to manually copy libcxx-fix.h for octave382 as well? And is >>>>> the file identical to the octave364 copy, or do I need to start a rebuild >>>>> for octave382 to get the corresponding file? >>>>> >>>> >>>> I tried a few oct832 packages (without doing anything about libcxx-fix.h >>>> for octave382) and they all seem to die in the same way with a java error >>>> that is very different from the above: >>>> >>>> mkdir -p bld/share/octave/3.8.2/packages bld/lib/octave/3.8.2/packages >>>> `which xvfb-run` >>>> /sw/src/fink.build/optiminterp-atlas-oct382-0.3.4-3/optiminterp/octave-forge-comp >>>> which xvfb-run >>>> No Java runtime present, requesting install. >>>> 2014-10-25 23:07:33.340 octave-cli-3.8.2[45245:d07] >>>> JLRequestRuntimeInstall: Error calling: CFMessagePortCreateRemote >>>> ### execution of /tmp/fink.zx8W6 failed, exit code 97 >>>> Removing runtime build-lock... >>>> Removing build-lock package... >>>> /sw/bin/dpkg-lockwait -r fink-buildlock-optiminterp-atlas-oct382-0.3.4-3 >>>> >>>> >>>> java -version >>>> java version "1.7.0_51" >>>> Java(TM) SE Runtime Environment (build 1.7.0_51-b13) >>>> Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) >>>> >>>> Package manager version: 0.38.1 >>>> Distribution version: selfupdate-rsync Sat Oct 25 22:57:26 2014, 10.9, >>>> x86_64 >>>> Trees: local/main stable/main >>>> Xcode.app: 6.0.1 >>>> Xcode command-line tools: 6.0.0.0.1.1410400753 >>>> >>>> >>>> Anyway, it is end of the day here. Happy to keep testing tomorrow, if it >>>> would be useful. >>> >>> Thanks for testing! >> >> You are welcome, happy to help. >> >>> The libcxx-fix.h files are the same for both Octave versions. It may well >>> be present for your octave382 build, though--more bad shell scripting in >>> the 364 version from me which wasn't present in the 382 version. >> >> I do indeed have the 382 version correctly installed by fink. I just >> rebuilt octave364-atlas-x11 since it showed as outdated but libcxx-fix.h >> still did not get installed by fink as it should be (I moved my manually >> copied version aside before rebuilding). And >> >> dpkg -S libcxx-fix.h >> octave382-atlas-x11-dev: /sw/include/octave-3.8.2/octave/libcxx-fix.h >> >> only reports the 382 version. >> >> Let me know if I can test/try anything else. >> >> many thanks, >> — Viv >> >> > > Anything you want to build would be helpful. :-) > > I fixed the octave364 build last night so it installs everything it should. > I'm in the process of getting octave382 up on 10.10 with tweaked dependencies > to avoid installing Apple's legacy Java to see what happens there. octave364 still didn’t install that pesky libcxx-fix.h on my system. In fact, there are no files at all in that directory /sw/include/octave-3.6.4/octave/ Could it be a case-sensitive file system problem? But I can confirm that octave382 builds on 10.9 (with the java dependency changed from 1.6 to 1.7) using your latest file which has one extra 1.6 that I changed in a local copy. And that trying to install oct382 packages fails to find the JRE with the same error as before. many thanks, — Viv ------------------------------------------------------------------------------ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
