> Yes, that's clever. But, you can create a symbolic link to the > sysroot from each installation with a single command. And, your > installer for third-party developers can do that for you.
Beware - the linker expands symlinks to determine if a library comes from the sysroot or not. It affects "libraries" which are really linker scripts (like libc.so); the linker will relocate the paths within *if* the library exists - truely exists - in the sysroot directory. Symlinks *to* the sysroot location work, symlinks *from* the sysroot location break the linker. At least, last time I was bitten by this, that's how it worked.
