> Marcus G Daniels writes:
> Prof Brian Ripley wrote:
>> Some of them use Fortran, please note, and libtool is none too good at
>> that.
> I didn't have an (obvious) problem with that. I did notice that
> DYLIB_* variables in Makeconf.in didn't have USE_LIBTOOL_TRUE/FALSE
> conditionalizati
Prof Brian Ripley wrote:
Has anyone looked at setting up R to build its modules with libtool's
dlpreopen?
[libtool -dlpreopen is a facility that allows one to simulate dynamic
linking on platforms that lack it.
No current R platform does.
The static linking workarounds are for a Cray MTA/2, a mu
Prof Brian Ripley wrote:
Some of them use Fortran, please note, and libtool is none too good at
that.
I didn't have an (obvious) problem with that. I did notice that DYLIB_*
variables in Makeconf.in didn't have USE_LIBTOOL_TRUE/FALSE
conditionalizations. That was a place it broke for me with F
Yes.
Some of them use Fortran, please note, and libtool is none too good at that.
Not sure why this merited sending twice
On Wed, 2 Feb 2005, Marcus G. Daniels wrote:
Has anyone looked at setting up R to build its modules with libtool's
dlpreopen?
[libtool -dlpreopen is a facility that allow
Has anyone looked at setting up R to build its modules with libtool's
dlpreopen?
[libtool -dlpreopen is a facility that allows one to simulate dynamic
linking on platforms that lack it. However, it requires collecting all
of the component `shared' objects into one and linking them (and a
meta
Has anyone looked at setting up R to build its modules with libtool's
dlpreopen?
[libtool -dlpreopen is a facility that allows one to simulate dynamic
linking on platforms that lack it. However, it requires collecting all
of the component `shared' objects into one and linking them (and a
meta
