* Christoph Hellwig wrote on Fri, Jun 06, 2008 at 03:07:56PM CEST: > > LIBTOOL="libtool --tag=CC" CC=~/bin/cgcc ./configure > > does it for me. So I guess the problem is with libtool and it needs > to be taught about cgcc. Well, thing is, the typical way things work is that a libtool script is generated as part of the configure process, and it sets things for the $CC, $CXX, etc. used for that configure. With this package, however, /usr/bin/libtool is used, and that typically has been configured only for /usr/bin/gcc etc. I suppose a distro could add a section for cgcc, yes, or make it assume --tag=CC for 'cgcc'. But really passing --tag=CC is the sane thing to do: the package knows that your code is C code, whereas libtool inferring it from the command line is error-prone (which is why the tag check was made stricter in the first place). Cheers, Ralf -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
