Opened on 02/15/16 at 14:50:34
Last modified on 12/02/18 at 22:34:53
#2581 assigned defect
Some bugfix for RTEMS-source-builder
Reported by: | merlo | Owned by: | Chris Johns |
---|---|---|---|
Priority: | low | Milestone: | 4.9.5 |
Component: | config | Version: | 4.9 |
Severity: | minor | Keywords: | rtems-source-builder |
Cc: | Blocked By: | ||
Blocking: |
Description
Hi. I added a patch in the newlib patch command for RTEMS 4.9 Toolchain. For this versions I also resolved some hash warnings and I added the --without-rtems option.
Attachments (3)
Change History (10)
Changed on 02/15/16 at 14:52:31 by merlo
Attachment: | 0001-Fix-hash-warnings-and-patch-command-for-newlib.patch added |
---|
Changed on 02/15/16 at 14:52:40 by merlo
Attachment: | 0002-Fix-hash-warnings.patch added |
---|
Changed on 02/15/16 at 14:52:47 by merlo
Attachment: | 0003-Add-management-for-without-rtems-option.patch added |
---|
comment:1 Changed on 02/15/16 at 16:33:53 by Gedare Bloom
Milestone: | → 4.9.5 |
---|---|
Owner: | set to Chris Johns |
Status: | new → assigned |
comment:2 Changed on 03/16/16 at 06:31:05 by Chris Johns
comment:3 Changed on 03/16/16 at 08:09:33 by merlo
Newlib bug and hash warnings are now fixed. I added --without-rtems option for the file rtems-kernel-4.9.6-1.cfg, as indicated in the project web page, and this option is still missing. Thanks.
comment:4 Changed on 03/16/16 at 08:16:01 by Chris Johns
The doco maybe out of date.
I have implemented general support for --with/--without support. The logic can appear a bit awkward, eg --with-blue=no is the same as --without-blue which is the same as --without-blue=yes which is not the same as --without-blue=no.
If you try the command line to the RSB and test this I would welcome it.
I have also added --with-rtemsbsp as a list, eg --with-rtemsbsp="erc32 sis". Also --with-rtems-test and --with-rtems-smp.
comment:5 Changed on 04/12/16 at 13:34:28 by merlo
Sorry for the late response.
Today I cloned the last version of RTEMS-Source-Builder and I built by:
../source-builder/sb-set-builder --log=log-m68k.txt --without-rtems --prefix=$HOME/development/rtems/4.9 4.9/rtems-m68k
RTEMS Source Builder - Set Builder, 4.12 (334356248183)
Build Set: 4.9/rtems-m68k
config: devel/expat-2.1.0-1.cfg
package: expat-2.1.0-x86_64-linux-gnu-1
building: expat-2.1.0-x86_64-linux-gnu-1
reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.txt
reporting: devel/expat-2.1.0-1.cfg -> expat-2.1.0-x86_64-linux-gnu-1.xml
config: tools/rtems-binutils-2.19.1-1.cfg
package: m68k-rtems4.9-binutils-2.19.1-x86_64-linux-gnu-1
warning: binutils-2.19.1.tar.bz2: no hash found
building: m68k-rtems4.9-binutils-2.19.1-x86_64-linux-gnu-1
reporting: tools/rtems-binutils-2.19.1-1.cfg -> m68k-rtems4.9-binutils-2.19.1-x86_64-linux-gnu-1.txt
reporting: tools/rtems-binutils-2.19.1-1.cfg -> m68k-rtems4.9-binutils-2.19.1-x86_64-linux-gnu-1.xml
config: tools/rtems-gcc-4.3.2-newlib-1.16.0-1.cfg
package: m68k-rtems4.9-gcc-4.3.2-newlib-1.16.0-x86_64-linux-gnu-1
building: m68k-rtems4.9-gcc-4.3.2-newlib-1.16.0-x86_64-linux-gnu-1
reporting: tools/rtems-gcc-4.3.2-newlib-1.16.0-1.cfg -> m68k-rtems4.9-gcc-4.3.2-newlib-1.16.0-x86_64-linux-gnu-1.txt
reporting: tools/rtems-gcc-4.3.2-newlib-1.16.0-1.cfg -> m68k-rtems4.9-gcc-4.3.2-newlib-1.16.0-x86_64-linux-gnu-1.xml
config: tools/rtems-gdb-6.8-1.cfg
package: m68k-rtems4.9-gdb-6.8-x86_64-linux-gnu-1
building: m68k-rtems4.9-gdb-6.8-x86_64-linux-gnu-1
reporting: tools/rtems-gdb-6.8-1.cfg -> m68k-rtems4.9-gdb-6.8-x86_64-linux-gnu-1.txt
reporting: tools/rtems-gdb-6.8-1.cfg -> m68k-rtems4.9-gdb-6.8-x86_64-linux-gnu-1.xml
config: tools/rtems-kernel-4.9.6-1.cfg
package: m68k-rtems4.9-kernel-4.12 (334356248183)-1
building: m68k-rtems4.9-kernel-4.12 (334356248183)-1
error: building m68k-rtems4.9-kernel-4.12 (334356248183)-1
Build FAILED
So, --without-rtems has no effect. I also tried --with-rtems=no, but the result is the same. Is it set something wrong?
comment:6 follow-up: 7 Changed on 11/30/18 at 09:36:40 by shashvat jain
The m68k arch seems to build without any error for me , is this problem solved already ?
comment:7 Changed on 12/02/18 at 22:34:53 by Chris Johns
Replying to shashvat jain:
The m68k arch seems to build without any error for me , is this problem solved already ?
Did you try the 4.9 branch?
Please check the RSB and if these changes are still needed. Thanks.