On Tue, Dec 23, 2003 at 11:42:43AM -0600, Drew Scott Daniels wrote:
> [please CC me where appropriate]
>
> As to point 3 in
> http://lists.debian.org/debian-bsd/2003/debian-bsd-200312/msg00098.html
> > 3) The GNU config triple will have '-netbsd-gnu' as it's third part.
> > (This is unchanged - and don't blame me for a 4-part triplet. I didn't
> > start it, merely maintained consistancy with -linux-gnu).
> Why not -netbsd<version> where the version could somehow indicate the
> "fork" to tools? Why the -gnu here? What effects will this have on
> libtool/autotools-dev's use/implementations? I don't mean to cause alarm,
> I would however be more at ease if my questions are answered.
In part because netbsd's is already -netbsd<version>, specifically
-netbsd1.6 or -netbsd2.0 (etc). The -gnu reflects a GNU-derived userland
(which CAN matter, a lot, for some autoconfiscated things; for example, how
does tsort work, what are valid options to grep, how does tar work, etc).
The origional proposal was -debian, but the autotools upstream preferred
the more general -gnu (it also maps to linux-gnu, which is "Linux core,
GNU userland". Since most autoconfiscated things are more or less kernel
agnostic (or, rather, autoconf can't help with anything that cares that
much about the kernel), the 'core' here normally refers to system calls and
libc.
Or so I was given to understand, by upstream; I don't claim to be able to
make too much sense of the whole thing. In a very real sense, however, the
'-gnu' tag *is* a 'version'; specifically, that one can use the config
settings for native NetBSD 1.6, 2.0, or a NetBSD with GNU userland that
takes care of ensuring sanity on various things like pthreads for you in
some fashion.
--
Joel Baker <fenton@debian.org> ,''`.
Debian GNU/NetBSD(i386) porter : :' :
`. `'
`-
Attachment:
pgpUX4IFaQMZG.pgp
Description: PGP signature