rtems-source-builder on cygwin/64

emanuel stiebler emu at e-bbes.com
Sat Mar 14 10:03:30 UTC 2015


On 2015-03-14 00:59, Chris Johns wrote:
> On 13/03/2015 7:37 pm, emanuel stiebler wrote:
>> On 2015-03-13 05:55, Chris Johns wrote:
>>
>>> Have a look in this line ...
>>>
>>>
>>> https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/windows.py#n56
>>>
>>>
>>>
>>>
>>> .. and remove line 57 and make line 58 'host_triple = build_triple' so
>>> the host and build names are the same by default.
>>>
>>> If this works you might then be able to remove line 53 and allow 32bit
>>> or 64bit.
>>
>> error: failed to load CYGWIN_NT-6.1 host support
>> Build FAILED
>>
>> So I guess there more to copy ...
>
> I suspect an error in the editing. Any issue importing the module gives
> this exception. I suggest you run the Windows module directly using
> something like:
>
>   $ python windows.py
>
> It should show the error.

Hi,
it was an error in some white spaces, after editing the same in again it 
didn't complain anymore ...

But, anyway, it still "thinks" it is on MinGW?

RTEMS Source Builder - Set Builder, v0.5.0
Build Set: 4.11/rtems-arm
Build Set: 4.11/rtems-autotools.bset
Build Set: 4.11/rtems-autotools-internal.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-w64-mingw32-1
building: autoconf-2.69-x86_64-w64-mingw32-1
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-w64-mingw32-1
building: automake-1.12.6-x86_64-w64-mingw32-1
cleaning: autoconf-2.69-x86_64-w64-mingw32-1
cleaning: automake-1.12.6-x86_64-w64-mingw32-1
Build Set: Time 0:00:59.248904
Build Set: 4.11/rtems-autotools-base.bset
config: tools/rtems-autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-w64-mingw32-1
building: autoconf-2.69-x86_64-w64-mingw32-1
config: tools/rtems-automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-w64-mingw32-1
building: automake-1.12.6-x86_64-w64-mingw32-1
installing: autoconf-2.69-x86_64-w64-mingw32-1 -> /opt/rtems-4.11
installing: automake-1.12.6-x86_64-w64-mingw32-1 -> /opt/rtems-4.11
cleaning: autoconf-2.69-x86_64-w64-mingw32-1
cleaning: automake-1.12.6-x86_64-w64-mingw32-1
Build Set: Time 0:01:00.049505
Build Set: Time 0:01:59.298409
config: tools/rtems-binutils-2.24-1.cfg
package: arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1
download: ftp://ftp.gnu.org/gnu/binutils/binutils-2.24.tar.bz2 -> 
sources/binutils-2.24.tar.bz2
downloading: sources/binutils-2.24.tar.bz2 - 21.7MB of 21.7MB (100%)
building: arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1
error: building arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1
Build FAILED
   See error report: 
rsb-report-arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1.txt
error: building arm-rtems4.11-binutils-2.24-x86_64-w64-mingw32-1
Build Set: Time 0:06:50.131120
Build FAILED

And the failure is in binutils, because it doesn't know:

gcc -O2 -pipe 
-I/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.11/rtems-arm/opt/rtems-4.11/include 
-c -DHAVE_CONFIG_H -g -O2 -D__USE_MINGW_ACCESS  -I. 
-I../../binutils-2.24/libiberty/../include  -W -Wall -Wwrite-strings 
-Wc++-compat -Wstrict-prototypes -pedantic 
../../binutils-2.24/libiberty/pex-win32.c -o pex-win32.o
../../binutils-2.24/libiberty/pex-win32.c: In function 
'pex_win32_open_read':
../../binutils-2.24/libiberty/pex-win32.c:122:3: warning: implicit 
declaration of function '_open' [-Wimplicit-function-declaration]
    return _open (name, _O_RDONLY | (binary ? _O_BINARY : _O_TEXT));
    ^
../../binutils-2.24/libiberty/pex-win32.c:122:23: error: '_O_RDONLY' 
undeclared (first use in this function)
    return _open (name, _O_RDONLY | (binary ? _O_BINARY : _O_TEXT));
                        ^
../../binutils-2.24/libiberty/pex-win32.c:122:23: note: each undeclared 
identifier is reported only once for each function it appears in
../../binutils-2.24/libiberty/pex-win32.c:122:45: error: '_O_BINARY' 
undeclared (first use in this function)
    return _open (name, _O_RDONLY | (binary ? _O_BINARY : _O_TEXT));

So, probably still some mixup with the environment ...

Thanks for you help!!!




More information about the devel mailing list