Message from discussion passing uint64_t integer to a function that takes uint64_t converts it to 32 bit
Received: by 10.66.78.170 with SMTP id c10mr3190402pax.22.1349626251224;
Sun, 07 Oct 2012 09:10:51 -0700 (PDT)
Received: by 10.68.225.39 with SMTP id rh7ls20306806pbc.7.gmail; Sun, 07 Oct
2012 09:10:50 -0700 (PDT)
Received: by 10.68.219.198 with SMTP id pq6mr4170227pbc.0.1349626250820;
Sun, 07 Oct 2012 09:10:50 -0700 (PDT)
Date: Sun, 7 Oct 2012 09:10:49 -0700 (PDT)
From: Sarvi Shanmugham <sarvil...@gmail.com>
Subject: Re: [python-cffi] passing uint64_t integer to a function that takes
uint64_t converts it to 32 bit
Content-Type: text/plain; charset=UTF-8
Yes. I am using the _cffi_backend built for the build host during the compilation.
Which is why a test load of the shared so cross built for the target host generates trace back that I have to ignore cross builds.
We are compiling some 12 other python extensions without any emulators the same way I am compiling these cffi extensions.
I can't find anything through google on autoconf and emulations for cross compilation.
And we don't use it for any of the more then 100 or some components that we cross compile.
May be I don't understand the issue with data types and sizes
From what I can tell, int, long sizes vary with platforms. If you really want fixed length data types it looks like you need to use intN_t from stdint.h. And considering that cffi has basic data types thare infact intN_t, shouldn't that be the right choice?