You are not logged in.
I just tried to install adol-c from the AUR. At the end of the install I ran into this error message:
error: failed to commit transaction (conflicting files)
adol-c: /usr/lib64 exists in filesystem
Errors occurred, no packages were upgraded.
The install generated these errors earlier on:
Prefix /usr not writable
please run ./configure --prefix=DIR
with a writable directory path otherwise administrator privileges
will be required to run `make install'
libtool: warning: remember to run 'libtool --finish /usr/lib64'
Does this mean the adol-c package wanted to create /usr/lib64? That seems weird.
(I used yaourt.)
Last edited by khouli (2015-05-21 00:25:13)
Offline
Check wether /usr/lib64 is a symlink. Pacman will complain if you try to install something using a symlink as a directory. I think every (almost every) package should install to /usr/lib. And that's what should be in PKGBUILD as --prefix.
Fix the PKGBUILD.
Offline
Ah, good to know. Yep, /usr/lib64 is a symlink to /usr/lib.
Here's the snippet from the PKGBUILD that sets --prefix. It isn't actually naming /usr/lib64 explicitly.
./configure --enable-sparse --with-colpack=/usr --prefix=/usr --enable-shared=no
If I try changing --prefix to /usr/lib then I get essentially the same error but it notes that now it's /usr/lib that isn't writable instead of /usr.
Prefix /usr not writable
please run ./configure --prefix=DIR
with a writable directory path otherwise administrator privileges
will be required to run `make install'
This is all occurring as part of a makepkg command so getting an error about privileges has me confused.
Last edited by khouli (2015-05-20 10:34:14)
Offline
Read the full warning:
[...] otherwise administrator privileges
will be required to run `make install'
That is just the way it is. This warning is only useful for people planning to install as their normal user (maybe somewhere under $HOME). So ignore it.
You need to find out if there's another option (try ./configure --help or other documentation, or search the Makefile) to change the path that uses lib64 specifically, not the general --prefix. Could be --libdir(=/usr/lib).
Offline
The configure file does indeed have a --libdir option and --libdir=/usr/lib solved this problem. Thanks.
With that solved, is there anything I should do to get the PKGBUILD in the AUR changed? Is my best bet just leaving a comment on adol-c page in the AUR?
Last edited by khouli (2015-05-21 00:26:36)
Offline
You could also email the maintainer, the email should be in the PKGBUILD.
Offline