I wholeheartedly agree. If anyone can shed light on this annoyance (and
enlighten me in the process), I'd be rather grateful.
./configure should ONLY do that--configure what's already been
automake'd, autoconf'd, and "perl admin/am_edit"'d. Why it insists on
doing it over and over and over again purely annoys the snot out of me.
Anyone have any magic or level of clue greater than mine into the dark,
mystical world of auto* on what potions I need to conjure, dark wibble
dances I need to dance or otherwise to get rid of this bothersome habit?
* [09/17/01 01:38] Of all the gin joints in all the towns in all the world,
* Kyle Donaldson <[EMAIL PROTECTED]> walks into mine and says:
> On Sun, 16 Sep 2001, Sean 'Shaleh' Perry wrote:
> >
> > Funny, the projects not based on kproject seem to work fine. Not every
> > project
> > I use forces the run of autotools -- not sure where that comes from. I
> > recently purchased the autoconf book and hope to get better at this.
> >
>
> Hmm... I've never, ever, seen them work, even on projects that have nothing
> to do with kproject. I have always gotten errors, on Slackware Linux (4.0,
> 7.0, 7.1, 8.0), FreeBSD (4.1.1, 4.3, 5.0-dev) and OpenBSD (2.9).
>
> Maybe the autotools a relatively good idea. However, on projects that use
> them, they should never be needed by anyone else but the developers. (Why
> does ./configure insist on checking for them? The generation has already
> been done, otherwise ./configure wouldn't exist!)
>
> --
> Kyle Donaldson
> Movement Without Reason
> "Our company is like Microsoft quality, a figment of your imagination"
--
----%<----------%<----
Jason Kasper (vanRijn)
bash$ :(){ :|:&};:
Numbers 6:24-26
