Opened 12 years ago

Closed 12 years ago

Last modified 10 years ago

#3329 closed defect (fixed)

Shadow will not build after installing acl and attr

Reported by: Wayne Blaszczyk Owned by: DJ Lucas
Priority: normal Milestone:
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

After installing attr and acl (BLFS Version 2012-04-09), I cannot build shadow (after installing linux-pam). The following error occurs during make:

/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o useradd useradd.o ../libmisc/libmisc.a ../lib/libshadow.la -lpam -lpam_misc -lacl -lattr libtool: link: cannot find the library /usr/usr/lib/libattr.la' or unhandled argument /usr/usr/lib/libattr.la' make[2]: * [useradd] Error 1 make[2]: Leaving directory `/sources/shadow-4.1.5/src' make[1]: * [all-recursive] Error 1 make[1]: Leaving directory `/sources/shadow-4.1.5' make: * [all] Error 2

Change History (7)

comment:1 by ken@…, 12 years ago

Did you put libattr in /usr/usr ? If so, I suppose you could add that to /etc/ld.so.conf.

If not, where is /usr/usr coming from ? I assume it was picked up from a pkgconfig file.

comment:2 by Wayne Blaszczyk, 12 years ago

There is no /usr/usr directory and I cannot find any attr.pc file. I have rebuilt this several times now with various versions and it all points to something being wrong with the current attr instructions.

comment:3 by DJ Lucas, 12 years ago

Owner: changed from blfs-book@… to DJ Lucas

My bad..I broke it. The problem is in acl. When I 'fixed' this problem, the dependency was picked up from the broken attr la file. The sed for acl will have to be sed "s@'/lib@'/usr/lib@" -i /usr/lib/libacl.la. In your case, just get rid of the double /usr in the libacl.la file and all will be well. I'll get this into the book in a sec.

comment:4 by bdubbs@…, 12 years ago

Looking at my logs, there is no match for pc in either attr or acl.

WE may have some problem though. I get:

$ ldd /usr/bin/attr
        linux-vdso.so.1 =>  (0x00007fffcf367000)
        libattr.so.1 => /usr/lib/libattr.so.1 (0x00007fce3623b000)
        libc.so.6 => /lib/libc.so.6 (0x00007fce35eb4000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fce3643f000)

even though /usr/lib/libattr.so.1 is symlinked to /lib, attr is not looking there. If /usr was not mounted, it may be a problem.

in reply to:  4 comment:5 by bdubbs@…, 12 years ago

Replying to bdubbs@…:

We may have some problem though. I get:

$ ldd /usr/bin/attr
        linux-vdso.so.1 =>  (0x00007fffcf367000)
        libattr.so.1 => /usr/lib/libattr.so.1 (0x00007fce3623b000)
        libc.so.6 => /lib/libc.so.6 (0x00007fce35eb4000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fce3643f000)

The above may be a problem just for me. I double checked and had libattr.so.1 in /usr/lib with a different date than the one in /lib. When I removed the offending files in /usr/lib, attr found libattr.so.1 => /lib64/libattr.so.1 just fine.

comment:6 by DJ Lucas, 12 years ago

Resolution: fixed
Status: newclosed

Fixed in r9898.

comment:7 by bdubbs@…, 10 years ago

Milestone: current

Milestone current deleted

Note: See TracTickets for help on using tickets.