On Sun, 13 Sep 1998, Richard Braakman wrote:
> Zed Pobre wrote:
> > Part 3: (bug#25385)
> >
> > Section 4.1 ("Architecture specification strings") should be changed
> > to allow the Hurd operating system. This requires that the segment
> > reading:
> >
> > where `<arch>' is one of the following: i386, alpha, arm, m68k,
> > powerpc, sparc.
> >
> > be changed to:
> >
> > where `<arch>' is one of the following: i386, alpha, arm, gnu, m68k,
> > powerpc, sparc.
>
> This is wrong. It would add gnu-linux as an architecture. What is
> needed is to add <arch>-gnu to <arch>-linux, for all architectures.
> (Currently there is only an i386 port, but that may change).
Hi.
Richard is right. The bug report means that whenever <arch>-linux is
allowed, <arch>-gnu should be allowed also (even if only i386-gnu
is used for now).
This <arch>-linux or <arch>-gnu thing ("Architecture specification
strings") is the type of argument we pass to autoconf-generated configure
scripts.
> I find it amusing that the FSF contradicts its own "GNU/Linux" stance
> here :-) Apparently linux is "GNU/Linux", but the Hurd is called "gnu"
> to distinguish it from "linux". I would find an architecture string
> with "hurd" to be far more consistent.
Probably, but I'm afraid it's too late to change that.
--
"08aca8c29c6c02b3ad35ddbd47eddec5" (a truly random sig)
