Clemens,

> Why do you have to? If you're running autoreconf anyway, why not just patch 
> configure.in or configure.ac? Those are usually easier to patch.

Well it turns out to be harder than expected. The patch corresponds to some 
code generated by an autoconf macro. If I disable the macro, nothing more 
happens, and if I let it, the configure file throw an error. I am trapped. 

Vincent

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to