[PATCH] waf: Fix the build on openbsd

[Jeremy Allison]

On Thu, Feb 26, 2015 at 10:06:39PM +0100, Michael Adam wrote:
> 
> This is all a matter of resources.
> We have a build system that works well most of the time.
> We have a few people that are getting more and more
> into hacking it when there are problems.
> So that being said the situation with waf is imho not as
> bad as some like to see it.
> 
> Introducing a new build system is a major effort.
> I don't know if anybody would currently have the
> time to introduce it. And it might also need
> maintainer resources.
> 
> The current problem is not that there were no
> patches for the openbsd build problem, but that
> there were several of them and people were not
> agreeing on which was appropriate, and a general
> discussion of how to treat wafadmin patches
> was started. So it seems that we don't have
> too little waf support.
> 
> 
> Coming back to the original openbsd build issue:
> 
> I propose that we first apply Volker's patch
> to wafadmin and also communicate it to upstream.
> (There was mention of some upstram bug tracker
> as the preferred location to report patches.
> Maybe we have just not pushed the correct buttons
> in the past. ;)
> 
> This would fix the problem for now.
> If we decide later that we generally want to go
> a different approach, then we can still revert
> the patch and re-do it differently.
> 
> Opinions?

Sounds good to me. I just want to see the
OpenBSD build fixed.

I also want to see the cross-compilation
build fixed, then I'll be happier with
waf.

My take on build systems is the less
I have to know about them, the better.

autoconf/automake satified that for me.
waf requires a full programming language
knowledge in a language I don't know, and
find a pain to use. In that way it's worse :-).