[Rd] Re: [R] Newbie questions
Sun, 5 Nov 2000 09:06:25 +0100 (CET)
>>>>> Peter Dalgaard BSA writes:
> Zsombor Cseres-Gergely <firstname.lastname@example.org> writes:
>> There is something with the hurd ld.so, but I do not know, what. But I
>> 1) run 'make test' with --gui=none. It went up till dies with
>> > library("eda") # returns invisibly
>> Error in dyn.load(x, as.logical(local), as.logical(now)) :
>> unable to load shared library "/home/zs/R-1.1.1/library/eda/libs/eda.so":
>> /home/zs/R-1.1.1/library/eda/libs/eda.so: undefined symbol: R_rsort
>> Error in library("eda") : .First.lib failed
>> Execution halted
> OK, so that shows that dynamic loading doesn't work.
>> 3) sent a message to the Hurd folks. One reply was this:
>> <quote on>
>> The correct linker options for this sort of issue are the same as on Linux.
>> Perhaps their build scripts behave differently on Linux than on Hurd. It
>> sounds like they expect to link the main executable with --export-dynamic
>> (aka -E). Use nm --dynamic or objdump --dynamic-syms to see what symbols
>> are defined in the executable on Linux and on Hurd.
>> <quote off>
> Aha... Actually watching the link step during make would probably show
> that -export-dynamic is not among the options. The codes that inserts
> that flag during configure would seem to be (in configure or configure.in)
> which likely will not trigger on the Hurd... In the longer run we
> should fix configure, but on a short term, you can fix this by setting
> MAIN_LDFLAGS = -export-dynamic
> in Makeconf. (It would seem to be spelled with a single hyphen, for
> some oddball reason).
Actually, can you try a current snapshot of R-devel?
I am in the process of converting all shlib stuff to GNU libtool which
is now used by default ... and I think this change should make Peter's
suggestion happen automagically ...
Thanks && waiting for your findings,
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !) To: email@example.com