Thanks for taking the time to look at this Uwe. Turns out the
problem was caused by the fact that foo.so was built with
incorrect linker options (not pointing to bar.so), so there were
undefined symbols. Why it worked at all is a puzzle.
2010/5/22 Uwe Ligges
> - Does bar really dyn.load its shar
- Does bar really dyn.load its shared library on load?
- Have you told package foo (in the DESCRIPTION) it is LinkingTo: bar ?
Uwe Ligges
On 21.05.2010 22:35, Dominick Samperi wrote:
Hello,
I am observing the following strange behavior when I try to
load a shared library using dyn.load() und
Hello,
I am observing the following strange behavior when I try to
load a shared library using dyn.load() under Linux...
The library foo.so refers to a symbol in another package bar
(with shared library bar.so), I get:
dyn.load('foo.so') # error message because I forgot to load bar
library(bar)
