basedir spec and plugins
dobey.pwns at gmail.com
Tue Jun 30 06:09:26 PDT 2009
On Tue, 2009-06-30 at 13:02 +0100, Simon McVittie wrote:
> ia64-linux-gnu (is the word size/endianness differentiation really necessary,
> or is there one endianness and word size that, in practice, everyone uses?
> If you really need to distinguish, talk to config-patches at gnu.org, without
> which software that uses autotools probably won't compile for the "other"
> configurations anyway)
> > ia64-hpux-32 (subtypes g++ and aCC)
> > ia64-hpux-64 (subtypes g++ and aCC)
> Again, config.guess doesn't seem to distinguish: does nobody actually use one
> of these configurations?
> > sparc-solaris-32 (subtypes g++ and CC)
> > sparc-solaris-64 (subtypes g++ and CC)
> > sparc-linux-32
> > sparc-linux-64
> sparc-solarisN, sparc-linux-gnu, sparc64-linux-gnu.
> It might be worth asking the proposers of multiarch how their work relates to
> C++ compiler ABIs; in principle you could have sparc-solaris3-g++3 and
> sparc-solaris3-suncc, I suppose.
Why not just "lib32" and "lib64"? Do we really need some significant
amount of complexity to deal with hosts/compilers/archs/etc... ?
More information about the xdg