I'm building a Linux system that doesn't have a /usr directory. Getting the toolchain to work was surprisingly easy, but I'm hitting this irritation with a lot of auto* scripts: configure, etc. often seem to assume env is in /usr/bin.
A workaround is to do ln -sv .. /usr during the build, but obviously that's aesthetically unappealing and runs the risk of a path with /usr in it leaking into the final system. (There will be a network mounted /usr in production, and I don't want the base system to even know it exists.)
Did I install my autotools wrong, or is this just an irritating assumption configure often makes? Am I breaking FHS by not putting env in /usr/bin? (That's not a deal breaker for me; I'm already breaking it by having /inc and /share.)
envin/usr/bin. that's not a big deal: everyone breaks FHS. really. people vaguely care about it, but not really. what you are breaking, though, is decades of convention. and that is much more important. – strugee Jun 12 '14 at 7:00