RSB tool binary locations

[Chris Johns]

On 19/01/2016 04:07, Brandon Matthews wrote:
> Hello again!
>
> After completing an RSB build cycle, I'm a bit confused about where to expect the tool binaries. I'm following the instructions at https://ftp.rtems.org/pub/rtems/releases/4.11/4.11.0-rc1/README.txt.
>

The tools should be installed into the prefix supplied on the RSB 
command line.

> I'm invoking sb-set-builder with
>
> builder at rtems-build:/mnt/rtems/rtems-source-builder-4.11.0-rc1/rtems$ ../source-builder/sb-set-builder --prefix=/opt/rtems-4.11.0-rc1/ 4.11/rtems-arm
>

This looks fine.

> Interestingly, the tool binaries never end up in /opt/rtems-4.11.0-rc1:

This happens if any part of the build fails. The RSB installs into an 
internal path first and once all parts of the build have completed 
without error the contents of the internal prefix is copied to your prefix.

It is much easier to do this than figure out and track what was 
installed and then remove it if the build fails. A partially installed 
yet failed build is also not a good idea.

>
> builder at rtems-build:/mnt/rtems/rtems-source-builder-4.11.0-rc1/rtems$ sudo find / -name 'arm-rtems4.11-gcc'
> /mnt/rtems/rtems-source-builder-4.11.0-rc1/rtems/build/tmp/arm-rtems4.11-gcc-4.9.3-newlib-2.2.0.20150423-x86_64-linux-gnu-1-root-builder/opt/rtems-4.11.0-rc1/bin/arm-rtems4.11-gcc

This path seems fine.

>
> In the RSB log, I see output from `make install`, but don't see any step to copy the output from `.../tmp/$PACKAGE/$PREFIX` to `$PREFIX`. Is this a bug or am I missing a step? (the $PREFIX dir is owned by builder, so no permissions issues).
>

Did the build fail?
Did you end up with an RSB report file?

Chris