I am in the process of preparing llvm and
llvm-gcc-4.2 packaging for the new llvm 2.5
release (which finally has a usable gfortran
that passes the Polyhedron benchmarks). The
packaging uses the Xcode 3.1 linker in
/Developer/usr/bin so that the LTO is available
at -O4 in the compilers. I am also packaging
the libLTO.dylib which is built as part of
llvm in a llvm-shlibs so that users can replace
Apple's version with that copy. The newer libLTO.dylib
allows for complete LTO support rather than just
dead code elimination.
The fink maintainer mode is confused by
libLTO.dylib because it's otool -L output shows...
libLTO.dylib:
@executable_path/../lib/libLTO.dylib (compatibility version 1.0.0,
current version 2056.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version
1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.0.0)
Fink should understand that Apple considers the use of
@executable_path/../lib/libLTO.dylib
as a valid path for the shared library.
Jack
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
