thanks for your help. Your suggestion to use "LDCMD=cc SHLIBLD=cc"
for configure worked, I've got a working R again :-)
And got me confused.
Ideally, I'd like to use the C compiler (rather than ld) for linking the
main binary as well as shared libs, so overriding should only occur if
there is a good reason. I assume that there was one for aix, but from
the above maybe it is gone now?
Users of current r-devel snapshots on AIX, can you confirm that
MAINLD=cc SHLIBLD=cc /path/to/configure
make
works o.k.? (Or actually, use your C compiler rather than `cc' ...)
Other roadblocks I've encountered (and the reason I cc: r-devel):
-- ld/cc doesn't automatically include /usr/local/lib while gcc does.
This comes from the sytem installation here and has nothing to do with
R. But having to add LIBS=-L/usr/local/lib may come as a surprise to
people who don't do this regularly.
Does configure check for the existence of e.g. libz.a with cc or gcc?
It uses the C compiler specified.
Well, LIBS is needed when you have things in `non-standard' locations.
Of course your mileage may vary on the definition of non-standard :-)
Is there anything I/configure could do about this? (Note that I don't
think that unconditionally adding /usr/local/lib to LIBS is a good
idea.)
-- the installation fails when I try to build in a special
subdirectory. install-sh can't be found. I've edited the Makefile to
use "build/tools/../$(INSTALL_DATA)". (I guess build/$(INSTALL_DATA)
would be enough.) I believe this worked on a sun. Is this a
consequence of overriding install-sh on AIX in configure?
I need more info on that. configure does two fixing steps after using
the standard autoconf code for determining a BSD compatible install: if
we end up with the script, then make sure its path is absolute. I think
this is needed and should work. Secondly, on platforms where the code
was known to give something that would not work, use the script in any
case. Maybe the latter can be avoided with the most recent autoconf
code.
What exactly is the failure you observe?
-- demo.so is not installed and demo(dyn.load) fails. This is a
trivial matter if detected before 'rm -rf build' ...
Why is that?
-k
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
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: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._