On 07/19/2013 06:55 AM, BOUQUE Anais wrote: > Hello, > I use autoreconf and configure, and I have a problem using configure : I use > the cl6x compiler, (./configure --host=c6x CC=cl6x) but when configure does > "cl6x -version" or "cl6x-v" or "cl6x -V", there is an error, because the > correct option to have the version of cl6x is "cl6x -version".
Well, maybe we should tweak autoconf to add '-version' to the list of options attempted. > configure:2102: cl6x -V </dev/null >&5 >>> WARNING: invalid compiler option -V (ignored) >>> ERROR: no source files, nothing to do > configure:2105: $? = 0 > configure:2128: checking for C compiler default output file name > configure:2131: cl6x -O2 -mv6600 -mf4 --abi=eabi -pr --symdebug:none > --visibility=default --linux --gcc > -I/vobs/elin/C66/ATELIER/sdk/c6x-uclinux/libc/usr/include/ > -I/vobs/elin/C66/ATELIER/sdk/lib/gcc/c6x-uclinux/4.5.1/include -march=c674x > -L/vobs/elin/C66/ATELIER/sdk/bin/../c6x-uclinux/libc/c674x -DC6X -march=c674x > -mdsbt -msdata=none -frename-registers -fremove-local-statics -O2 conftest.c > >&5 > > > Can I do something to solve that problem? But as for the "problem" of a noisy log file, this entire attempt to probe versions is merely informational, and should in no way prevent the rest of the configure script from using your compiler, regardless of whether we were able to guess your compiler's quirks for outputting a version number. > If you need more precise information, tell me, and I will send it to you. The only bug, if there is one, is that we should add one more option to attempt in the loops for version probing in lib/autoconf/c.m4. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
