From: "Stephen P. Becker" <geoman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why autoconf in system?
Date: Mon, 12 Sep 2005 08:58:25 -0400 [thread overview]
Message-ID: <43257B71.7000700@gentoo.org> (raw)
In-Reply-To: <1126529308.5947.178.camel@localhost.localdomain>
> Hi, as I mentioned, I built LFS without this (and I have coreutils on
> it ;)
>
> Not at all - if we need to modify or create configure files during build
> as Paul and Martin said ... we need autoconf/automake
And furthermore, many programs (or upstream authors if you prefer) are
braindead and don't know what some non-x86 arches are without updating
the config.sub/config.guess, and re-running autoconf/automake.
-Steve
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-12 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 12:26 [gentoo-dev] Why autoconf in system? Frank Schafer
2005-09-12 12:38 ` Paul de Vrieze
2005-09-12 12:40 ` Martin Schlemmer
2005-09-12 12:41 ` Mike Frysinger
2005-09-12 12:48 ` Frank Schafer
2005-09-12 12:56 ` Mike Frysinger
2005-09-12 12:58 ` Stephen P. Becker [this message]
2005-09-12 14:38 ` Mike Frysinger
2005-09-12 16:06 ` Martin Schlemmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43257B71.7000700@gentoo.org \
--to=geoman@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox