Message-ID: <4A2651CA-8F99-4708-AD9F-6A50E59C9206@r-project.org>
Date: 2006-04-20T20:51:43Z
From: Simon Urbanek
Subject: plier source compilation error related to dylib
In-Reply-To: <9CD93529-283B-483D-AFF8-2DDD00AF9CCE@mac.com>
On Apr 20, 2006, at 2:25 PM, S Kong wrote:
> [Quad:~/Desktop/pliersrc] skong% R64 CMD SHLIB affyplier.cpp
> plieralg.cpp plier_impl.cpp rwrapper.cpp
> g++ -no-cpp-precomp -I/usr/local/lib64/R/include -I/usr/local/
> include -fno-common -arch ppc64 -m64 -mcpu=G5 -mtune=G5 -
> mpowerpc-gpopt -force_cpusubtype_ALL -c plieralg.cpp -o plieralg.o
> g++ -no-cpp-precomp -I/usr/local/lib64/R/include -I/usr/local/
> include -fno-common -arch ppc64 -m64 -mcpu=G5 -mtune=G5 -
> mpowerpc-gpopt -force_cpusubtype_ALL -c plier_impl.cpp -o plier_impl.o
> g++ -no-cpp-precomp -I/usr/local/lib64/R/include -I/usr/local/
> include -fno-common -arch ppc64 -m64 -mcpu=G5 -mtune=G5 -
> mpowerpc-gpopt -force_cpusubtype_ALL -c rwrapper.cpp -o rwrapper.o
> g++ -bundle -flat_namespace -undefined suppress -m64 -L/usr/local/
> lib -L/usr/local/lib64/R/lib -o affyplier.so affyplier.o plieralg.o
> plier_impl.o rwrapper.o -L/usr/local/lib64/R/lib -lR
> ld64 warning: indirect library libgfortran.0.dylib could not be
> loaded: file not found: libgfortran.0.dylib
> ld64 warning: indirect library libgcc_s.1.0.dylib could not be
> loaded: file not found: libgcc_s.1.0.dylib
> ld64 warning: indirect library libreadline.5.dylib could not be
> loaded: file not found: libreadline.5.dylib
Yes, that is already better :). However, those should be just
warnings, not errors - does affyplier.so exist? Once R is started,
the DYLIB_LIBRARY_PATH is set and dyld should find the libraries.
If not, then it really depends on your compilers - check libR.dylib
and the others in /usr/local/lib64/R/lib with otool64 -L to see where
they are actually expected. If in doubt, send me the output of
otool64 -L /usr/local/lib64/R/lib/*
and
otool64 -L /usr/local/lib/libg*
Cheers,
Simon