Re: new problem: libjava.dylib: image not found -- but it is there

On Jan 27, 2010, at 2:03 PM, Greg Lewis wrote: >> The $ORIGIN hack seems like the sort of thing which Mac OS X would do >> better; does anyone know the Mac or BSD story here? >> >> The original version of the BSD file omits mention of LD_RUNPATH_EXTRAS, >> while the original version of linux and

Re: new problem: libjava.dylib: image not found -- but it is there

On Tue, Jan 26, 2010 at 06:16:35PM -0800, John Rose wrote: > One of the significant differences between the makefiles for linux and bsd is > this: > > -ifdef LIBRARY > - # Libraries need to locate other libraries at runtime, and you can tell > - # a library where to look by way of the dynamic

Re: new problem: libjava.dylib: image not found -- but it is there

On Jan 26, 2010, at 8:52 PM, John Rose wrote: > this is what happens in the end Oops... That was because I was doing incremental rebuilds. Actually, those makefile changes seem to do the trick: > Here are my makefile changes so far (relative to a $davinci installation). > It is pretty crude

Re: new problem: libjava.dylib: image not found -- but it is there

On Jan 26, 2010, at 6:41 PM, Mike Swingler wrote: > Also, the bin tools need to have "push rpath" directives as well, so you'll > probably need to experiment with a number of different paths to find a > combination that builds a coherent JDK. I did some experimentation and got something that bu

Re: new problem: libjava.dylib: image not found -- but it is there

The BSD Makefile should definitely specify some link directives. On Mac OS X, dyld uses a stack of "rpath" directives that are pushed by each library that is loaded (the dyld man page has more info in the "DYNAMIC LIBRARY LOADING" section). We have recently started building the Apple JDK with @

Re: new problem: libjava.dylib: image not found -- but it is there

One of the significant differences between the makefiles for linux and bsd is this: -ifdef LIBRARY - # Libraries need to locate other libraries at runtime, and you can tell - # a library where to look by way of the dynamic runpaths (RPATH or RUNPATH) - # buried inside the .so. The $ORIGIN

Re: new problem: libjava.dylib: image not found -- but it is there

I asked around at the office, and here's a possible root of the problem: http://hg.openjdk.java.net/bsd-port/bsd-port/jdk/rev/de45eac5670e The launcher (java.c in the jdk repo) used to re-exec itself with LD_LIBRARY_PATH bindings, so the libjvm and libjava DLLs could find each other. This tri

Re: new problem: libjava.dylib: image not found -- but it is there

I built JDK7 today based on these instructions http://wikis.sun.com/display/OpenJDK/Darwin9Build I'm experiencing the same problem. One possible clue is that the libjava.dylib files itself doesn't appear to be the problem. This is the lates

Re: new problem: libjava.dylib: image not found -- but it is there

I built JDK7 today based on these instructions http://wikis.sun.com/display/OpenJDK/Darwin9Build I'm experiencing the same problem. David On Mon, Jan 18, 2010 at 6:39 PM, Ugo Kanain wrote: > I have been unable to use openjdk because of the same issue. This seems to > be a problem with how it w

Re: new problem: libjava.dylib: image not found -- but it is there

I have been unable to use openjdk because of the same issue. This seems to be a problem with how it was built on 10.5 (though the intel flavor seems to have been more successful than the ppc). On another thread, Mike suggests using the LC_RPATH compiler directive. Though I wasn't able to m