readline detection problems
"BO" == Benjamin Otto <b.otto at uke.uni-hamburg.de> writes:
BO> Dear community, BO> I'm trying to install R-2.2.1 on an IRIX 6.2 (Unix System V Release 4) BO> system without root access. Unfortunately readline is not installed in BO> default, so I installed it locally in my home directory, more precisely in: BO> $HOME/vol/readline-5.1, where $HOME is "/home3/fa/faga001". Afterwards I BO> appended the path to the library with several $PATH variable, which now BO> looks like: BO> PATH=:/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11:/usr/local/bin:/us BO> r/freeware/bin:/usr/local/bin:.:/home3/fa/faga001/vol:/home3/fa/faga001/vol/ BO> readline-5.1:/home3/fa/faga001/vol/readline-5.1/lib Ok, on Unix-alikes, libraries and executables are treated differently; PATH is for executables only. So you're looking for something to do with libraries. BO> Still, readline is not detected by the configure script. I tried the BO> commands: BO> ./configure --with-readline="-L/$HOME/vol/readline" BO> ./configure --with-readline="/$HOME/vol/readline" BO> ./configure --with-readline=/$HOME/vol/readline If you run "./configure --help", it tells you that --with-readline takes the values 'yes' and 'no', with the default being 'yes', so you don't need to set it. BO> ./configure --x-includes="-L/$HOME/vol/readline" BO> ./configure --x-includes="/$HOME/vol/readline" This is for telling configure where to find X window system header files (.h or .hh files) BO> ./configure --x-libraries="-L/$HOME/vol/readline" BO> ./configure --x-libraries="/$HOME/vol/readline" This is for telling configure where to find X window system libraries. If you look at the R Installation and Administration help page, and search on "compilation flags" (or just search repeatedly on "readline"!), you'll find that what you want to set is the environment variable LDFLAGS -- probably like this: export LDFLAGS="-L/home3/fa/faga001/vol/readline-5.1/" or export LDFLAGS="-L/home3/fa/faga001/vol/readline-5.1/ -L/usr/local/lib" BO> trying out the different path variants which I previously included BO> in the $PATH variable. Nothing helps yet. According to printenv BO> there is currently no kind of $LIBRARY or sth. like that defined, BO> but maybe the path should rather be included in such an BO> env. variable, I didn't find any hint in the documentation. When all else fails, I resort to pulling the configure script into my favorite text editor and reading that...
Patricia J. Hawkins Hawkins Internet Applications www.hawkinsia.com