Yaourt problem

paldepind · 2010-08-02 08:21:12

When I try to install anything with Yaourt I get this error:

package-query: error while loading shared libraries: libalpm.so.4: cannot open shared object file: No such file or directory

I've tried reinstalling both package-query and yaourt from AUR, but it didn't work.

hokasch · 2010-08-02 10:41:49

What versions do you have installed? Works here with fully updated system:

Name           : package-query
Version        : 0.3-2

Name           : yaourt
Version        : 0.9.4.3-1

Name           : pacman
Version        : 3.4.0-2

Radioactiveman · 2010-08-02 12:01:20

Did you just install the two packages again or did you compile them again?

falconindy · 2010-08-02 13:31:27

paldepind wrote:

When I try to install anything with Yaourt I get this error:
package-query: error while loading shared libraries: libalpm.so.4: cannot open shared object file: No such file or directory
I've tried reinstalling both package-query and yaourt from AUR, but it didn't work.

Recompile package-query. Don't just reinstall it.

Mr.Elendig · 2010-08-02 15:47:25

My quick search came up with alteast 11 threads about this. Please use the search function.

paldepind · 2010-08-02 15:58:59

falconindy wrote:

paldepind wrote:
When I try to install anything with Yaourt I get this error:
package-query: error while loading shared libraries: libalpm.so.4: cannot open shared object file: No such file or directory
I've tried reinstalling both package-query and yaourt from AUR, but it didn't work.
Recompile package-query. Don't just reinstall it.

Sorry, I didn't express myself correctly. I did recompile it.

falconindy wrote:

What versions do you have installed?

The same as you.

hokasch · 2010-08-02 16:10:55

https://bbs.archlinux.org/viewtopic.php … 88#p779488

If that is not helping you, please post the output from
pacman -Qo /usr/lib/libalpm*
nevermind, package-query not build against the new libs should be the problem.

Last edited by hokasch (2010-08-02 16:13:18)

paldepind · 2010-08-02 16:23:36

So this is a bug in package-query or what?

Last edited by paldepind (2010-08-02 16:24:12)

falconindy · 2010-08-02 16:57:41

paldepind wrote:

Sorry, I didn't express myself correctly. I did recompile it.

Then you reinstalled the old build. Perhaps you reused the old build directory and didn't run make clean? This is a common dynamic library loading error that crops up any time a library (libalpm in this case) gets an so-name bump. If you truly (correctly) recompiled package-query and it linked against a .so that doesn't exist on your system, then it's plausible that you've discovered a serious flaw in gcc which has yet to be discovered/reported.

In short: Please use makepkg in a new build directory to compile and install package-query.

paldepind · 2010-08-02 18:07:03

I did what you said and it works now. Thanks!

But I don't understand why there is a problem in just reusing the old build directory.Could you please explain that to me in a noob friendly way?

falconindy · 2010-08-02 18:25:49

In short: Makefiles are unintelligent.

Less short: Makefiles employ the use of targets which, speaking in overly generic terms, have an output (a binary) and one or more requirements (source files). It's important to know that any time you run make successfully, the mtime of the Makefile is updated. When you run make, a few checks (among many others) are done:

1) is the mtime of the Makefile newer than all of the requirements?
2) does the output exist?

If the answer to both of these is yes, then you get the output:

make: `target' is up to date.

make also returns 0 here, signaling that everything is cool.

makepkg isn't much smarter. When it runs in the old build directory, make returns 0, even though nothing happened. makepkg only knows that nothing has gone wrong yet, and it continues on its way, packaging up the old files.

Solutions:
1) For the user, invoke makepkg with -c (or `rm -rf src' before building)
2) For the PKGBUILD maintainer, invoke make with -B (unconditionally remaking targets)

Mr.Elendig · 2010-08-02 19:17:19

paldepind wrote:

I did what you said and it works now. Thanks!
But I don't understand why there is a problem in just reusing the old build directory.Could you please explain that to me in a noob friendly way?

Another thing: If you don't use -f, and makepkg finds an already built package, it will happily install that instead of rebuilging. (if you use the -i flag)

paldepind · 2010-08-02 20:23:11

Thanks guys! I understand it know

Arch Linux

#1 2010-08-02 08:21:12

Yaourt problem

#2 2010-08-02 10:41:49

Re: Yaourt problem

#3 2010-08-02 12:01:20

Re: Yaourt problem

#4 2010-08-02 13:31:27

Re: Yaourt problem

#5 2010-08-02 15:47:25

Re: Yaourt problem

#6 2010-08-02 15:58:59

Re: Yaourt problem

#7 2010-08-02 16:10:55

Re: Yaourt problem

#8 2010-08-02 16:23:36

Re: Yaourt problem

#9 2010-08-02 16:57:41

Re: Yaourt problem

#10 2010-08-02 18:07:03

Re: Yaourt problem

#11 2010-08-02 18:25:49

Re: Yaourt problem

#12 2010-08-02 19:17:19

Re: Yaourt problem

#13 2010-08-02 20:23:11

Re: Yaourt problem

Board footer