Issues with configuring BSP with waf

Fri Mar 12 22:47:09 UTC 2021

On Fri, Mar 12, 2021 at 2:54 PM Ida Delphine <idadelm at gmail.com> wrote:
>
> Hello,
> I did follow the instructions in https://docs.rtems.org/branches/master/user/start/app.html, added init.c, modified hello.c and added wscript. I ran the command:
> ./waf configure --rtems=$HOME/quick-start/rtems/6 --rtems-bsp=sparc/erc32
> But still ended with same error like before. I don't know what I am missing. I don't think I have skipped any step.
> Still got this error:
> Setting top to                           : /home/idadel/quick-start/app/hello
> Setting out to                           : /home/idadel/quick-start/app/hello/build
> RTEMS path is not valid, "/home/idadel/quick-start/rtems/6/share/rtems5" not found.

Try passing --rtems-version=6
Something in rtems_waf seems to be appending a 5 for some reason.

Also, make sure, /home/idadel/quick-start/rtems/6 is where you have
successfully installed the build of RTEMS. That seems right based on
the quick start directions though.

As for GSoC, what we're looking for is
 https://docs.rtems.org/branches/master/user/start/gsoc.html#prove-you-can-work-on-rtems

> (complete log in /home/idadel/quick-start/app/hello/build/config.log)
>
>
> On Fri, Mar 12, 2021 at 5:43 PM Gedare Bloom <gedare at rtems.org> wrote:
>>
>> On Thu, Mar 11, 2021 at 10:55 PM Ida Delphine <idadelm at gmail.com> wrote:
>> >
>> > Hello,
>> > Please I need some help. Following the GSoC getting started guide(https://docs.rtems.org/branches/master/user/start/gsoc.html),everything went well to the point I had to do an offline download. I used this command
>> > ../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
>> > Seems like there was a mismatch. I got this error:
>> > b-set-builder --source-only-download 5/rtems-sparc
>> > RTEMS Source Builder - Set Builder, 6 (5e449fb5c2cb)
>> > Build Set: 5/rtems-sparc
>> > error: no build set file found: 5/rtems-sparc.bset
>> > Build Set: Time 0:00:00.000205
>> > Build FAILED
>> > I then replaced 5/rtems in the command with 6/rtems and everything worked. I was able to install the suite, build the board support package, and test my BSP though along the way I had to replace "5" with "6" in certain commands. Everything went well until I wanted to prove I can work on RTEMS. I followed the instructions to create my hello application and added the necessary .c files. The problem was when I tried configuring this application using waf with the command:
>> >
>> This is really great and you are very close. We definitely do want you
>> to be using '6' and not '5' for GSoC.
>>
>> > ./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
>> >
>> Although you can create a standalone hello application, and that would
>> be an excellent way to show some progress, for the GSoC "proof" we
>> actually want you to modify the hello that gets built as part of
>> rtems. Its source is located in rtems.git/testsuites/samples/hello
>>
>> Then you will rebuild rtems and it should recompile your modified hello sample.
>>
>> > I got this error:
>> > Setting top to                           : /home/idadel/quick-start/app/hello
>> > Setting out to                           : /home/idadel/quick-start/app/hello/build
>> > RTEMS path is not valid, "/home/idadel/quick-start/rtems/5/share/rtems5" not found.
>> > (complete log in /home/idadel/quick-start/app/hello/build/config.log)
>> > I thought I showld startover but and work with rtems.git/5 instead of rtems.git/master. Same with rsb. So I got the sources and did a "git checkout"  from the master to the "5" branch. Everything went well with me not not having to change any "5" to "6" in some commands. I didn't make it as far as testing my BSP. I had issues with configuring my BSP with the command:
>> >
>> > ./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
>> >
>> > I got this:
>> > bash: ./waf: No such file or directory
>> > I'm confused and don't know what I missed or where I went wrong.
>> >
>> > Ida.
>> >
>> >
>> >
>> >
>> > On Thu, Mar 11, 2021 at 6:03 PM Ida Delphine <idadelm at gmail.com> wrote:
>> >>
>> >> Okay. Thank you :)
>> >>
>> >> On Thu, 11 Mar 2021, 5:57 pm Gedare Bloom, <gedare at rtems.org> wrote:
>> >>>
>> >>> On Thu, Mar 11, 2021 at 9:48 AM Ida Delphine <idadelm at gmail.com> 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?
>> >>> >
>> >>> Yes, that issue has been resolved so please try again. Hopefully,
>> >>> things work a bit better. We try not to break things, but unexpected
>> >>> problems come up from time to time, especially based on host OS
>> >>> dependencies.
>> >>>
>> >>> > Cheers,
>> >>> > Ida.
>> >>> >
>> >>> > On Thu, Mar 11, 2021 at 4:18 PM Gedare Bloom <gedare at rtems.org> wrote:
>> >>> >>
>> >>> >> On Thu, Mar 11, 2021 at 7:33 AM Ida Delphine <idadelm at gmail.com> 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 https://waf.io/waf-2.0.19 > waf
>> >>> >>
>> >>> >> https://git.rtems.org/rtems/tree/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 rtems.org
>> >>> >> > http://lists.rtems.org/mailman/listinfo/users