News for hackers. Stuff that matters.
Re:GNU make insanity: finding the value of the -j parameter by crististm on Sunday March 29, 2015 @07:02AM (#9284462)
I took my chances at using autotools in 2014.

I did this to see for myself if autotools bashing is justified and I can tell you this: If a configure script is that bad, then the project's developers did a poor job using autotools.

Re:GNU make insanity: finding the value of the -j parameter by tedunangst on Sunday March 29, 2015 @08:43AM (#9284625)
It's hard to believe the problem lies solely with the developers when every project is this bad. For fun, I just downloaded the source for GNU grep. You'd figure they might have some experience. Among the 600 tests configure performs is

    checking whether mkfifoat is declared without a macro... yes
Why? Nowhere in grep is there a single call to mkfifoat. Why does it care?

I also liked this:

    checking for MAP_ANONYMOUS... yes
    checking for MAP_ANONYMOUS... yes
    checking for MAP_ANONYMOUS... yes
    checking for MAP_ANONYMOUS... yes
    checking for MAP_ANONYMOUS... yes
    checking for MAP_ANONYMOUS... yes
    checking for MAP_ANONYMOUS... yes
Re:GNU make insanity: finding the value of the -j parameter by crististm on Sunday March 29, 2015 @09:56AM (#9284819)
The downside is that after you make it work there is no incentive/glamor in getting back to clean-up. Thus, not enough people get to have the minimum knowledge to fix things risking whatever worked to stop working.

And the work has a bigger risk because you can't actually check on more than a couple of distributions before you ship.