collect2: cannot find `ld' - problem on installing alsa-oss

satimis · 09-10-2005, 03:06 AM

Hi folks,

BLFS 6.1

On installing alsa-oss-1.0.9 problem was encountered on "make install"

Steps performed as follows;

$ tar -jxf alsa-oss-1.0.9.tar.bz2
$ cd alsa-oss-1.0.9
$ ./configure &&
> make

Code:

.....
creating libossredir.la
(cd .libs && rm -f libossredir.la && ln -s ../libossredir.la
libossredir.la)
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/oss-redir'
Making all in test
make[1]: Entering directory `/sources/alsa-oss-1.0.9/test'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/test'
make[1]: Entering directory `/sources/alsa-oss-1.0.9'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/sources/alsa-oss-1.0.9'

$ su
Password:
# make install

Code:

Making install in alsa
make[1]: Entering directory `/sources/alsa-oss-1.0.9/alsa'
make[2]: Entering directory `/sources/alsa-oss-1.0.9/alsa'
....
collect2: cannot find `ld'
libtool: install: error: relink `libaoss.la' with the above command
before installing it
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/sources/alsa-oss-1.0.9/alsa'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/alsa'
make: *** [install-recursive] Error 1

# ls -al /usr/bin/ld

Code:

-rwxr-xr-x  1 root root 360462 Aug  5 18:57 /usr/bin/ld

"ld" was there. Please advise.

TIA

BR
satimis

kjordan · 09-10-2005, 10:28 AM

Do an echo $PATH after you su. If the PATH is incomplete, either use "su -" which makes it a login shell, or after you use just "su", do a source /etc/profile.

satimis · 09-10-2005, 10:57 AM

Hi kjordan,

bash-3.00$ su
Password:
root@localhost:/home/satimis# echo $PATH

Code:

/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.

root@localhost:/home/satimis# source /etc/profile
No printout

root@localhost:/home/satimis# exit
exit
bash-3.00$ su -
Password:
root@localhost:~# echo $PATH

Code:

/usr/local/sbin:/usr/local/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin

BR
satimis

kjordan · 09-10-2005, 11:00 AM

Try make install now.

satimis · 09-10-2005, 11:14 AM

Quote:

Originally posted by kjordan
Try make install now.

root@localhost:~# cd /sources/alsa-oss-1.0.9
root@localhost:/sources/alsa-oss-1.0.9# make install

Code:

Making install in alsa
make[1]: Entering directory `/sources/alsa-oss-1.0.9/alsa'
make[2]: Entering directory `/sources/alsa-oss-1.0.9/alsa'
/bin/sh ../mkinstalldirs /usr/bin
 /bin/install -c aoss /usr/bin/aoss
/bin/sh ../mkinstalldirs /usr/lib
 /bin/sh ../libtool --mode=install /bin/install -c  libalsatoss.la /usr/lib/liba
lsatoss.la
/bin/install -c .libs/libalsatoss.so.0.0.0 /usr/lib/libalsatoss.so.0.0.0
(cd /usr/lib && rm -f libalsatoss.so.0 && ln -s libalsatoss.so.0.0.0 libalsatoss
.so.0)
(cd /usr/lib && rm -f libalsatoss.so && ln -s libalsatoss.so.0.0.0 libalsatoss.s
o)
/bin/install -c .libs/libalsatoss.lai /usr/lib/libalsatoss.la
/bin/install -c .libs/libalsatoss.a /usr/lib/libalsatoss.a
ranlib /usr/lib/libalsatoss.a
chmod 644 /usr/lib/libalsatoss.a
PATH="$PATH:/sbin" ldconfig -n /usr/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
 ----------------------------------------------------------------------
 /bin/sh ../libtool --mode=install /bin/install -c  libaoss.la /usr/lib/libaoss.la
libtool: install: warning: relinking `libaoss.la'
(cd /sources/alsa-oss-1.0.9/alsa; /bin/sh ../libtool --mode=relink gcc -g -O2 -o libaoss.la -rpath /usr/lib -version-info 0:0:0 alsa-oss.lo libalsatoss.la )
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.3/../../..//libasound.la' seems to be moved
mv: cannot stat `libaoss.so.0.0.0': No such file or directory
libtool: install: error: relink `libaoss.la' with the above command before installing it
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/sources/alsa-oss-1.0.9/alsa'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/alsa'
make: *** [install-recursive] Error 1

Still the same.

satimis

kjordan · 09-10-2005, 03:11 PM

Well, your ld error is gone. Perhaps the missing file is related to it.

Try making it again:
make clean
make
make install

satimis · 09-15-2005, 12:07 AM

Hi kjordan,

Quote:

Try making it again:
make clean
make
make install

Sorry, the problem is "su" and "su -"

Steps performed as follows;

bash-3.00$ cd /sources/
bash-3.00$ rm -Rf alsa-oss-1.0.9
bash-3.00$ tar jxf alsa-oss-1.0.9.tar.bz2
bash-3.00$ cd alsa-oss-1.0.9
bash-3.00$ ./configure &&
> make

Code:

...
.....
creating libossredir.la
(cd .libs && rm -f libossredir.la && ln -s ../libossredir.la libossredir.la)
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/oss-redir'
Making all in test
make[1]: Entering directory `/sources/alsa-oss-1.0.9/test'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/test'
make[1]: Entering directory `/sources/alsa-oss-1.0.9'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/sources/alsa-oss-1.0.9'

bash-3.00$ su -
Password:
root@localhost:~# make install

Code:

make: *** No rule to make target `install'.  Stop.

root@localhost:~# ls

Code:

core.3697

After "su -" it changed directory.

root@localhost:~# cd /sources/alsa-oss-1.0.9
root@localhost:/sources/alsa-oss-1.0.9# make install

Code:

...
.....
/bin/sh ../mkinstalldirs /usr/include
 /bin/install -c -m 644 oss-redir.h /usr/include/oss-redir.h
make[2]: Leaving directory `/sources/alsa-oss-1.0.9/oss-redir'
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/oss-redir'
Making install in test
make[1]: Entering directory `/sources/alsa-oss-1.0.9/test'
make[2]: Entering directory `/sources/alsa-oss-1.0.9/test'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/sources/alsa-oss-1.0.9/test'
make[1]: Leaving directory `/sources/alsa-oss-1.0.9/test'
make[1]: Entering directory `/sources/alsa-oss-1.0.9'
make[2]: Entering directory `/sources/alsa-oss-1.0.9'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.   
make[2]: Leaving directory `/sources/alsa-oss-1.0.9'
make[1]: Leaving directory `/sources/alsa-oss-1.0.9'
root@localhost:/sources/alsa-oss-1.0.9#

It went throught without complaint

I think the problems on my other postings are the same, "su" and "su -". I haven't tested them yet, expecting to find more information from the trouble directories, if any. If once installed properly then all information gone.

I was not aware on LFS/BLFS 6.1 whether " Now, as the root user" meant "su -" NOT "su". Previously some packages can be installed only with "su"

BR
satimis