[R-sig-Debian] gcc: error: SHLIB_LIBADD: No such file or directory

Marius Hofert marius.hofert at tum.de
Sat Jan 11 12:16:56 CET 2014


Hi,

I installed Ubuntu 13.10 on Android 4.4.2 (Nexus 5). I also
installed all the tools I have on my Desktop Ubuntu without
problems on the Nexus 5 Ubuntu. I then wanted to install R-3.0.2 (from
source). 'make' runs fine up to installing MASS:

make[2]: Entering directory `/usr/local/R/R-3.0.2-build/src/library/Recommended'
begin installing recommended package MASS
During startup - Warning messages:
1: Setting LC_CTYPE failed, using "C"
2: Setting LC_TIME failed, using "C"
3: Setting LC_MESSAGES failed, using "C"
4: Setting LC_MONETARY failed, using "C"
5: Setting LC_PAPER failed, using "C"
6: Setting LC_MEASUREMENT failed, using "C"
* installing *source* package 'MASS' ...
** package 'MASS' successfully unpacked and MD5 sums checked
** libs
make[3]: Entering directory `/tmp/Rtmpz2fzbC/R.INSTALL1ae62f487212/MASS/src'
gcc -std=gnu99 -I/usr/local/R/R-3.0.2-build/include -DNDEBUG
-I/usr/local/include    -fpic  -g -O2  -c MASS.c -o MASS.o
gcc -std=gnu99 -I/usr/local/R/R-3.0.2-build/include -DNDEBUG
-I/usr/local/include    -fpic  -g -O2  -c lqs.c -o lqs.o
gcc -std=gnu99 -shared -L/usr/local/lib -o MASSSHLIB_EXT MASS.o lqs.o
SHLIB_LIBADD
gcc: error: SHLIB_LIBADD: No such file or directory
make[3]: *** [MASSSHLIB_EXT] Error 1
make[3]: Leaving directory `/tmp/Rtmpz2fzbC/R.INSTALL1ae62f487212/MASS/src'
ERROR: compilation failed for package 'MASS'
* removing '/usr/local/R/R-3.0.2-build/library/MASS'
make[2]: *** [MASS.ts] Error 1
make[2]: Leaving directory `/usr/local/R/R-3.0.2-build/src/library/Recommended'
make[1]: *** [recommended-packages] Error 2
make[1]: Leaving directory `/usr/local/R/R-3.0.2-build/src/library/Recommended'
make: *** [stamp-recommended] Error 2
mhofert at localhost:/usr/local/R/R-3.0.2-build$

I looked for "gcc: error: SHLIB_LIBADD: No such file or
directory" and found
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679180 and
https://bugs.launchpad.net/raspbian/+bug/1007014 The problem
seems to be addressed/solved (?) some time ago, but how can one fix it?

Cheers,
Marius



More information about the R-SIG-Debian mailing list