GMP error when building aarch64-rtems-gcc on Mingw64

[jameszxj]

It has been there for a while. It is caused by the gmp configure parameter (in gcc/makefile.in line 12644 )


I change "--host=none-${host_vendor}-${host_os} --target=none-${host_vendor}-${host_os}"
to "--host=${host_alias} --target=${host_alias}", the building succeeds.
  


------------------ Original ------------------
From:                                                                                                                        "Ryan Long"                                                                                    <ryan.long at oarcorp.com>;
Date: Tue, Mar 22, 2022 05:33 AM
To: "devel"<devel at rtems.org>;

Subject: GMP error when building aarch64-rtems-gcc on Mingw64



While building gcc, arg3nexwm1 fails. The error follows

In file included from ../../../gnu-mirror-gcc-348fb9d/gmp/gmp-impl.h:146,
                 from fib_table.c:4:
../fib_table.h:4:1: warning: data definition has no type or storage class
    4 | Error, error, this data is for 32 bits
      | ^~~~~
../fib_table.h:4:1: warning: type defaults to 'int' in declaration of 
'Error' [-Wimplicit-int]
../fib_table.h:4:8: warning: type defaults to 'int' in declaration of 
'error' [-Wimplicit-int]
    4 | Error, error, this data is for 32 bits
      |        ^~~~~
../fib_table.h:4:20: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'data'
    4 | Error, error, this data is for 32 bits
      |                    ^~~~
fib_table.c:7:1: warning: data definition has no type or storage class
    7 | Error, error, this data is for 32 bits
      | ^~~~~
fib_table.c:7:1: warning: type defaults to 'int' in declaration of 
'Error' [-Wimplicit-int]
fib_table.c:7:8: warning: type defaults to 'int' in declaration of 
'error' [-Wimplicit-int]
    7 | Error, error, this data is for 32 bits
      |        ^~~~~
fib_table.c:7:20: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'data'
    7 | Error, error, this data is for 32 bits
      |                    ^~~~

This is due to GMP_NUMB_BITS not being equal to 32. Has anyone 
encountered this?

Thanks,

Ryan

_______________________________________________
devel mailing list
devel at rtems.org
http://lists.rtems.org/mailman/listinfo/devel