Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 18 Dec 2014 20:50:10 +0100
From: magnum <>
Subject: Re: autoconf

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. Having said that, many of them
are added by the prefab macros we use.

OTOH this is not an issue for the casual user who builds this once a
year or less.


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.