[pacman-dev] Problem compiling pacman 3.0.6-2
It appears that pacman needs /usr/lib/libattr.la but the package "attr" has options=('!libtool') and does not provide that file. Setting options=('libtool') for the package "attr" solves the problem, but I don't know if that is the correct solution. Karolina
On Dec 16, 2007 9:02 AM, Karolina <karolina.lindqvist@kramnet.se> wrote:
It appears that pacman needs /usr/lib/libattr.la but the package "attr" has options=('!libtool') and does not provide that file.
Hmm, I've never noticed that this libtool file is needed when I have compiled pacman. It would help all of us debug this if you posted the actual failure message. -Dan
måndag 17 december 2007 skrev Dan McGee:
Hmm, I've never noticed that this libtool file is needed when I have compiled pacman. It would help all of us debug this if you posted the actual failure message.
Here it comes: /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -march=c3 -mno-3dnow -O2 -pipe -fomit-frame-pointer -fstack-protector-all -Wall -Werror -no-undefined -version-info 2:0:0 -o libalpm.la -rpath /usr/lib add.lo alpm.lo alpm_list.lo backup.lo be_files.lo cache.lo conflict.lo db.lo delta.lo deps.lo error.lo group.lo handle.lo log.lo md5.lo package.lo remove.lo server.lo sync.lo trans.lo util.lo -ldownload -larchive -lssp grep: /usr/lib/libattr.la: No such file or directory /bin/sed: can't read /usr/lib/libattr.la: No such file or directory libtool: link: `/usr/lib/libattr.la' is not a valid libtool archive make[3]: *** [libalpm.la] Error 1 make[3]: Leaving directory `/root/abs/core/base/pacman-git/src/pacman/lib/libalpm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/abs/core/base/pacman-git/src/pacman/lib/libalpm' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/abs/core/base/pacman-git/src/pacman' make: *** [all] Error 2 ==> ERROR: Build Failed. Aborting...
On Dec 17, 2007 3:32 PM, Karolina Lindqvist <karolina.lindqvist@kramnet.se> wrote:
måndag 17 december 2007 skrev Dan McGee:
Hmm, I've never noticed that this libtool file is needed when I have compiled pacman. It would help all of us debug this if you posted the actual failure message.
Here it comes:
/bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -march=c3 -mno-3dnow -O2 -pipe -fomit-frame-pointer -fstack-protector-all -Wall -Werror -no-undefined -version-info 2:0:0 -o libalpm.la -rpath /usr/lib add.lo alpm.lo alpm_list.lo backup.lo be_files.lo cache.lo conflict.lo db.lo delta.lo deps.lo error.lo group.lo handle.lo log.lo md5.lo package.lo remove.lo server.lo sync.lo trans.lo util.lo -ldownload -larchive -lssp grep: /usr/lib/libattr.la: No such file or directory /bin/sed: can't read /usr/lib/libattr.la: No such file or directory libtool: link: `/usr/lib/libattr.la' is not a valid libtool archive make[3]: *** [libalpm.la] Error 1 make[3]: Leaving directory `/root/abs/core/base/pacman-git/src/pacman/lib/libalpm' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/abs/core/base/pacman-git/src/pacman/lib/libalpm' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/abs/core/base/pacman-git/src/pacman' make: *** [all] Error 2 ==> ERROR: Build Failed. Aborting...
/bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -fstack-protector-all -Wall -Werror -no-undefined -version-info 2:0:0 -o libalpm.la -rpath /usr/lib add.lo alpm.lo alpm_list.lo backup.lo be_files.lo cache.lo compat.lo conflict.lo db.lo delta.lo deps.lo error.lo group.lo handle.lo log.lo md5.lo package.lo remove.lo server.lo sync.lo trans.lo util.lo -ldownload -larchive -lssp Works fine for me. What is the output of the following? $ ldd lib/libalpm/.libs/libalpm.so linux-gate.so.1 => (0xb7f6a000) libdownload.so => /usr/lib/libdownload.so (0xb7f1b000) libarchive.so.2 => /usr/lib/libarchive.so.2 (0xb7ef4000) libssp.so.0 => /usr/lib/libssp.so.0 (0xb7ef1000) libc.so.6 => /lib/libc.so.6 (0xb7dbb000) libz.so.1 => /lib/libz.so.1 (0xb7da8000) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb7d98000) libattr.so.1 => /lib/libattr.so.1 (0xb7d94000) libacl.so.1 => /lib/libacl.so.1 (0xb7d8d000) /lib/ld-linux.so.2 (0x80000000) This may be worth filing a bug report about, although it seems like an issue with your libattr compile (in that the static library was not compiled correctly, we have this same problem with libarchive). -Dan
måndag 17 december 2007 skrev Dan McGee:
Works fine for me. What is the output of the following? $ ldd lib/libalpm/.libs/libalpm.so linux-gate.so.1 => (0xb7f6a000) libdownload.so => /usr/lib/libdownload.so (0xb7f1b000) libarchive.so.2 => /usr/lib/libarchive.so.2 (0xb7ef4000) libssp.so.0 => /usr/lib/libssp.so.0 (0xb7ef1000) libc.so.6 => /lib/libc.so.6 (0xb7dbb000) libz.so.1 => /lib/libz.so.1 (0xb7da8000) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb7d98000) libattr.so.1 => /lib/libattr.so.1 (0xb7d94000) libacl.so.1 => /lib/libacl.so.1 (0xb7d8d000) /lib/ld-linux.so.2 (0x80000000)
This may be worth filing a bug report about, although it seems like an issue with your libattr compile (in that the static library was not compiled correctly, we have this same problem with libarchive).
I get the same thing. The same problem as with libarchive then. Karolina
participants (3)
-
Dan McGee
-
Karolina
-
Karolina Lindqvist