./configure
CFLAGS="-isysroot /Developer/SDKs/MacOSX10.5.sdk
-arch ppc -arch i386 -arch x86_64 -arch ppc64"
LDFLAGS="-Wl,-syslibroot,/Developer/SDKs/MacOSX10.5.sdk
-arch ppc -arch i386 -arch x86_64 -arch ppc64"
--enable-shared --disable-dependency-tracking --prefix=/usr
make
make install
sh-3.2# file /usr/lib/libxslt.1.1.24.dylib
/usr/lib/libxslt.1.1.24.dylib:
Mach-O universal binary with 4 architectures
/usr/lib/libxslt.1.1.24.dylib (for architecture ppc7400):
Mach-O dynamically linked shared library ppc
/usr/lib/libxslt.1.1.24.dylib (for architecture i386):
Mach-O dynamically linked shared library i386
/usr/lib/libxslt.1.1.24.dylib (for architecture x86_64):
Mach-O 64-bit dynamically linked shared library x86_64
/usr/lib/libxslt.1.1.24.dylib (for architecture ppc64):
Mach-O 64-bit dynamically linked shared library ppc64
Thrown if an application attempts to access or modify a field, or to call a method that it does not have access to.
Normally, this error is caught by the compiler; this error can only occur at run time if the definition of a class has incompatibly changed.
(
ref.)
... identifying the class in the Extensions and adjusting/removing the corresponding .jar should help. Anyways, don't understand why packing dependencies within the same jar as the actual one of a library.
Posted in:
Programming |
OSX After the occurrence of errors like:
configure: error: no acceptable C compiler found in $PATH or configure: error: C compiler cannot create executables even though gcc got updated to version 4.*, the following did help:
- Reinstalling XCode tools
- Cleaning and upgrading the ports collection:
~# port selfupdate
~# port -d sync
~# portindex
~# port --all clean all
~# port upgrade installed
