From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why autoconf in system?
Date: Mon, 12 Sep 2005 18:06:20 +0200 [thread overview]
Message-ID: <1126541180.14207.55.camel@lycan.lan> (raw)
In-Reply-To: <200509121038.15443.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
On Mon, 2005-09-12 at 10:38 -0400, Mike Frysinger wrote:
> On Monday 12 September 2005 08:58 am, Stephen P. Becker wrote:
> > > 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.
>
> those two files dont require re-running autoconf/automake
>
> it isnt uncommon though to have upstream run autotools in the wrong order and
> package the result as their release ... then when you run `./configure &&
> make`, the build system has mismatched timestamps and thus tries to invoke
> autotools to fix itself :/
Toss in libtool in the mess, and it runs aclocal, autoconf and then
automake, and you end up with a mismatched ltmain.sh and whatever
macro's of libtool expanded in configure, causing either breakage
(random or not), or in our case an error informing about the mismatch :/
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-09-12 16:08 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
2005-09-12 14:38 ` Mike Frysinger
2005-09-12 16:06 ` Martin Schlemmer [this message]
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=1126541180.14207.55.camel@lycan.lan \
--to=azarah@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