2011/10/20 Josh Blum
<address@hidden>
>
> Volk usually also fails on the old install, the problem is , I think it
> should detect that it was no good and take it out of the build entirely?
>
No, this is a bug that needs to be fixed. Please help. Provide compiler
version gcc --version and all error verbose. Thanks.
gcc --version: gcc (Gentoo 4.3.4 p1.2, pie-10.1.5) 4.3.4
error from make is in make.log
Furthermore stdout wrote:
[ 0%] Generating ../include/volk/volk.h, volk.c, volk_init.h, ../include/volk/volk_typedefs.h, ../include/volk/volk_cpu.h, volk_cpu.c, ../include/volk/volk_config_fixed.h, volk_environment_init.c, volk_environment_init.h, volk_machines.h, volk_machines.c, volk_machine_generic.c, volk_machine_sse2_only.c, volk_machine_sse2_32.c, volk_machine_sse3_32.c, volk_machine_ssse3_32.c, volk_machine_sse4_a_32.c, volk_machine_sse4_1_32.c, volk_machine_sse4_2_32.c
Scanning dependencies of target volk
[ 0%] Building C object volk/lib/CMakeFiles/volk.dir/volk_prefs.c.o
[ 0%] Building C object volk/lib/CMakeFiles/volk.dir/volk_rank_archs.c.o
[ 0%] Building C object volk/lib/CMakeFiles/volk.dir/volk.c.o
before dying
>
>> Also, cmake -DENABLE_VOLK=OFF <srcdir> will disable it.
>>
>> Yeah, found that when i posted the output of cmake to a file and read it,
> could there be some more intuitive way of finding this out than
> trial-and-error?
cmake-gui, ccmake (ncurses) would make it more obvious. Also future
documentation. :-)
Ok, sooo much easier and understandable :) You should suggest this as the default method of configuring :D
> I think the configurescript should bypass the volk entirely when it cannot
> build it?
>
How can the configure know that volk cannot be built?
Take a look in configure.log, it says a lot about things I do not have, might this not be an indicator?
-Josh
make.log