Building rtems toolchain with fortran support error

[Joel Sherrill]

On Mon, Nov 21, 2016 at 9:24 AM, Ricardo Derbes <rmderbes at gmail.com> wrote:

> Hello.
> I'm trying to build rtems toolchain for i386 using
> rtems-source-builder with fortran support (--with-fortran option).
> The RSB I'm using has been dowloaded from git, commit
> 534332f22a66f16b4022e87ae50c11ff20c98dcb from Sep 12 2016.
>
> The full command line is:
> ../source-builder/sb-set-builder
> --prefix=~/devel4.12-i386.fortran/rtems4.12 4.12/rtems-i386
> --without-rtems --with-fortran
>
> When trying to build gcc, it fails with the following errors (excerpt
> from report file
> rsb-report-i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1.txt):
>
> Tail of the build log:
> ~/devel4.12-i386.fortran/rtems-source-builder/rtems/
> build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/
> include/ieeefp.h:196:38:
> error: 'EXT_FRACHBITS' undeclared here (not in a function)
> __ieee_ext_field_type  ext_frach : EXT_FRACHBITS;
>                                       ^~~~~~~~~~~~~
> ~/devel4.12-i386.fortran/rtems-source-builder/rtems/
> build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/
> include/ieeefp.h:196:26:
> error: bit-field 'ext_frach' width not an integer constant
> __ieee_ext_field_type  ext_frach : EXT_FRACHBITS;
>                           ^~~~~~~~~
> /home/dev/devel4.12-i386.fortran/rtems-source-builder/
> rtems/build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/
> include/ieeefp.h:197:3:
> error: unknown type name '__ieee_ext_field_type'
>    __ieee_ext_field_type  ext_exp   : EXT_EXPBITS;
>    ^~~~~~~~~~~~~~~~~~~~~
> ~/devel4.12-i386.fortran/rtems-source-builder/rtems/
> build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/
> include/ieeefp.h:197:38:
> error: 'EXT_EXPBITS' undeclared here (not in a function)
> __ieee_ext_field_type  ext_exp   : EXT_EXPBITS;
>                                       ^~~~~~~~~~~
> /home/dev/devel4.12-i386.fortran/rtems-source-builder/
> rtems/build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/
> include/ieeefp.h:197:26:
> error: bit-field 'ext_exp' width not an integer constant
> __ieee_ext_field_type  ext_exp   : EXT_EXPBITS;
>                           ^~~~~~~
> ~/devel4.12-i386.fortran/rtems-source-builder/rtems/
> build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/
> include/ieeefp.h:198:3:
> error: unknown type name '__ieee_ext_field_type'
> __ieee_ext_field_type  ext_sign  : 1;
>    ^~~~~~~~~~~~~~~~~~~~~
>
> As for my application I need fortran support, how can I fix this problem?
> As long I can see, all symbols that the compiler claims as undeclared
> are indeed declared and accessible in file
> ~/devel4.12-i386.fortran/rtems-source-builder/rtems/
> build/i386-rtems4.12-gcc-6-20160609-newlib-2.4.0.
> 20160527-x86_64-linux-gnu-1/gcc-6-20160609/newlib/libc/include/ieeefp.h
> May be it's missing a symbol, e.g a proper value for LDBL_MANT_DIG ?
>
>
I see that GCC predefines these symbols:

#define __FLT_MANT_DIG__ 24
#define __DEC64_MANT_DIG__ 16
#define __LDBL_MANT_DIG__ 53
#define __DBL_MANT_DIG__ 53
#define __DEC32_MANT_DIG__ 7
#define __DEC128_MANT_DIG__ 34

And ieeefp.h in newlib has this:

#elif LDBL_MANT_DIG == 53
/* This happens when doubles are 32-bits and long doubles are 64-bits.  */
#define EXT_EXPBITS     11
#define EXT_FRACHBITS   20
#define EXT_FRACLBITS   32
#define __ieee_ext_field_type unsigned long

I am suspicious that the ifdef should use __LDBL_MANT_DIG__  not
LDBL_MANT_DIG.

But I will have to ask on the newlib mailing list to get an answer.

--joel



> Thank you
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20161121/85a9f4f2/attachment.html>