If your system is 32-bit, I don't think that type (uint128_t
) is available. You might email the developers of GATB with a bug report containing more details about your system.
Hello,
GATB uses cmake for building its software, and in your case, it seems that the uint128 availibility is wrongly set to true by cmake. After that, when the "make" command is launched, the compiler tries to use something not present which causes the compilation issue you got.
Just to be sure, could you please launch the cmake command and give us the console output? Note: if you have already launched the cmake command, it should be better to remove all its generated files (like CMakeCache.txt for instance). A simple way is to delete the "build" directory, create a new "build" directory and go into it, and then launch "cmake .."
Erwan Drézen (GATB team)
That was probably a misunderstanding, I don't recall proposing to use the binary release in that case.. I recall advising to develop on a 64 bits machine. Although, in light of Erwan's comment, maybe it will be possible to use a 32 bits machine after all, in case this is a bug related to cmake?
Ok, so cmake seems to correctly detect that 32 bits system can't use uint128.
By the way, is it possible for you to compile the code on your 32 bits system and tell me if it works ?
Actually, we don't generate GATB binaries for 32 bits systems, so it would useful for us to know if it works.
Erwan
Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
I've emailed the main GATB developer (edrezen) about this
Hi,
Thank you a lot ...
Thank you for your answer
My system is 64 bit. When I type on terminal
grep flags /proc/cpuinfo
I getlm is corresponding to 64 bit !!!
THANK YOU
To make 100% sure, what's the output of the
uname -a
command?That gives
Thanks
That is a 32 bits Linux even though your CPU supports 64 bits (see http://stackoverflow.com/questions/246007/how-to-determine-whether-a-given-linux-is-32-bit-or-64-bit).