error: no build set file found: arm/realview_pbx_a9_qemu.bset

Joel Sherrill joel at rtems.org
Tue Feb 7 00:15:23 UTC 2017


On Mon, Feb 6, 2017 at 5:37 PM, Gedare Bloom <gedare at rtems.org> wrote:

> Try
> ../source-builder/sb-set-builder --list-bsets
> to get a list of the valid bsets you may use.
>

The arm board is simulated as part of the qemu build
with qemu.bset Since that is not RTEMS specific it is
under the bare directory at the top if I recall correctly.

--joel


>
> On Sun, Feb 5, 2017 at 9:08 PM, Karim, Hassan
> <hassan.karim at bison.howard.edu> wrote:
> > I've been running in circles dor days trying to compile RTEMS for the
> > arm/realview_pbx_a9_qemu BSP.
> > what am I doing wrong?
> > When I run the setbuilder it says I don't have a bset for realview. I
> say to
> > myself, I know. I was this set builder would create it. But alas... it
> > doesn't. Am I missing a step?
> > I already built a qemu.bset and I've even gotten to the point where I
> built
> > the erc32 BSP and ran the ticker for sparc/erc32. So I thought I was
> ready
> > to compile.
> >
> > ../source-builder/sb-set-builder --without-rtems
> --log=arm_realvoewbx.log
> > --prefix=$HOME/rtems/4.12 arm/realview_pbx_a9_qemu
> > RTEMS Source Builder - Set Builder, 4.12 (08f709966f97 modified)
> > Build Set: arm/realview_pbx_a9_qemu
> > error: no build set file found: arm/realview_pbx_a9_qemu.bset
> > Build Set: Time 0:00:00.002498
> > Build FAILED
> >
> >
> >
> > Regards,
> >
> > Hassan Karim, CISSP
> > https://www.linkedin.com/in/hassankarimcissp
> > Comp Sci Ph.D. Student
> > Howard University
> > (202) 569-1012
> >
> > _______________________________________________
> > users mailing list
> > users at rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20170206/358b2958/attachment-0002.html>


More information about the users mailing list