On Nov 4, 2014, at 11:07 AM, David Fang <f...@csl.cornell.edu> wrote:
> Hi all, > Sitting in my experimental tree is a draft of llvm35's packaging > that bootstraps (much like its predecessor llvm34), but fails Shlib > validation because the install_names for shlibs all start with @rpath (or > on older darwin @executable_path or @loader_path). This was a decision by > upstream build maintainers that allows this package to be > binary-relocatable, even though fink makes no such guarantees about its > packages -- fink's remain in fixed install locations. > dmacks and akh began to look into a patch that would allow this to pass > validation. Can you guys comment on the status/issues/obstacles? > Such a fix would unblock llvm35 from hitting dists. > > Thanks! > > Fang > > -- > David Fang > http://www.csl.cornell.edu/~fang/ > > This also could avoid annoyances with packages that link to java stuff (yeah, I know they’re not supposed to do that, but some upstreams don’t get it) since the install_names there use @rpath, too, and there isn’t an unversioned link that points to the latest installed Java version: $ otool -L /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre/lib/server/libjvm.dylib /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/jre/lib/server/libjvm.dylib: @rpath/libjvm.dylib (compatibility version 1.0.0, current version 1.0.0) If the upstream build uses rpath properly then we wouldn’t have to worry about having potentially non-identical paths for different builds. -- Alexander Hansen, Ph.D. Fink User Liaison
------------------------------------------------------------------------------
_______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
