From: Corinna V. <vin...@re...> - 2006-11-20 14:29:04
|
On Nov 20 10:22, Keith MARSHALL wrote: > I am convinced that the entire autoconf set up for mingw-runtime requires > a complete overhaul; IMO, Corinna's patch remains broken. It employs an > unusual distribution of labour between `configure' and `Makefile', and it > does not correctly utilise the standard `--build' and `--host' flags to > establish the configuration; instead it improperly, and unnecessarily IMO, > adds a `--with-cross-host' flag, without any explanation of its intended > purpose or usage. For the explanation of --with-cross-host see the toplevel configure.in file. As for "adding" a --with-cross-host flag, did you have a look into winsup/mingw/configure.in as it was before my patch (cvs up -r 1.12 configure.in && grep with_cross_host configure.in)? I also think it's somewhat strange to claim I didn't add any explanation, see http://sourceware.org/ml/gdb-patches/2006-08/msg00198.html To reiterate, the patch was intended to solve one specific situation which was not fully covered so far which is, building a fully automated, self-contained canadian cross with Mingw as host and with the winsup directory simply being part of a gcc/binutils/gdb/etc source tree. Like for instance this: build = linux, host = mingw, target = arm-elf which requires to run three builds on the linux machine: linux-x-mingw (generate linux->mingw crosstools and mingw libs) linux-x-arm-elf (generate arm-elf libs) mingw-x-arm-elf (generate mingw->arm-elf crosstools using the tools and libs built in the 1st step) If you tried this before my patch, you got stuck due to several tiny but nevertheless annoying problems outlined in the above mail. As for using --with-cross-host instead of "correctly utilis[ing] the standard `--build' and `--host' flags, you should try a canadian cross like the above yourself. You will find that even when building with build=linux host=linux target=mingw as necessary for the first step, this is tweaked to build=linux host=mingw target=mingw when configuring the target libraries. That's why --with-cross-host exists right now and that's why I don't see another solution for this problem right now. > I have tried, on several occasions, to contact > her directly, to ask for clarification of her intended objectives, but > have yet to receive any reply. I'm not aware that you tried to contact me about this, except by CCing me in two mails to the mingw-dvlpr mailing lists on 2006-09-03. But, never mind. > I intend to rewrite the entire configure > and Makefile setup for mingw-runtime, to properly comply with established > autoconf convention; I would prefer to have her co-operation, to ensure > that what I do remains compatible with her objectives, in case I might > inadvertently break something in a Cygwin build. However, I will not > allow the current breakage of the MinGW cross-compiler build to persist > indefinitely; if Corinna continues to ignore my emails, then I will be > obliged to `go it alone', but I really do not want to do that. I created this patch to solve a specific problem. I didn't intend to revamp the Mingw configury and I certainly didn't intend to revamp the approach taken by the current toplevel configury. I'm not excited about working on the Mingw autoconf stuff, mainly because I'm glad if I don't have to work on autoconf stuff at all, but also because I have already way too many open lots. As usual the best arguments are working patches. If you can come up with a better and more elegant approach which neither breaks Cygwin builds (native and cross), nor canadian cross builds, fine with me. But without actual code it's a bit... well, fruitless. Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat |