Anyhow, [issues with rpaths persist][persist]. Since it both hard to
predict all installation configurations at compile time, and tools to
-change rpaths later on (i.e. `chrpath`) aren't able to increase the
-size of the rpath string on Linux ([they can on Solaris][solaris],
-because Solaris leaves a bit of padding at the end of the dynamic
-string table in the compiled [ELF][] file). This means you will have
-trouble moving a library out of the standard library path into some
-out-of-the-way location. However, in the more common case of
-installing a library *into* the standard library path, `chrpath` is
-the tool you need, and it solved my comedilib QA issue.
+change rpaths later on (i.e. [chrpath][] and [patchelf][]) aren't able
+to increase the size of the rpath string on Linux ([they can on
+Solaris][solaris], because Solaris leaves a bit of padding at the end
+of the dynamic string table in the compiled [ELF][] file). This means
+you will have trouble moving a library out of the standard library
+path into some out-of-the-way location. However, in the more common
+case of installing a library *into* the standard library path,
+`chrpath` is the tool you need, and it solved my comedilib QA issue.
Along the way, I ran across two other interesting posts by Diego
Pettenò about not [bundling][] [libraries][].
[c2]: http://www.mail-archive.com/debian-devel@lists.debian.org/msg61796.html
[works]: http://www.mail-archive.com/debian-devel@lists.debian.org/msg61967.html
[persist]: http://blog.flameeyes.eu/2010/06/20/the-why-and-how-of-rpath
+[chrpath]: http://directory.fsf.org/wiki/Chrpath
+[patchelf]: http://nixos.org/patchelf.html
[solaris]: http://blogs.sun.com/ali/entry/changing_elf_runpaths
[ELF]: http://en.wikipedia.org/wiki/Executable_and_Linkable_Format
[bundling]: http://blog.flameeyes.eu/2009/01/02/bundling-libraries-for-despair-and-insecurity