Re: rtems-source-builder on cygwin/64, WAF?
On 2015-03-17 22:38, Chris Johns wrote: On 18/03/2015 7:28 am, Chris Johns wrote: I am testing this now as I needed to add 'merge' to the git module. Pushed as https://git.rtems.org/rtems-source-builder/commit/?id=b0f9e30fa46a8025b76bf86321ebe585de8972f4 OK, so I managed to compile the toolchains for arm, m68k and mips today. (and also compiled RTEMS for arm and two BSPs) So I guess it is working. Thanks! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 2015-03-17 17:37, Joel Sherrill wrote: On 3/17/2015 11:30 AM, emanuel stiebler wrote: On 2015-03-17 11:41, Chris Johns wrote: On 17/03/2015 2:48 am, Joel Sherrill wrote: Hmmm.. copying from the log you attached: This looks like somehow the the contents of ./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being tripped by whatever conditionals are set on your host. I see FreeBSD, Apple, and Linux sections of the file. You can build rtems-tools by hand easily and see what's going wrong in that file. It may be as easy as adding || defined(__cygwin__) or similar in the right place. I have pushed a fix for this. It is building on Cygwin. Which one did you update? I did a git pull on rtems-source-builder, and still got the same error ... This was an issue in rtems-tools. Can you see if you can update that and build it by hand? RSB may need a hash tag updated and Chris might not have done that. *** note sure on this *** On 2015-03-17 17:37, Joel Sherrill wrote: This was an issue in rtems-tools. Can you see if you can update that and build it by hand? RSB may need a hash tag updated and Chris might not have done that. *** note sure on this *** OK, this time it went through! Thanks! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 18/03/2015 7:28 am, Chris Johns wrote: I am testing this now as I needed to add 'merge' to the git module. Pushed as https://git.rtems.org/rtems-source-builder/commit/?id=b0f9e30fa46a8025b76bf86321ebe585de8972f4 Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 18/03/2015 3:37 am, Joel Sherrill wrote: On 3/17/2015 11:30 AM, emanuel stiebler wrote: On 2015-03-17 11:41, Chris Johns wrote: On 17/03/2015 2:48 am, Joel Sherrill wrote: Hmmm.. copying from the log you attached: This looks like somehow the the contents of ./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being tripped by whatever conditionals are set on your host. I see FreeBSD, Apple, and Linux sections of the file. You can build rtems-tools by hand easily and see what's going wrong in that file. It may be as easy as adding || defined(__cygwin__) or similar in the right place. I have pushed a fix for this. It is building on Cygwin. Which one did you update? I did a git pull on rtems-source-builder, and still got the same error ... This was an issue in rtems-tools. Can you see if you can update that and build it by hand? RSB may need a hash tag updated and Chris might not have done that. *** note sure on this *** It is tracking head. I am wondering if the git sequence being used is wrong and should be: git://git.rtems.org/rtems-tools.git?fetch?reset=hard?merge where we fetch, reset to erase any local patches applied and then merge any changes fetched. I am testing this now as I needed to add 'merge' to the git module. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
On 2015-03-17 11:41, Chris Johns wrote: On 17/03/2015 2:48 am, Joel
Sherrill wrote:
Hmmm.. copying from the log you attached:
This looks like somehow the the contents of
./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being
tripped by whatever conditionals are set on your host. I see FreeBSD,
Apple, and Linux sections of the file.
You can build rtems-tools by hand easily and see what's going
wrong in that file. It may be as easy as adding || defined(__cygwin__)
or similar in the right place.
I have pushed a fix for this. It is building on Cygwin.
Which one did you update? I did a git pull on rtems-source-builder,
and still got the same error ...
RTEMS Tools Project - Source Builder Error Report
Build: error: building rtems-tools-HEAD-1
Command Line: ../source-builder/sb-set-builder --log=l-arm.txt --jobs=4
--prefix=/opt/rtems-4.11 4.11/rtems-arm --no-clean
Python: 2.7.8 (default, Jul 25 2014, 14:04:36) [GCC 4.8.3]
git://git.rtems.org/rtems-source-builder.git/origin/7f7d388af88f56139d7c6a832b551c5366adcefc-modified
CYGWIN_NT-6.1 w530 1.7.35(0.287/5/3) 2015-03-04 12:09 x86_64
Tail of the build log:
script: 80: build_top=$(pwd)
script: 81: source_dir_rtems_tools=rtems-tools-HEAD-1
source setup: rtems-tools-HEAD-1: source rtems-tools -q -D -n rtems-tools-HEAD-1
making dir:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/sources/git
git: fetch: git://git.rtems.org/rtems-tools.git - sources/git/rtems-tools.git
git: reset: git://git.rtems.org/rtems-tools.git
git: checkout: git://git.rtems.org/rtems-tools.git = master
script: 82: cd
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
script: 83: ln -s
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/sources/git/rtems-tools.git
${source_dir_rtems_tools}
script: 84: cd rtems-tools-HEAD-1
script: 85: chmod -R a+rX,g-w,o-w .
script: 86: cd ${build_top}
script: 87: SB_CXC=no
script: 88: echo == clean %{buildroot}: ${SB_BUILD_ROOT}
script: 89: rm -rf ${SB_BUILD_ROOT}
script: 90: /bin/mkdir -p ${SB_BUILD_ROOT}
script: 91: echo == %build:
script: 92: build_top=$(pwd)
script: 93: if test x86_64-pc-cygwin != x86_64-pc-cygwin ; then
script: 94: RT_HOST=-host=x86_64-pc-cygwin
script: 95: else
script: 96: RT_HOST=
script: 97: fi
script: 98: cd ${source_dir_rtems_tools}
script: 99: ./waf configure ${RT_HOST} --prefix=/opt/rtems-4.11
script:100: ./waf
script:101: cd ${build_top}
script:102: echo == %install:
script:103: build_top=$(pwd)
script:104: rm -rf $SB_BUILD_ROOT
script:105: cd ${source_dir_rtems_tools}
script:106: ./waf --destdir=$SB_BUILD_ROOT install
script:107: cd ${build_top}
removing:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
making dir:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1
write script:
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1/doit
building: rtems-tools-HEAD-1
run: sh -ex
/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/rtems-tools-HEAD-1/doit
+ export
'SB_ORIG_PATH=/opt/rtems-4.11/bin:/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/PROGRAM
FILES/COMMON FILES/MICROSOFT SHARED/WINDOWS LIVE:/cygdrive/c/PROGRAM FILES
(X86)/COMMON FILES/MICROSOFT SHARED/WINDOWS LIVE:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/ICLS CLIENT:/cygdrive/c/PROGRAM FILES/INTEL/ICLS
CLIENT:/cygdrive/c/windows/SYSTEM32:/cygdrive/c/windows:/cygdrive/c/windows/SYSTEM32/WBEM:/cygdrive/c/windows/SYSTEM32/WINDOWSPOWERSHELL/V1.0:/cygdrive/c/PROGRAM
FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM
FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES
(X86)/INTEL/OPENCL SDK/2.0/BIN/X86:/cygdrive/c/PROGRAM FILES (X86)/INTEL/OPENCL
SDK/2.0/BIN/X64:/cygdrive/c/PROGRAM FILES/COMMON
FILES/LENOVO:/cygdrive/c/PROGRAM FILES (X86)/COMMON FILES/ULEAD
SYSTEMS/MPEG:/cygdrive/c/PROGRAM FILES (X86)/WINDOWS
LIVE/SHARED:/cygdrive/c/SWTOOLS/READYAPPS:/cygdrive/c/PROGRAM FILES
(X86)/SYMANTEC/VIP ACCESS CLIENT:/cygdrive/c/PROGRAM FILES (X86)/COMMON
FILES/LENOVO:/cygdrive/c/Program Files/ThinkPad/Bluetooth
Software:/cygdrive/c/Program Files/ThinkPad/Bluetooth
Software/syswow64:/cygdrive/c/Program Files (x86)/Intel/OpenCL
SDK/2.0/bin/x86:/cygdrive/c/Program Files (x86)/Intel/OpenCL
SDK/2.0/bin/x64:/cygdrive/c/Program Files/Intel/Intel(R) Management Engine
Components/DAL:/cygdrive/c/Program Files/Intel/Intel(R) Management Engine
Components/IPT:/cygdrive/c/Program Files (x86)/Intel/Intel(R) Management Engine
Components/DAL:/cygdrive/c/Program Files (x86)/Intel/Intel(R) Management Engine
Components/IPT:/cygdrive/c/Program Files (x86)/Common
Re: rtems-source-builder on cygwin/64, WAF?
On 3/17/2015 11:30 AM, emanuel stiebler wrote: On 2015-03-17 11:41, Chris Johns wrote: On 17/03/2015 2:48 am, Joel Sherrill wrote: Hmmm.. copying from the log you attached: This looks like somehow the the contents of ./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being tripped by whatever conditionals are set on your host. I see FreeBSD, Apple, and Linux sections of the file. You can build rtems-tools by hand easily and see what's going wrong in that file. It may be as easy as adding || defined(__cygwin__) or similar in the right place. I have pushed a fix for this. It is building on Cygwin. Which one did you update? I did a git pull on rtems-source-builder, and still got the same error ... This was an issue in rtems-tools. Can you see if you can update that and build it by hand? RSB may need a hash tag updated and Chris might not have done that. *** note sure on this *** -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available(256) 722-9985 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 2015-03-15 22:19, Chris Johns wrote: [ back on list ] I wasn't sure, people like to read this long log files ;-) Thanks. Can you please try the attached windows.py ? Sure. It seems to work. Is plowing through the sources for hours now ... Will report, if it really works later ... 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-pc-cygwin-1 building: autoconf-2.69-x86_64-pc-cygwin-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-pc-cygwin-1 building: automake-1.12.6-x86_64-pc-cygwin-1 cleaning: autoconf-2.69-x86_64-pc-cygwin-1 cleaning: automake-1.12.6-x86_64-pc-cygwin-1 Build Set: Time 0:01:01.136507 Build Set: 4.11/rtems-autotools-base.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-pc-cygwin-1 building: autoconf-2.69-x86_64-pc-cygwin-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-pc-cygwin-1 building: automake-1.12.6-x86_64-pc-cygwin-1 installing: autoconf-2.69-x86_64-pc-cygwin-1 - /opt/rtems-4.11 installing: automake-1.12.6-x86_64-pc-cygwin-1 - /opt/rtems-4.11 cleaning: autoconf-2.69-x86_64-pc-cygwin-1 cleaning: automake-1.12.6-x86_64-pc-cygwin-1 Build Set: Time 0:01:00.793307 Build Set: Time 0:02:01.929814 config: tools/rtems-binutils-2.24-1.cfg package: arm-rtems4.11-binutils-2.24-x86_64-pc-cygwin-1 building: arm-rtems4.11-binutils-2.24-x86_64-pc-cygwin-1 config: tools/rtems-gcc-4.9.2-newlib-git-1.cfg package: arm-rtems4.11-gcc-4.9.2-newlib-b75c57950318ed657807f87a4c694e7b8d68fcae-x86_64-pc-cygwin-1 git: fetch: git://sourceware.org/git/newlib.git - sources/git/newlib.git git: reset: git://sourceware.org/git/newlib.git git: checkout: git://sourceware.org/git/newlib.git = master git: checkout: git://sourceware.org/git/newlib.git = b75c57950318ed657807f87a4c694e7b8d68fcae building: arm-rtems4.11-gcc-4.9.2-newlib-b75c57950318ed657807f87a4c694e7b8d68fcae-x86_64-pc-cygwin-1 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64, WAF?
Hmmm.. copying from the log you attached: This looks like somehow the the contents of ./rtemstoolkit/elftoolchain/libelf/_libelf_config.h are not being tripped by whatever conditionals are set on your host. I see FreeBSD, Apple, and Linux sections of the file. You can build rtems-tools by hand easily and see what's going wrong in that file. It may be as easy as adding || defined(__cygwin__) or similar in the right place. [ 6/141] c: rtemstoolkit/elftoolchain/libelf/elf_cntl.c - build/rtemstoolkit/elftoolchain/libelf/elf_cntl.c.4.o ../rtemstoolkit/elftoolchain/libelf/elf.c:31:14: error: expected declaration specifiers or '...' before string constant LIBELF_VCSID($Id: elf.c 1345 2011-01-01 11:17:52Z jkoshy $); ^ ../rtemstoolkit/elftoolchain/libelf/elf.c:34:18: error: 'LIBELF_ARCH' undeclared here (not in a function) .libelf_arch = LIBELF_ARCH, ^ ../rtemstoolkit/elftoolchain/libelf/elf.c:35:22: error: 'LIBELF_BYTEORDER' undeclared here (not in a function) .libelf_byteorder = LIBELF_BYTEORDER, ^ ../rtemstoolkit/elftoolchain/libelf/elf.c:36:19: error: 'LIBELF_CLASS' undeclared here (not in a function) .libelf_class = LIBELF_CLASS, ^ ../rtemstoolkit/elftoolchain/libelf/elf_begin.c:44:14: error: expected declaration specifiers or '...' before string constant LIBELF_VCSID($Id: elf_begin.c 1923 2011-09-23 09:01:13Z jkoshy $); On 3/16/2015 10:16 AM, emanuel stiebler wrote: On 2015-03-15 22:19, Chris Johns wrote: [ back on list ] Thanks. Can you please try the attached windows.py ? OK, it seems to build most of the stuff, and fails in the WAF build :( 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-pc-cygwin-1 building: autoconf-2.69-x86_64-pc-cygwin-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-pc-cygwin-1 building: automake-1.12.6-x86_64-pc-cygwin-1 cleaning: autoconf-2.69-x86_64-pc-cygwin-1 cleaning: automake-1.12.6-x86_64-pc-cygwin-1 Build Set: Time 0:00:54.896497 Build Set: 4.11/rtems-autotools-base.bset config: tools/rtems-autoconf-2.69-1.cfg package: autoconf-2.69-x86_64-pc-cygwin-1 building: autoconf-2.69-x86_64-pc-cygwin-1 config: tools/rtems-automake-1.12.6-1.cfg package: automake-1.12.6-x86_64-pc-cygwin-1 building: automake-1.12.6-x86_64-pc-cygwin-1 installing: autoconf-2.69-x86_64-pc-cygwin-1 - /opt/rtems-4.11 installing: automake-1.12.6-x86_64-pc-cygwin-1 - /opt/rtems-4.11 cleaning: autoconf-2.69-x86_64-pc-cygwin-1 cleaning: automake-1.12.6-x86_64-pc-cygwin-1 Build Set: Time 0:00:52.899693 Build Set: Time 0:01:47.811790 config: devel/expat-2.1.0-1.cfg package: expat-2.1.0-x86_64-pc-cygwin-1 building: expat-2.1.0-x86_64-pc-cygwin-1 config: tools/rtems-binutils-2.24-1.cfg package: arm-rtems4.11-binutils-2.24-x86_64-pc-cygwin-1 building: arm-rtems4.11-binutils-2.24-x86_64-pc-cygwin-1 config: tools/rtems-gcc-4.9.2-newlib-git-1.cfg package: arm-rtems4.11-gcc-4.9.2-newlib-b75c57950318ed657807f87a4c694e7b8d68fcae-x86_64-pc-cygwin-1 git: fetch: git://sourceware.org/git/newlib.git - sources/git/newlib.git git: reset: git://sourceware.org/git/newlib.git git: checkout: git://sourceware.org/git/newlib.git = master git: checkout: git://sourceware.org/git/newlib.git = b75c57950318ed657807f87a4c694e7b8d68fcae building: arm-rtems4.11-gcc-4.9.2-newlib-b75c57950318ed657807f87a4c694e7b8d68fcae-x86_64-pc-cygwin-1 config: tools/rtems-gdb-7.9-1.cfg package: arm-rtems4.11-gdb-7.9-x86_64-pc-cygwin-1 download: http://ftp.gnu.org/gnu/gdb/gdb-7.9.tar.xz - sources/gdb-7.9.tar.xz downloading: sources/gdb-7.9.tar.xz - 17.0MB of 17.0MB (100%) warning: gdb-7.9.tar.xz: no hash found Creating source directory: patches download: http://git.rtems.org/rtems-tools/plain/tools/4.11/gdb/gdb-sim-arange-inline.diff - patches/gdb-sim-arange-inline.diff redirect: https://git.rtems.org/rtems-tools/plain/tools/4.11/gdb/gdb-sim-arange-inline.diff downloading: patches/gdb-sim-arange-inline.diff - 761.0 bytes of 761.0 bytes (100%) download: http://git.rtems.org/rtems-tools/plain/tools/4.11/gdb/gdb-sim-cgen-inline.diff - patches/gdb-sim-cgen-inline.diff redirect: https://git.rtems.org/rtems-tools/plain/tools/4.11/gdb/gdb-sim-cgen-inline.diff downloading: patches/gdb-sim-cgen-inline.diff - 706.0 bytes of 706.0 bytes (100%) building: arm-rtems4.11-gdb-7.9-x86_64-pc-cygwin-1 config: tools/rtems-tools-4.11-1.cfg package: rtems-tools-HEAD-1 git: clone: git://git.rtems.org/rtems-tools.git - sources/git/rtems-tools.git git: fetch: git://git.rtems.org/rtems-tools.git - sources/git/rtems-tools.git git: reset: git://git.rtems.org/rtems-tools.git git: checkout: git://git.rtems.org/rtems-tools.git = master building: rtems-tools-HEAD-1 error:
Re: rtems-source-builder on cygwin/64
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!!! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
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. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
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 ... ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 13/03/2015 3:12 am, emanuel stiebler wrote: On 2015-03-12 02:56, Chris Johns wrote: I invested a large amount time last year attempting to get cygwin to build native tools and gave up. I just could not get anything close to stable and then I really had no idea what I had got cygwin to actually install (I suspect that is just my lack of knowledge). I am not sure about building cygwin hosted versions of the tools. Ok, Chris, but how would I even start? On Cygwin, it tries to build the MinGW32 version of it, how can I trigger it to do a native cygwin/64 build? 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. Note, a user can always cross-compile for MinGW with cygwin using --host command line option so nothing is lost with this change. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 12/03/2015 10:38 pm, e...@e-bbes.com wrote: Zitat von Chris Johns chr...@rtems.org: On 12/03/2015 5:52 pm, emanuel stiebler wrote: OK, is there a option which downloads and patches everything and then tries do compile? I am not sure I understand. To get the latest RSB changes just do a pull with git, that is 'git pull' in the RSB clone. The RSB will download all the required source and patch it when building. Yes, I see. It downloads the source, the patches, patches and compiles, and gets the next package. I wanted to download everything first, and then try to compile. (slow network at home) Try adding the options '--dry-run --with-download' to your normal RSB command line. It should create and download the source into the source directory and patches into the patches directory. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 12/03/2015 5:52 pm, emanuel stiebler wrote: On 2015-03-12 02:56, Chris Johns wrote: On 12/03/2015 4:59 am, emanuel stiebler wrote: On 2015-03-11 18:40, Joel Sherrill wrote: On 3/11/2015 12:12 PM, emanuel stiebler wrote: Hi all, should it work at the moment? Since Chris is likely the best one to answer that and he won't be online for at least a a few hours, give it a try. You will know the answer before he wakes up. :) I do not test cygwin but will accept patches if they look ok. OK, is there a option which downloads and patches everything and then tries do compile? I am not sure I understand. To get the latest RSB changes just do a pull with git, that is 'git pull' in the RSB clone. The RSB will download all the required source and patch it when building. And, where to change the -j 8 on the makefiles? I noticed, that sometimes cygwin doesn't get the process finished right and waits. So for debugging, -j 1 should be better .. Pass '--jobs=none' to the RBS as an option. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
Zitat von Chris Johns chr...@rtems.org: On 12/03/2015 5:52 pm, emanuel stiebler wrote: OK, is there a option which downloads and patches everything and then tries do compile? I am not sure I understand. To get the latest RSB changes just do a pull with git, that is 'git pull' in the RSB clone. The RSB will download all the required source and patch it when building. Yes, I see. It downloads the source, the patches, patches and compiles, and gets the next package. I wanted to download everything first, and then try to compile. (slow network at home) And, where to change the -j 8 on the makefiles? I noticed, that sometimes cygwin doesn't get the process finished right and waits. So for debugging, -j 1 should be better .. Pass '--jobs=none' to the RBS as an option. Will try, thanks! ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
rtems-source-builder on cygwin/64
Hi all, should it work at the moment? All the best, emanuel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 2015-03-11 18:40, Joel Sherrill wrote: On 3/11/2015 12:12 PM, emanuel stiebler wrote: Hi all, should it work at the moment? Since Chris is likely the best one to answer that and he won't be online for at least a a few hours, give it a try. You will know the answer before he wakes up. :) I'm on cygwin, and it sits after just few hundred lines in /bin/sh ./libtool --silent --mode=link gcc -O2 -pipe -I/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/include -std=gnu99 -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -no-undefined -version-info 7:0:6 -rpath /opt/rtems-4.11/lib -L/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/lib -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo and cpu usage goes back to 0% ... ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 3/11/2015 12:59 PM, emanuel stiebler wrote: On 2015-03-11 18:40, Joel Sherrill wrote: On 3/11/2015 12:12 PM, emanuel stiebler wrote: Hi all, should it work at the moment? Since Chris is likely the best one to answer that and he won't be online for at least a a few hours, give it a try. You will know the answer before he wakes up. :) I'm on cygwin, and it sits after just few hundred lines in /bin/sh ./libtool --silent --mode=link gcc -O2 -pipe -I/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/include -std=gnu99 -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -no-undefined -version-info 7:0:6 -rpath /opt/rtems-4.11/lib -L/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/lib -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo and cpu usage goes back to 0% ... There should be a log file rsb-* with more details. Without that, we are just guessing. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available(256) 722-9985 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 3/11/2015 12:12 PM, emanuel stiebler wrote: Hi all, should it work at the moment? Since Chris is likely the best one to answer that and he won't be online for at least a a few hours, give it a try. You will know the answer before he wakes up. :) I know there are still a couple of MSYS2 issues but I doubt those apply to Cygwin. It probably should just work. If it doesn't, report it. All the best, emanuel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel -- Joel Sherrill, Ph.D. Director of Research Development joel.sherr...@oarcorp.comOn-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available(256) 722-9985 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: rtems-source-builder on cygwin/64
On 12/03/2015 4:59 am, emanuel stiebler wrote: On 2015-03-11 18:40, Joel Sherrill wrote: On 3/11/2015 12:12 PM, emanuel stiebler wrote: Hi all, should it work at the moment? Since Chris is likely the best one to answer that and he won't be online for at least a a few hours, give it a try. You will know the answer before he wakes up. :) I do not test cygwin but will accept patches if they look ok. I invested a large amount time last year attempting to get cygwin to build native tools and gave up. I just could not get anything close to stable and then I really had no idea what I had got cygwin to actually install (I suspect that is just my lack of knowledge). I am not sure about building cygwin hosted versions of the tools. I have always built and used native Windows tools and up until recently I have been using a Canadian cross (Cxc) build on FreeBSD. Native Windows tools run at the best possible speed on Windows because there is no POSIX emulation layer and they integrate into other Windows tools, such as IDEs, because the paths used are standard Windows paths. When combined with waf as a build system the overall performance and stability is excellent. I have recently just pushed changes into the RSB to support MSYS2 and I am in the process of updating the RSB documentation to outline what you need to do. I have been able to build an ARM compiler tool chain on Windows using MSYS2 and this is first for many years. It take a while so please be patient. The doco update is: -- MSYS2 This is a new version of the old MinGW project's original MSYS based around the Arch Linux pacman packager. MSYS and MSYS2 are a specific fork of the Cygwin project with some fundamental changes in the handling of paths and mounts that allow easy interaction between the emulated POSIX environment and the native Windows environment. Install MSYS2 using the installer you can download from https://msys2.github.io/. Follow the instructions on the install page and make sure you remove any global path entries to any other Cygwin, MinGW, MSYS or packages that may uses a Cygwin DLL, for example some ports of Git. To build the tools you need install the following packages using pacman: $ pacman -S git cvs bison make texinfo patch unzip diffutils tar \ mingw64/mingw-w64-x86_64-gcc mingw64/mingw-w64-x86_64-binutils To build make sure you add '--without-python --jobs=none' to the standard RSB command line. MSYS2 has a temp file name issue and so the GNU AR steps on itself when running in parallel on SMP hardware which means we have to set the jobs option to none. Install a suitable version of Python from http://www.python.org/ and add it to the start of your path. The MSYS2 python does not work with waf. -- Finally there are a couple of issues we are looking into: 1. The gdb-7.8.2 does not build for Windows. We need gdb-7.9 however some local RTEMS patches need updating before we can switch all targets to that version. The ARM target has been switched. 2. Building rtems-tools, which happens when building the tools, is failing for some Windows users. The RTEMS ticket #2205 details the issue. If you can add anything please do. I'm on cygwin, and it sits after just few hundred lines in /bin/sh ./libtool --silent --mode=link gcc -O2 -pipe -I/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/include -std=gnu99 -I./lib -I. -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -no-undefined -version-info 7:0:6 -rpath /opt/rtems-4.11/lib -L/cygdrive/d/_home/emu/RTEMS.Work/rtems-source-builder/rtems/build/tmp/sb-emu/4.10/rtems-arm/opt/rtems-4.11/lib -o libexpat.la lib/xmlparse.lo lib/xmltok.lo lib/xmlrole.lo and cpu usage goes back to 0% ... At a guess this looks like a make issue with the -j option which is the default for the RSB. try '--jobs=none'. I have observed both MinGW MSYS and Cygwin suffer from incorrect handling of the wait status returned from fork calls in make which results in make stalling and this happening. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
