If you build regular qemu with the RSB, does the same thing happen? Try
../source-builder/sb-set-builder --log=qemu_log.txt --prefix=$HOME/development/5 devel/qemu On 16 March 2018 at 16:48, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> wrote: > still the same error > > -- vijay > > On 16 March 2018 at 21:39, Cillian O'Donnell <cpodonne...@gmail.com> > wrote: > >> Just checked and the build was failing because one of the patches needed >> its hash to be updated to sha256. Just pushed that change. The build >> finishes successfully on my end. Pull that change into couverture-build >> branch and try it again. I'm not seeing any automake stuff here, so just >> check that and let me know. >> >> On 16 March 2018 at 14:59, Vijay Kumar Banerjee <vijaykumar9...@gmail.com >> > wrote: >> >>> building couverture-qemu from rtems-source-builder ( >>> https://github.com/cillianodonnell/rtems-source-builder/tr >>> ee/couverture-build ) >>> gives error building auromake-1.12.6-x86_64-linux-gnu-1 . >>> >>> I have attached the error report . >>> >>> -- vijay >>> >>> On 15 March 2018 at 19:17, Cillian O'Donnell <cpodonne...@gmail.com> >>> wrote: >>> >>>> >>>> >>>> On 15 March 2018 at 12:26, Vijay Kumar Banerjee < >>>> vijaykumar9...@gmail.com> wrote: >>>> >>>>> It runs with a bunch of errors . I have attached the log file >>>>> >>>> >>>> Ok, I'm guessing you didn't set up Couverture-Qemu (special version of >>>> qemu designed for generating extra trace data for coverage analysis). >>>> That's what those errors are about. I have an RSB build for that. >>>> >>>> https://github.com/cillianodonnell/rtems-source-builder/tree >>>> /couverture-build >>>> >>>> and the instructions for building it are >>>> >>>> https://devel.rtems.org/wiki/GSoC/2017/coveragetools#Buildin >>>> gCouverture-QemuwiththeRSB >>>> >>>> I know what the other problem is too. I have a specific environment >>>> variable defined for the path, sorry I can't even remember putting it >>>> there, I thought that was automatically generated (probably should be, >>>> another thing to add to the list :)... ). So wherever you stuck the export >>>> path for where the rsb built the tools, in .bashrc or whatever you're >>>> using. Also put something like: >>>> >>>> export PATH=$HOME/development/rtems/5/bin:$PATH >>>> >>>> export >>>> PATH=$HOME/development/rtems/test/rtems-tools/build/tester/covoar:$PATH >>>> >>>> >>>> or you could just copy covoar into the /bin directory with all the >>>> other rsb tools gcc and all that, it'll find it either way. >>>> >>>> >>>> >>>>> >>>>> -- vijay >>>>> >>>>> On 15 March 2018 at 16:58, Cillian O'Donnell <cpodonne...@gmail.com> >>>>> wrote: >>>>> >>>>>> Looks good. If you run the samples without coverage is everything ok? >>>>>> >>>>>> So removing --coverage and tacking on /samples >>>>>> >>>>>> $HOME/development/rtems-tools/tester/rtems-test >>>>>> --rtems-bsp=leon3-qemu --log=log-leon3.log >>>>>> --rtems-tools=$HOME/development/rtems/5 >>>>>> --rtems-builddir=$HOME/development/rtems/kernel/leon3 >>>>>> sparc-rtems5/c/leon3/testsuites/samples >>>>>> >>>>>> Do the tests run? >>>>>> >>>>>> On 15 March 2018 at 10:53, Vijay Kumar Banerjee < >>>>>> vijaykumar9...@gmail.com> wrote: >>>>>> >>>>>>> I have attached the output of the ls of that directory >>>>>>> >>>>>>> -- vijay >>>>>>> >>>>>>> On 15 March 2018 at 15:52, Cillian O'Donnell <cpodonne...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 15 March 2018 at 03:58, Vijay Kumar Banerjee < >>>>>>>> vijaykumar9...@gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> hello , >>>>>>>>> >>>>>>>>> as told by Joel , I started this thread to further discuss the >>>>>>>>> coverage analysis toolset . >>>>>>>>> >>>>>>>>> Current status is , I'm trying to builld and run rtems-test from >>>>>>>>> the coverage-merge branch of the previous GSoC student Cillian . >>>>>>>>> https://github.com/cillianodonnell/rtems-tools/tree/coverage-merge >>>>>>>>> >>>>>>>>> I'm getting an error that says . >>>>>>>>> "Covoar not found !" >>>>>>>>> >>>>>>>> >>>>>>>> It's supposed to find it in rtems-tools/build/tester/covoar/ If >>>>>>>> it's in there it should be fine. Can you show me the contents of that >>>>>>>> directory? >>>>>>>> >>>>>>>> cpod@cpod ~/development/rtems/test/rtems-tools/build/tester/covoar >>>>>>>> $ ls >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> the Covoar appeared in rtems-tools/tester/covoar . >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> Vijay >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> devel mailing list >>>>>>>>> devel@rtems.org >>>>>>>>> http://lists.rtems.org/mailman/listinfo/devel >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
