Issues with configuring BSP with waf

Vijay Kumar Banerjee vijay at
Thu Mar 11 16:56:56 UTC 2021

Hello Ida,

On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine <idadelm at> wrote:
> Thank you for your response. I am not working on the rtems.git/master branch. I'm not using it because earlier I tried downloading sources with it but I got this error
> error: shell macro failed: /home/idadel/quick-start/src/rsb/source-builder/sb/rtems-build-dep -c gcc  -l : 2: error: no library (-l) provided
> So I decided to use the other alternative(get the sources from releases)
> Since I'm a GSoC applicant should I wait till the issue at the master branch is resolved?
The wait is over. The issue has been resolved upstream and hopefully,
you'll be able to build it without issue.

Best regards,

> Cheers,
> Ida.
> On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom <gedare at> wrote:
>> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine <idadelm at> wrote:
>> >
>> > Hello everyone,
>> > Was following the quick build documentation and had issues around where I have to do a manual BSP build.  In the last step of configuring the BSP, I ran this command:
>> >
>> > ./waf configure --prefix=$HOME/quick-start/rtems/5
>> >
>> Are you working on rtems.git/master branch or /5 branch? Note that you
>> need to be sure to use a consistent compiler toolchain based on the
>> version of RTEMS that you use.
>> In rtems/5 branch we don't have waf support integrated yet. The
>> upgrade to waf is happening currently on the master branch, which will
>> eventually become the RTEMS version 6 release.
>> For GSoC students we expect development to happen on the development
>> head and not a release, so please make sure that you have the
>> toolchain built from rtems-source-builder.git/master and the rtems
>> source tree from rtems.git/master.
>> > It didn't produce the expected output. I instead got:
>> > bash: ./waf: No such file or directory
>> > As a result I downloaded it with the command:
>> > curl > waf
>> Currently, the waf-based build of rtems only supports "in tree"
>> builds, which means you need to run waf from within the rtems.git/
>> root of your source. This is a limitation of the waf build.
>> FWIW, waf build improvements could also fall under GSoC effort,
>> although no one has written it up as a task yet. It would be mostly
>> Python.
>> > I ran  the last command to configure the BSP again but still did not get the expected  output. I got this rather:
>> > Waf: Run from a folder containing a 'wscript' file (or try -h for the generic options)
>> > Please how do I fix this? What am I missing?
>> > I have tried looking for solutions but to no avail.
>> >
>> Sometimes the solutions only exist inside other people's heads, so
>> asking questions is encouraged.
>> > Thanks,
>> > Ida.
>> > _______________________________________________
>> > users mailing list
>> > users at
>> >
> _______________________________________________
> users mailing list
> users at

More information about the users mailing list