configure problem

[Chris Johns]

On 27/12/17 3:16 pm, bin.wang at qkmtech.com wrote:
> ok ,sorry , i am new to rtems . 
> yes, i use the MSYS2 to build the tools. so i use the tools path in the xilinx
> sdk , as the document said ,i add the tools path to the PAHT envirment variable
> 
> you means i should use the pure eclipse ? and do not use the xilinx sdk?

It might be a good idea if you can.

Let me attempt to break down what is happening ....

1. RTEMS Tools, the GCC compiler, assembler and debugger. You need MSYS2 to
build these because of the autoconf configure used and size of the build. I also
think cygwin can be used but I do not test this.

2. RTEMS Kernel. I have only built RTEMS on Windows using MSYS2. In theory you
any working shell on Windows should be OK but I have not tested this. Again a
good working shell is needed because of the autoconf based build system.

Items 1 and 2 create native executables and suitable libraries and you can in
theory use any Windows environment that runs native Windows executables.

> now i get the follow error
> 
> //--------------------------------------------------------------------------------------------------------------------------------------
> 
> Generating Makefile in build directory: E:/workdir/pallas_SDKworkspace/rtems_kernel_build/build
> 
> sh -c "/E/workdir/pallas_SDKworkspace/rtems_kernel_build/rtems-4.11.2/configure --target=arm-rtems4.11 --prefix=/kernelinstall --enable-rtemsbsp=xilinx_zynq_zc702 --enable-tests --enable-posix --disable-networking --enable-cxx --enable-rtems-debug" 
> checking for gmake... no
> checking for gmake... no
> checking for make... make
> checking for RTEMS Version... 4.11.2
> checking build system type... i686-pc-mingw32
> checking host system type... i686-pc-mingw32
> checking target system type... arm-unknown-rtems4.11
> checking for a BSD-compatible install... /g/software/xilinx/SDK/2017.3/gnuwin/bin/ginstall -c
> configure: error: ls -t appears to fail.  Make sure there is not a broken
> configure: error: ls -t appears to fail.  Make sure there is not a broken
>   alias in your environment
This looks like the environment does not work with autoconf's configure file.

There is not much we can do.

Chris