#2995 closed defect (fixed)
Missing bsets
Reported by: | Hassan Karim | Owned by: | joel.sherrill@… |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | tool/rsb | Version: | 5 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
When I went to rebuild based on 4.12, I cloned from github.
I am no longer getting all of the b-sets that I was expecting. Specifically, 4.12/rtems-sparc
Chris Johns said to submit it as a bug. It must have happened within the last couple of weeks. As my scripts that automated these tasks were working as of around 3/1/2017
git clone git://git.rtems.org/rtems-source-builder.git
$SETBLDRSCRIPTDIR/sb-set-builder --list-bsets
RTEMS Source Builder - Set Builder, 4.12 (2074bd1168ee)
Examining: config
Examining: ../rtems/src/rtems-source-builder/source-builder/config
Examining: ../rtems/src/rtems-source-builder/bare/config
devel/autotools-base.bset
devel/autotools-internal.bset
devel/autotools.bset
devel/dtc.bset
devel/libtool.bset
devel/libusb.bset
devel/or1ksim.bset
devel/qemu.bset
gnu-tools-4.6.bset
gnu-tools-4.8.2.bset
lang/gcc491.bset
Change History (9)
comment:1 Changed on 04/17/17 at 03:29:20 by Joel Sherrill
comment:2 Changed on 04/17/17 at 03:44:58 by Hassan Karim
What could I look for specifically by hand in the git repository?
comment:3 Changed on 04/17/17 at 14:32:04 by Joel Sherrill
I don't think you need to look at anything. I can confirm the script doesn't find the RTEMS 4.12 bsets. It isn't seeing anything in the rtems/ directory.
$ ./source-builder/sb-set-builder --list-bsets
RTEMS Source Builder - Set Builder, 4.12 (2074bd1168ee)
Examining: config
Examining: source-builder/config
Examining: bare/config
devel/autotools-base.bset
devel/autotools-internal.bset
devel/autotools.bset
devel/dtc.bset
devel/libtool.bset
devel/libusb.bset
devel/or1ksim.bset
devel/qemu.bset
gnu-tools-4.6.bset
gnu-tools-4.8.2.bset
lang/gcc491.bset
The rtems 4.12 bset's are:
$ ls rtems/config/4.12
rtems-aarch64.bset rtems-i386.bset rtems-powerpc.bset
rtems-all.bset rtems-lm32.bset rtems-sh.bset
rtems-arm.bset rtems-m32c.bset rtems-sparc64.bset
rtems-autotools-base.bset rtems-m68k.bset rtems-sparc.bset
rtems-autotools.bset rtems-microblaze.bset rtems-tools.bset
rtems-autotools-internal.bset rtems-mips.bset rtems-v850.bset
rtems-bfin.bset rtems-moxie.bset rtems-x86_64.bset
rtems-default.bset rtems-nios2.bset
rtems-epiphany.bset rtems-or1k.bset
cd into rtems/ and then run set-builder using any of those. This is just a problem with the --list-bsets.
comment:5 Changed on 04/29/17 at 17:24:34 by Joel Sherrill
Good news. Please close if it is resolved n
comment:6 Changed on 05/11/17 at 07:31:02 by Sebastian Huber
Milestone: | 4.12 → 4.12.0 |
---|
comment:7 Changed on 10/10/17 at 06:57:05 by Sebastian Huber
Component: | bsps → tool/rsb |
---|
comment:8 Changed on 10/12/17 at 01:07:54 by Joel Sherrill
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:9 Changed on 11/09/17 at 06:27:14 by Sebastian Huber
Milestone: | 4.12.0 → 5.1 |
---|
Milestone renamed
When you mentioned GitHub?, I wondered if the mirroring was broken. It is not. And it looks like rtems/config/4.12 has the right content.
I will try the script in the morning to see what it lists on my computer.