Hello Joel, > > You either configure for no tests, samples or all tests. > I finally understand this. Thanks.
> If you are trying to speed up a build for debug purposes, you can be > careful and build just cpukit again and then switch.to the test > directory. > By this do you mean, that if I make some changes in the cpukit, I rebuild it---(i.e run the configure script in rtems/cpukit and consequently make) and it will be all that I am required to do? Won't I need to make the executables again? Regards, Tanu Hari Dixit. On Mon, Feb 6, 2017 at 7:08 PM, Tanu Hari Dixit <tokencol...@gmail.com> wrote: > Hello Gedare, Joel, > > I was able to re-build and execute the samples following your advice. > Thank you. > > Regards, > Tanu Hari Dixit. > > > On Sun, Feb 5, 2017 at 3:03 AM, Gedare Bloom <ged...@rtems.org> wrote: > > After you do a git-pull you should usually re-run bootstrap, delete > > your build, and re-run configure and make. This is especially true if > > you re-build a toolchain, at least to get started. > > > > On Sat, Feb 4, 2017 at 10:26 AM, Tanu Hari Dixit <tokencol...@gmail.com> > wrote: > >> Hi Kevin, Kuan-Hsun, > >> > >> Thank you for the answer. > >> I have run into a problem before trying the above solutions for myself, > >> while updating my local copy of the rtems repository with upstream with > "git > >> pull". > >> After I updated the local copy, I built the sparc toolset with > >> ../source-builder/sb-set-builder --log=l-sparc-test.txt > >> --prefix=$HOME/development/rtems/4.12 4.12/rtems-sparc > >> Then I ran ./bootstrap -c && ./bootstrap -p && ./bootstrap so as to > >> bootstrap. > >> Then from builds/erc32_test(subdirectory) I ran > >> thd@thd-Inspiron-5537:~/development/rtems/src/rtems$ > ../../rtems/configure > >> --target=sparc-rtems4.12 --enable-rtemsbsp=erc32 --enable-tests > >> --prefix=${HOME}/development/rtems/install_path_test > >> > >> And when I ran make, It showed the following error; > >> > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/build' > >> make[1]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/build' > >> Making all in tools/cpu > >> make[1]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/cpu' > >> Making all in generic > >> make[2]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/cpu/generic' > >> make[2]: Nothing to be done for `all'. > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/cpu/generic' > >> make[2]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/cpu' > >> make[2]: Nothing to be done for `all-am'. > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/cpu' > >> make[1]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/tools/cpu' > >> Making all in testsuites/tools > >> make[1]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/testsuites/tools' > >> Making all in generic > >> make[2]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/ > testsuites/tools/generic' > >> make[2]: Nothing to be done for `all'. > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/ > testsuites/tools/generic' > >> make[2]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/testsuites/tools' > >> make[2]: Nothing to be done for `all-am'. > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/testsuites/tools' > >> make[1]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/testsuites/tools' > >> Making all in sparc-rtems4.12/c > >> make[1]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/sparc-rtems4.12/c' > >> Making all in . > >> make[2]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/sparc-rtems4.12/c' > >> make[2]: Nothing to be done for `all-am'. > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/sparc-rtems4.12/c' > >> Making all in erc32 > >> make[2]: Entering directory > >> `/home/thd/development/rtems/src/builds/erc32_test/sparc- > rtems4.12/c/erc32' > >> make[2]: *** No rule to make target `all'. Stop. > >> make[2]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/sparc- > rtems4.12/c/erc32' > >> make[1]: *** [all-recursive] Error 1 > >> make[1]: Leaving directory > >> `/home/thd/development/rtems/src/builds/erc32_test/sparc-rtems4.12/c' > >> make: *** [all-recursive] Error 1 > >> > >> I have ran into this problem more than once. When last time this > happened, I > >> thought I must have messed up somewhere in the git (or rtems) workflow > and > >> hence decided to make a clean clone of the rtems repo and continue with > it. > >> I also tried git reset --hard <hash-number> last time and had no luck. > >> Right now, I did not do a hard reset and currently git reflog shows the > >> following output: > >> 239dd35 HEAD@{0}: pull: Fast-forward > >> ffa885a HEAD@{1}: clone: from git://git.rtems.org/rtems.git > >> > >> git status shows > >> > >> thd@thd-Inspiron-5537:~/development/rtems/src/rtems$ git status > >> On branch master > >> Your branch is up-to-date with 'origin/master'. > >> > >> Changes not staged for commit: > >> (use "git add <file>..." to update what will be committed) > >> (use "git checkout -- <file>..." to discard changes in working > directory) > >> > >> modified: c/src/lib/libbsp/powerpc/acinclude.m4 > >> > >> no changes added to commit (use "git add" and/or "git commit -a") > >> > >> > >> I don't know what I am missing. Do I need to do something before pulling > >> from upstream? How do I rectify this? Please help me with this. > >> > >> Thank you, > >> Tanu Hari Dixit. > >> > >> > >> On Sat, Feb 4, 2017 at 6:47 PM, Kuan Hsun Chen > >> <kuan-hsun.c...@tu-dortmund.de> wrote: > >>> > >>> Or alternatively you can prepare simulator like qemu to executed each > of > >>> it after compiling the source tree. > >>> Like this in testsuites/hello/: > >>> > >>> qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M > -kernel \ > >>> hello.exe -smp 4 > >>> > >>> > >>> Best, > >>> Kuan-Hsun > >>> > >>> 2017-02-04 14:12 GMT+01:00 Kirspel, Kevin <kevin-kirs...@idexx.com>: > >>>> > >>>> I use the rtems tester. > >>>> ftp://ftp.rtems.org/pub/rtems/people/chrisj/rtems-tester/ > rtems-tester.html > >>>> > >>>> Kevin Kirspel > >>>> Electrical Engineer - Sr. Staff > >>>> Idexx Roswell > >>>> 235 Hembree Park Drive > >>>> Roswell GA 30076 > >>>> Tel: (770)-510-4444 ext. 81642 > >>>> Direct: (770)-688-1642 > >>>> Fax: (770)-510-4445 > >>>> > >>>> -----Original Message----- > >>>> From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Tanu Hari > Dixit > >>>> Sent: Saturday, February 04, 2017 12:23 AM > >>>> To: rtems-de...@rtems.org <devel@rtems.org> > >>>> Subject: Regarding running one test > >>>> > >>>> Hello all, > >>>> > >>>> How do I run a single test from the testsuites? I want to run one test > >>>> from the rtems/testsuites/fstests. How do I go about doing that? > >>>> > >>>> Regards, > >>>> Tanu Hari Dixit. > >>>> _______________________________________________ > >>>> devel mailing list > >>>> devel@rtems.org > >>>> > >>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists. > rtems.org_mailman_listinfo_devel&d=DwICAg&c=2do6VJGs3LvEOe4OFFM1bA&r= > HDiJ93ANMEQ32G5JGdpyUxbdebuwKHBbeiHMr3RbR74&m=zH4W9XS8- > wD5iyDXdo5SEtjZwr3gbIp9TJjx8-z2cS8&s=mU8IyO6GG8v94eNhQoI76FuuhiadOC > FEoiJ3HdxyrrQ&e= > >>>> _______________________________________________ > >>>> devel mailing list > >>>> devel@rtems.org > >>>> http://lists.rtems.org/mailman/listinfo/devel > >>> > >>> > >>> > >>> > >>> -- > >>> M.Sc. Kuan-Hsun Chen > >>> > >>> TU Dortmund > >>> Department of Computer Science 12 > >>> Design Automation of Embedded Systems > >>> Otto-Hahn-Strasse 16, Room 102 > >>> > >>> 44227 Dortmund > >>> Germany > >>> > >>> Phone: +49 231 755 6124 > >>> Mail: kuan-hsun.c...@tu-dortmund.de > >> > >> > >> > >> _______________________________________________ > >> 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