[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141218195428.GA6168@openwall.com>
Date: Thu, 18 Dec 2014 22:54:28 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: autoconf
On Thu, Dec 18, 2014 at 08:50:10PM +0100, magnum wrote:
> On 2014-12-18 20:39, Solar Designer wrote:
> > I think the current configure script probes for way too many things.
> > For many of them, the build should just assume they're present. It'd
> > fail otherwise, so no reason to probe for them. For example, why probe
> > for strrchr() and snprintf()? I think we don't have alternate code that
> > wouldn't use those anyway. Why probe for bzero()? We should simply
> > consistently use memset() instead. And so on. Can we halve the number
> > of configure tests maybe?
>
> I did remove a good number of them but Jim wanted them back. I'd prefer
> only keeping ones that we actually use.
Can we just override Jim's preference on this? ;-) Like with majority
of votes (2 vs. 1)? ;-)
> Having said that, many of them are added by the prefab macros we use.
This may be a reason for us to cut down on use of those macros.
> OTOH this is not an issue for the casual user who builds this once a
> year or less.
This is bloat. I dislike bloat.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
