On 16/04/14 14:12, Ian Jackson wrote:
> I haven't looked at the code but I'm not sure what the purpose of
> config.guess is. ISTM likely that its whole purpose is a design
> error.
AIUI, it's for build systems that make decisions based on the
"canonical" GNU architecture name of the build architecture (or,
indirectly, the host architecture, since the default host architecture
is "whatever the build architecture is"). For instance, "if this is
Linux, do foo, else do bar" or "load plugins that are named
libmyapp-*-${architecture}.${appropriate extension}". One common reason
to need it is having a library for which you used libtool.
The "guess" in the name is because it's what guesses the architecture
you're running on: without it, you wouldn't just be able to
./configure
packages that use that feature, and would have to say explicitly:
./configure [--build=whatever] --host=whatever
(which Debian packages do anyway, but installation-from-source doesn't
usually require).
S
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/534ea0ed.7060...@debian.org
