On Tue, 2009-07-07 at 22:31 +0800, Xiaofan Chen wrote: > On Tue, Jul 7, 2009 at 8:02 PM, Zach Welch<z...@superlucidity.net> wrote: > >> > I will try it. But the start of the configure output says this. > >> > > >> > mc...@ubuntu904:~/Desktop/build/openocd/build-win32-ftd2xx$ sh > >> > myconfig-win32-ftd2xx.sh > >> > configure: WARNING: If you wanted to set the --build type, don't use > >> > --host. > >> > If a cross compiler is detected then cross compile mode will be used. > >> > > >> > >> But indeed it works. So the warning should be removed. > > > > The warning is part of autotools. When used correctly, it does not > > issue the warning. The warning should have led you to look in the > > documentation for those options. > > I read the warning, and it tells me not to use "--build=i686-pc-linux-gnu". > > > From Section 13.1 of autoconf.info: > > > > """ > > If you mean to override the result of `config.guess', use `--build', > > not `--host', since the latter enables cross-compilation. For > > historical reasons, whenever you specify `--host', be sure to specify > > `--build' too; this will be fixed in the future. So, to enter > > cross-compilation mode, use a command like this > > > > ./configure --build=i686-pc-linux-gnu --host=m68k-coff > > """ > > *** rant *** > This just enhanced my bad feeling about autotools. And I refuse > to learn anything about autotools. I can afford this since I am not > a developer. It is very hard to get it right. And it generated length > and not helpful Makefile. > > IMHO it is one of the worst build systems out there and unfortunately > widely used in the Open Source world. For example, libhid is using > auto-tools and it has never been right to get Python properly detected. > *** end of rant *** > > I believe the current auto-tool scripts are still not that correct. > For example, it fails to find libftdi install in /usr/local and insists > on libftdi to be installed in /usr.
The script still needs work yes. Ranting about it will not fix it, but I sympathize with your pain. Like any language, inexperienced developers can write bad code, and I think that represents the majority of use cases. That does not mean the tools are themselves bad; it means they are hard to learn. The same can be said for C programming. Personally, I think these endemic problems stem from the fact that autotools requires knowing several programming languages: sh, m4, and Makefile. Few bother to really learn the later two, as build tools lack the satisfaction and glamor that comes from working on C code. Yes, they can be hard, but I still recommend learning to master them. --Z _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
