| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Multi-architecture problem
Multi-architecture problem
Posted Apr 8, 2004 17:36 UTC (Thu) by hazelsct (subscriber, #3659)Parent article: The User-Accessible Filesystem Hierarchy Standard
Problem: for users in networks with multiple architectures, this presents only single bin and lib directories. Granted, this is not a large number of folk, but for those of us who have mixed IA-32, alpha, PowerMac, etc. systems in the network, this won't work.
For myself, I have for years used --prefix=$HOME/$HOSTTYPE, which isn't perfect either, but solves most of these problems. I do hope that if this is going to become a "standard" that it will address this problem.
(Log in to post comments)
Multi-architecture problem
Posted Apr 9, 2004 14:29 UTC (Fri) by nix (subscriber, #2304) [Link]
The system I use to install software that the admins at work don't want to manage (of which there is plenty) is to stow things into a tree .packages/{config-guess-triplet}/ and .packages/all, putting arch-dependent stuff into the former, and arch-independent stuff into the latter. Both are then stowed into place (although there are extra complexities with LD_LIBRARY_PATH for shared libraries).What can I say, it works, although a number of programs that don't implement the GNU Coding Standards properly (or at all) needed build-system patches to properly separate arch-dependent and -independent install trees.