[blfs-support] apr-1.5.1 `tar xf` and `make test` error

Fernando de Oliveira famobr at yahoo.com.br
Thu Jul 16 07:19:56 PDT 2015

Em 15-07-2015 20:29, Michael Gruben escreveu:
> Hey all, made it successfully through LFS, and have been installing things
> from BLFS without issue until now.
> Wanted to install httpd, requiring apr-utils, requiring apr, so `wget
> http://archive.apache.org/dist/apr/apr-1.5.1.tar.bz2` into sources.
> Successfully `# tar xf apr-1.5.1.tar.bz2`, but `# ls -alh apr-1.5.1`
> reveals that everything belongs to lfs:lfs (1000,1000 on my system).

This does not seem to be a problem. Tested and files are owned by 
1000:1000. Only if the user is other than 0 or 1000 this would be a 
problem, I think.

Anyway, you can always use:

tar -xf apr-1.5.1.tar.bz2 --no-same-owner

to get files owned by user uncompressing it.

> Subsequently, following the build instructions
> at BLFS-BOOK-7.7-nochunks.html#apr, receive the following after make test:
> libtool: link: `sendfile.lo' is not a valid libtool object
> Makefile:104: recipe for target 'sendfile' failed
> ...
> /sources/apr-1.5.1/build/apr_rules.mk:118: recipe for target
> 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: *** Waiting for unfinished jobs....
> libtool: link: warning: `/usr/lib64/libuuid.la' seems to be moved
> make[1]: Leaving directory '/sources/apr-1.5.1/test'
> Makefile:127: recipe for target 'check' failed
> make: *** [check] Error 2
> Happy to provide any additional information.

Referring to sendfile.lo, I only have the following in the tests 
(unfortunately it is for apr-1.5.2):

/bin/sh /tmp/apr-1.5.2/libtool --silent --mode=compile gcc -g -O2 
-I./../include -o sendfile.lo -c sendfile.c && touch sendfile.lo
/bin/sh /tmp/apr-1.5.2/libtool --silent --mode=link gcc -g -O2 -pthread 
-I./../include -no-install -o sendfile sendfile.lo ../libapr-1.la -luuid 
-lrt -lcrypt -lpthread -ldl

Those are two lines only, each one starting with "/bin/sh".

Apparently, no errors in make test.

Are you in chroot or ssh? I don't know if that matters.

More information about the blfs-support mailing list