Igor Bukanov wrote:
On 1/25/06, Robert Dewar <[EMAIL PROTECTED]> wrote:
A convenient way to get the endianness is to use
the System.Bit_Order attribute in Ada.
But this requires to run the program on the target which is not
possible with a cross-compiler. Or is there a trick to declare
somet
On 1/25/06, Robert Dewar <[EMAIL PROTECTED]> wrote:
> A convenient way to get the endianness is to use
> the System.Bit_Order attribute in Ada.
But this requires to run the program on the target which is not
possible with a cross-compiler. Or is there a trick to declare
something in Ada that would
Igor Bukanov wrote:
On 1/25/06, Paul Brook <[EMAIL PROTECTED]> wrote:
Autoconf already has tests for things like this. Something along the lines of:
const char D_P_S_4[sizeof(void *) == 4 : -1 : 1];
const char D_P_S_8[sizeof(void *) == 8 : -1 : 1];
Then see which compiles, or grep the error m
On 1/25/06, Paul Brook <[EMAIL PROTECTED]> wrote:
> Autoconf already has tests for things like this. Something along the lines of:
>
> const char D_P_S_4[sizeof(void *) == 4 : -1 : 1];
> const char D_P_S_8[sizeof(void *) == 8 : -1 : 1];
>
> Then see which compiles, or grep the error messages.
Righ
On Wednesday 25 January 2006 10:20, Igor Bukanov wrote:
> Is there any option to ask GCC to print various size and alignment
> info on the target platform? This would be very nice during cross
> compilation when one can not run the executables to autoconfigure for
> such parameters.
>
> Currently
Is there any option to ask GCC to print various size and alignment
info on the target platform? This would be very nice during cross
compilation when one can not run the executables to autoconfigure for
such parameters.
Currently I consider for that a hack like copiling the following source:
#in
