Problem: RSB does no longer install stand-alone sis

Gedare Bloom gedare at
Thu Aug 8 21:53:23 UTC 2019

I can confirm something is wrong. The install step does copy something
though, I get a tree like this:
sis-2.17-x86_64-linux-gnu-1.txt  sis-2.17-x86_64-linux-gnu-1.xml

I gave --log option to sb-set-builder. I can see the build compiled.

It looks like %clean is running before %copy. That looks suspicious to me.

On Thu, Aug 8, 2019 at 3:43 PM Jiri Gaisler <jiri at> wrote:
> RSB does not longer install the stand-alone version of sis. Even though the RSB log claims is does, the binary is not copied to the install location:
> installing: sis-2.17-x86_64-linux-gnu-1 -> /opt/rtems/5    does nothing ....
> There has been a few commits that changes the RSB install scripts but I am not able to see where it goes wrong. Maybe someone more enlightened than me could look at this.
> Building sis as bare tool has that same problem. The binary is built but not installed:
> rtems-source-builder/bare$ ../source-builder/sb-set-builder --prefix=/opt/rtems/5 devel/sis
> RTEMS Source Builder - Set Builder, 5 (e5460e9ecb99)
> Build Set: devel/sis
> config: devel/sis-2-1.cfg
> package: sis-2.17-x86_64-linux-gnu-1
> building: sis-2.17-x86_64-linux-gnu-1
> sizes: sis-2.17-x86_64-linux-gnu-1: 3.770MB (installed: 633.499KB)
> cleaning: sis-2.17-x86_64-linux-gnu-1
> reporting: devel/sis-2-1.cfg -> sis-2.17-x86_64-linux-gnu-1.txt
> reporting: devel/sis-2-1.cfg -> sis-2.17-x86_64-linux-gnu-1.xml
> installing: sis-2.17-x86_64-linux-gnu-1 -> /opt/rtems/5
> Build Set: Time 0:00:04.271759
>  $
> $ ls -l /opt/rtems/5/bin/*sis*
> ls: cannot access '/opt/rtems/5/bin/*sis*': No such file or directory
> _______________________________________________
> devel mailing list
> devel at

More information about the devel mailing list