1 |
On Mon, 2005-09-12 at 10:38 -0400, Mike Frysinger wrote: |
2 |
> On Monday 12 September 2005 08:58 am, Stephen P. Becker wrote: |
3 |
> > > Hi, as I mentioned, I built LFS without this (and I have coreutils on |
4 |
> > > it ;) |
5 |
> > > |
6 |
> > > Not at all - if we need to modify or create configure files during build |
7 |
> > > as Paul and Martin said ... we need autoconf/automake |
8 |
> > |
9 |
> > And furthermore, many programs (or upstream authors if you prefer) are |
10 |
> > braindead and don't know what some non-x86 arches are without updating |
11 |
> > the config.sub/config.guess, and re-running autoconf/automake. |
12 |
> |
13 |
> those two files dont require re-running autoconf/automake |
14 |
> |
15 |
> it isnt uncommon though to have upstream run autotools in the wrong order and |
16 |
> package the result as their release ... then when you run `./configure && |
17 |
> make`, the build system has mismatched timestamps and thus tries to invoke |
18 |
> autotools to fix itself :/ |
19 |
|
20 |
Toss in libtool in the mess, and it runs aclocal, autoconf and then |
21 |
automake, and you end up with a mismatched ltmain.sh and whatever |
22 |
macro's of libtool expanded in configure, causing either breakage |
23 |
(random or not), or in our case an error informing about the mismatch :/ |
24 |
|
25 |
|
26 |
-- |
27 |
Martin Schlemmer |