On Mon, Mar 12, 2012 at 16:12, Stefan Sperling <s...@elego.de> wrote:
> It might be some dependency that rupert needs for this build and which
> is either located in /usr/lib64 or needs a library installed there.
Probably. But that is no reason to inject -L/usr/lib64 into the linker
flags - pkg-config files should _never_ add flags referring
to locations that are in the standard search paths, e.g.
/usr/lib{64} for libraries of /usr/include for header files.
But there are a lot of sloppily written pkg-config files out there...
> Ah, you're correct that it may not be related to rupert's problem.
> What I meant is actually a problem with upgrades between minor versions
> (like 1.5 to 1.6) and the error is usually different (cannot find symbol
> 'foo'). Thanks for pointing that out.
I guess the correct answer should have been:
Subversion uses its own scheme of "versioned symbols"
(by never changing the signature of a function foo(),
instead adding foo1(), foo2() etc) and also being
careful when adding to structures.
> the entirely contradictory shared library versioning rules that exist
> in Debian and OpenBSD packaging?
Why single out Debian here? I can't see a difference wrt versioning
rules in all major Linux distributions.
Cheers, Roderich
