Building RTEMS 4.12 for ARM using source builder fails

[Chris Johns]

On 27/10/2017 04:21, Brendan McNally wrote:
> Hello - 
> 
> Noob here, attempting to build RTEMS tools using the Source Builder for the ARM
> architecture.

Welcome.

> I'm hoping someone can steer me straight.

It is looking pretty good.

> Here's the rundown:
> 
> Host:
> Win10pro x64, using MSYS2 (20161025).
> 
> sb-check identified some early problems with my python installation. I had
> originally installed Python 3.6.3 for windows from python.org
> <http://python.org>, then -- when that was unsuccessful (complained about
> .startswith() args) -- rolled back to 2.7.14, also from python.org
> <http://python.org>. This was also unsuccessful; sb-check reported issues with
> host config. Uninstalled both of these, and installed mingw64/python2 from
> msys2, per comments in source-builder/sb/windows.py, and that allwed sb-check to
> complete successfully.

The Windows section of the user manual contains details about building on Windows:

 https://docs.rtems.org/branches/master/user/hosts/index.html#microsoft-windows

The Python section explains the issue with Python on Windows. We are governed by
GDB and what it needs.

> Well, with one warning about SVN.
> 
>      warning: exe: absolute exe found in path: (__svn) /usr/bin/svn
> 

This can be ignored.

> I attempt to build the tools using the following command:
>    
>     ../source-builder/sb-set-builder --log=l-arm.txt \
> --prefix=$HOME/development/rtems/4.12 4.12/rtems-arm
> 
> and it fails building newlib with the following info:
> 
>    config: tools/rtems-gcc-7.2.0-newlib-2.5.0.20170922-1.cfg
>    package: arm-rtems4.12-gcc-7.2.0-newlib-2.5.0.20170922-x86_64-w64-mingw32-1
>    building: arm-rtems4.12-gcc-7.2.0-newlib-2.5.0.20170922-x86_64-w64-mingw32-1
>    error: building arg7n2xwm1
>    Build FAILED
>      See error report:
> rsb-report-arm-rtems4.12-gcc-7.2.0-newlib-2.5.0.20170922-x86_64-w64-mingw32-1.txt
>    error: building arg7n2xwm1
> 
> I also tried building with the additional flag --jobs=none, and receive the same
> error.
> 
> Looking in the report, it's complaining about an include file that cannot be
> located.
> 
> In file included from
> ../../../../../../../../../../gcc-7.2.0/newlib/libm/machine/arm/s_ceil.c:39:0:
> 
> ../../../../../../../../../../gcc-7.2.0/newlib/libm/machine/arm/../../math/s_ceil.c:23:10:
> fatal error: fdlibm.h: No such file or directory
> 
>  #include "fdlibm.h"
>           ^~~~~~~~~~
> compilation terminated.
> 
> Full report is attached.

I have just completed an ARM build on Win10 (fully updated) without error. I
noticed in the report's command line you are building under:

 C:/msys64/home/brendan/development/rtems/4.12

This results in file names that are longer than 260 characters which is the
default max. path length for the win32 API. Please review the comments here:

 https://docs.rtems.org/branches/master/user/hosts/index.html#windows-path-length

I am currently using 'D:\opt\rtems\rsb.git' for the RSB repo which works.

Chris