The checked-in mingw-w64-crt/Makefile.in was generated with 1.15. However the associated aclocal.m4 is generated with 1.14.1. I don't know much about the build files, but is mixing and matching like this a good idea?
Since I need to regenerate Makefile.in, I need to decide what to do: a) I could just let the generation process do what it does, effectively downgrading makefile.in from 1.15 back to 1.14.1. b) I could 'trick' my build environment into building a 1.15 build file and just check in the changed Makefile.in. c) I could use use "autoreconf -fiv" to regenerate all the build files in mingw-w64-crt with 1.15 and check them all in. d) I could regenerate all the build files in the entire project to 1.15 (some are as old as 1.11.6). But honestly, I'm not particularly comfortable doing any of these. I generally assume that newer versions fix problems or have other benefits, but sometimes they can introduce other issues. For all I know there's a good reason things are the way they are. And I'm certainly not going to be the best qualified to answer any questions or fix any problems that may arise as a result of c or d. Hopefully someone who knows more about this stuff than I do can check in the 'right' fix to get things back in sync. dw ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
