RTEMS - sparc/leon3 BSP configure script error
Chris Johns
chrisj at rtems.org
Mon Jan 19 20:52:17 UTC 2015
On 20/01/2015 3:22 am, Gedare Bloom wrote:
> Please keep this on the list where others may help.
>
> You should look at config.status for more info about what may have failed.
>
> On Mon, Jan 19, 2015 at 11:11 AM, Francois ARSENAULT
> <Francois.Arsenault at mdacorporation.com> wrote:
>> Hello,
>>
>> I have corrected the path to the cross-compiler and now the “configure” script should find the compiler (see the “which” command below).
>>
>> $ which sparc-rtems4.10-
>> sparc-rtems4.10-addr2line.exe sparc-rtems4.10-g++.exe sparc-rtems4.10-gprof.exe sparc-rtems4.10-readelf.exe
>> sparc-rtems4.10-ar.exe sparc-rtems4.10-gcc.exe sparc-rtems4.10-ld.exe sparc-rtems4.10-size.exe
>> sparc-rtems4.10-as.exe sparc-rtems4.10-gcc-4.3.3.exe sparc-rtems4.10-nm.exe sparc-rtems4.10-strings.exe
>> sparc-rtems4.10-c++.exe sparc-rtems4.10-gccbug sparc-rtems4.10-objcopy.exe sparc-rtems4.10-strip.exe
>> sparc-rtems4.10-c++filt.exe sparc-rtems4.10-gcov.exe sparc-rtems4.10-objdump.exe
>> sparc-rtems4.10-cpp.exe sparc-rtems4.10-gdb.exe sparc-rtems4.10-ranlib.exe
>>
>> Note: the cross-compiler came from Gaisler. We’ve used it in another project.
>>
>> Looking at the ./configure error:
>> …
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking for i686-pc-cygwin-gcc... i686-pc-cygwin-gcc
>> checking whether the C compiler works... no
>> configure: error: in `/cygdrive/c/COLKa/src/rtems-4.10.2/rtems_build/tools/build':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details
>> configure: error: /bin/sh '/cygdrive/c/COLKa/src/rtems-4.10.2/tools/build/configure' failed for tools/build
>>
>> It seems that there is an error in the …/build/tools/configure script.
>> Attached to this email, the “config.log” and the …/build/tools/configure script files.
>> The “config.log” file shows an error in tools/build/configure/configure:4454.
>> In tools/build/configure/configure:4454, this line is a blank line!!!
>>
>> I am not sure what is wrong here…
>> Any suggestion?
I suspect there is an issue with line endings. You need to make sure all
the configure scripts have the correct line ending. I suggest you try
something like:
$ dos2unix $(find . -name configure)
There maybe other files that need filtering. I cannot remember.
Chris
More information about the users
mailing list