Andrew Cooper writes ("Re: [Xen-devel] [OSSTEST PATCH 5/6] Debian: preferred
arch: Apply setarch to sshd"):
> What is wrong with setting XEN_TARGET_ARCH=x86_{64,32} ?
I considered this. (Indeed it's what I do in my own ad-hoc builds on
my workstation.) But:
Firstly it would involve maintenance of yet another mapping of
architecture names. I have mostly avoided this - although it is
creeping in with some of these special cases, I don't need a complete
table, only the names of busted architectures and their fixed ones.
Secondly, it does not work for autoconf. For autoconf I would have to
pass --host= or --build= or something and I would have to have the
complete set of autoconf arch names. autoconf arch names contain the
host OS as well, which makes this even more annoying.
Thirdly, there are probably things other than autoconf and Xen which
foolishly use uname. I din't want to play whack-a-mole with them.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
