You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Enrico Weigelt <we...@metux.de> on 2005/01/23 14:49:07 UTC
Re: [PATCH] fixing broken gnu ld (mis)detection problem
* Greg Stein <gs...@lyra.org> wrote:
<snip>
> pffft. Ease up on the veto there. Users don't need autoconf or
> libtool. The RM generates those files during the release process.
yeah, and then users have to repair broken ./configure scripts
again and again.
Well, at this point we have no need to use autoconf time wasting
autoconf anylonger. Instead we should maintain config stuff
carefully by hand - I'd volounteer for this job.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service
phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact@metux.de
cellphone: +49 174 7066481
---------------------------------------------------------------------
-- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------
Re: [PATCH] fixing broken gnu ld (mis)detection problem
Posted by Enrico Weigelt <we...@metux.de>.
* Andy Armstrong <an...@apache.org> wrote:
> Enrico Weigelt wrote:
> >yeah, and then users have to repair broken ./configure scripts
> >again and again.
>
> Really? How often does this actually happen? My experiences with
> autoconf have been pretty good down the years and they get better as
> people get better at using it.
For me: almost every day.
One of my main jobs is to build customized distros for small systems.
Evryting has to be crosscompiled (and so sysrooted). More than 50%
of the autoshit-based packages have to be fixed to get it working.
Apache is one of those packages requiring an extensive huge amount of work.
> It's certainly not beyond criticism -
> it's a sprawling and somewhat non-obvious metalanguage for a developer
> to learn for a start - but it works OK.
yeah, a chomsky-0 language, with about 90% of the files laying around
on your harddisk being silent part of the code ...
really great thing.
> >Well, at this point we have no need to use autoconf time wasting
> >autoconf anylonger. Instead we should maintain config stuff
> >carefully by hand - I'd volounteer for this job.
>
> Did we just go through a time warp? I thought we did this a month ago
> and decided it wasn't going to happen.
Yeah, since these month I had to spend whole days for fixing (not really
repairing) bugs in autoconf's spitout.
Using autoconf is really unproductive. Fixing broken stuff all over the
time eats up more resources than writing evrything by hand.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service
phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact@metux.de
cellphone: +49 174 7066481
---------------------------------------------------------------------
-- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------
Re: [PATCH] fixing broken gnu ld (mis)detection problem
Posted by Andy Armstrong <an...@apache.org>.
Enrico Weigelt wrote:
> yeah, and then users have to repair broken ./configure scripts
> again and again.
Really? How often does this actually happen? My experiences with
autoconf have been pretty good down the years and they get better as
people get better at using it. It's certainly not beyond criticism -
it's a sprawling and somewhat non-obvious metalanguage for a developer
to learn for a start - but it works OK.
> Well, at this point we have no need to use autoconf time wasting
> autoconf anylonger. Instead we should maintain config stuff
> carefully by hand - I'd volounteer for this job.
Did we just go through a time warp? I thought we did this a month ago
and decided it wasn't going to happen.
--
Andy Armstrong, hexten.net