Regarding running one test

Tanu Hari Dixit tokencolour at gmail.com
Sat Feb 4 18:25:23 UTC 2017


Hello Joel,

Thanks for the answer. I want to compile and build the exe file for just
one test. When I use the option --enable-tests with configure, does it
assume to build for all tests in the testsuites? I want to build for a
single test only. I haven't tried rtems-tester as of now because I updated
the rtems repository from upstream and have run into trouble. Can you
please help me with this?

Thanks,
Tanu Hari Dixit.

On Sat, Feb 4, 2017 at 10:24 PM, Joel Sherrill <joel at rtems.org> wrote:

> If you are building the erc32 BSP, there are a handful of options. It is
> probably the easiest BSP to run tests on a simulator.
>
> sparc-rtems4.12-run xxx.exe
>
> sparc-rtems4.12-gdb xxx.exe
> ... target sim
> ... load
> ... run
>
> The rtems-tester supports this BSP to ease running tests for this BSP.
>
> Also the older rtems-testing repo has a sim-scripts directory with scripts
> to ease using a number of simulators. It has gdb and direct run modes.
>
> --joel
>
>
> On Feb 4, 2017 10:23 AM, "Tanu Hari Dixit" <tokencolour at gmail.com> wrote:
>
>> The following is the output of the configure statement (I ran configure
>> again because I did not save the output of the previous one)
>>
>> thd at thd-Inspiron-5537:~/development/rtems/src/builds/erc32_test1$
>> ../../rtems/configure --target=sparc-rtems4.12 --enable-rtemsbsp=erc32
>> --enable-tests --prefix=${HOME}/development/rtems/install_path_test1
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking target system type... sparc-unknown-rtems4.12
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> configure: configuring in ./tools/build
>> configure: running /bin/sh '../../../../rtems/tools/build/configure'
>> '--prefix=/home/thd/development/rtems/install_path_test1'
>> '--host=x86_64-pc-linux-gnu' '--build=x86_64-pc-linux-gnu'
>> '--enable-rtemsbsp=erc32' '--enable-tests' '--target=sparc-rtems4.12'
>> '--cache-file=/dev/null' '--srcdir=../../../../rtems/tools/build'
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking for x86_64-pc-linux-gnu-gcc... no
>> checking for gcc... gcc
>> checking whether the C compiler works... yes
>> checking for C compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... no
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether gcc accepts -g... yes
>> checking for gcc option to accept ISO C89... none needed
>> checking for style of include used by make... GNU
>> checking dependency style of gcc... gcc3
>> checking how to run the C preprocessor... gcc -E
>> checking for grep that handles long lines and -e... /bin/grep
>> checking for egrep... /bin/grep -E
>> checking for ANSI C header files... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking getopt.h usability... yes
>> checking getopt.h presence... yes
>> checking for getopt.h... yes
>> checking libgen.h usability... yes
>> checking libgen.h presence... yes
>> checking for libgen.h... yes
>> checking for strerror... yes
>> checking for strtol... yes
>> checking for basename... yes
>> checking for strnlen... yes
>> checking for bash... /bin/bash
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: creating install-if-change
>> config.status: creating config.h
>> config.status: executing depfiles commands
>> configure: configuring in ./tools/cpu
>> configure: running /bin/sh '../../../../rtems/tools/cpu/configure'
>> '--prefix=/home/thd/development/rtems/install_path_test1'
>> '--host=x86_64-pc-linux-gnu' '--build=x86_64-pc-linux-gnu'
>> '--enable-rtemsbsp=erc32' '--enable-tests' '--target=sparc-rtems4.12'
>> '--cache-file=/dev/null' '--srcdir=../../../../rtems/tools/cpu'
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking target system type... sparc-unknown-rtems4.12
>> checking rtems target cpu... sparc
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking for bash... /bin/bash
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>> === configuring in generic (/home/thd/development/rtems/s
>> rc/builds/erc32_test1/tools/cpu/generic)
>> configure: running /bin/sh ../../../../../rtems/tools/cpu/generic/configure
>> --disable-option-checking '--prefix=/home/thd/development/rtems/install_path_test1'
>> '--host=x86_64-pc-linux-gnu' '--build=x86_64-pc-linux-gnu'
>> '--enable-rtemsbsp=erc32' '--enable-tests' '--target=sparc-rtems4.12'
>> 'build_alias=x86_64-pc-linux-gnu' 'host_alias=x86_64-pc-linux-gnu'
>> 'target_alias=sparc-rtems4.12' --cache-file=/dev/null
>> --srcdir=../../../../../rtems/tools/cpu/generic
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking target system type... sparc-unknown-rtems4.12
>> checking rtems target cpu... sparc
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking for bash... /bin/bash
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: creating size_rtems
>> configure: configuring in ./testsuites/tools
>> configure: running /bin/sh '../../../../rtems/testsuites/tools/configure'
>> '--prefix=/home/thd/development/rtems/install_path_test1'
>> '--host=x86_64-pc-linux-gnu' '--build=x86_64-pc-linux-gnu'
>> '--enable-rtemsbsp=erc32' '--enable-tests' '--target=sparc-rtems4.12'
>> '--cache-file=/dev/null' '--srcdir=../../../../rtems/testsuites/tools'
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking target system type... sparc-unknown-rtems4.12
>> checking rtems target cpu... sparc
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>> === configuring in generic (/home/thd/development/rtems/s
>> rc/builds/erc32_test1/testsuites/tools/generic)
>> configure: running /bin/sh ../../../../../rtems/testsuites/tools/generic/configure
>> --disable-option-checking '--prefix=/home/thd/development/rtems/install_path_test1'
>> '--host=x86_64-pc-linux-gnu' '--build=x86_64-pc-linux-gnu'
>> '--enable-rtemsbsp=erc32' '--enable-tests' '--target=sparc-rtems4.12'
>> 'build_alias=x86_64-pc-linux-gnu' 'host_alias=x86_64-pc-linux-gnu'
>> 'target_alias=sparc-rtems4.12' --cache-file=/dev/null
>> --srcdir=../../../../../rtems/testsuites/tools/generic
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking target system type... sparc-unknown-rtems4.12
>> checking rtems target cpu... sparc
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking for bash... /bin/bash
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: creating difftest
>> config.status: creating sorttimes
>> configure: configuring in sparc-rtems4.12/c
>> configure: running /bin/sh '../../../../rtems/c/configure'
>> '--prefix=/home/thd/development/rtems/install_path_test1'
>> '--host=sparc-rtems4.12' '--build=x86_64-pc-linux-gnu'
>> '--target=sparc-rtems4.12'  '--enable-rtemsbsp=erc32' '--enable-tests'
>> '--with-target-subdir=sparc-rtems4.12' '--exec-prefix=/home/thd/devel
>> opment/rtems/install_path_test1/sparc-rtems4.12'
>> '--includedir=/home/thd/development/rtems/install_path_
>> test1/sparc-rtems4.12/include'  '--cache-file=/dev/null'
>> '--srcdir=../../../../rtems/c'
>> checking for gmake... no
>> checking for make... make
>> checking for RTEMS Version... 4.11.99.0
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... sparc-unknown-rtems4.12
>> checking target system type... sparc-unknown-rtems4.12
>> checking rtems target cpu... sparc
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for sparc-rtems4.12-strip... sparc-rtems4.12-strip
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether to enable maintainer-specific portions of Makefiles... no
>> checking that generated files are newer than configure... done
>> configure: creating ./config.status
>> config.status: creating Makefile
>>
>> target architecture: sparc.
>> available BSPs: erc32.
>> 'make all' will build the following BSPs: erc32.
>> other BSPs can be built with 'make RTEMS_BSP="bsp1 bsp2 ..."'
>>
>> config.status: creating Makefile
>>
>>
>> Thank you,
>> Tanu Hari Dixit.
>>
>> On Sat, Feb 4, 2017 at 9:26 PM, Kirspel, Kevin <Kevin-Kirspel at idexx.com>
>> wrote:
>>
>>> I don’t have the spac toolset so I cannot test your situation.  However,
>>> can you post the output of your configure?  I want to make sure it found
>>> the erc32 BSP.
>>>
>>>
>>>
>>> Kevin Kirspel
>>>
>>> Electrical Engineer - Sr. Staff
>>>
>>> Idexx Roswell
>>>
>>> 235 Hembree Park Drive
>>>
>>> Roswell GA 30076
>>>
>>> Tel: (770)-510-4444 ext. 81642 <(770)%20510-4444>
>>>
>>> Direct: (770)-688-1642 <(770)%20688-1642>
>>>
>>> Fax: (770)-510-4445 <(770)%20510-4445>
>>>
>>>
>>>
>>> *From:* Tanu Hari Dixit [mailto:tokencolour at gmail.com]
>>> *Sent:* Saturday, February 04, 2017 10:27 AM
>>> *To:* Kuan Hsun Chen <kuan-hsun.chen at tu-dortmund.de>
>>> *Cc:* rtems-devel at rtems.org <devel at rtems.org>; Kirspel, Kevin <
>>> Kevin-Kirspel at idexx.com>
>>> *Subject:* Re: Regarding running one test
>>>
>>>
>>>
>>> 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 at 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/s
>>> rc/builds/erc32_test/tools/build'
>>> make[1]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/build'
>>> Making all in tools/cpu
>>> make[1]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/cpu'
>>> Making all in generic
>>> make[2]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/cpu/generic'
>>> make[2]: Nothing to be done for `all'.
>>> make[2]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/cpu/generic'
>>> make[2]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/cpu'
>>> make[2]: Nothing to be done for `all-am'.
>>> make[2]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/cpu'
>>> make[1]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/tools/cpu'
>>> Making all in testsuites/tools
>>> make[1]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/testsuites/tools'
>>> Making all in generic
>>> make[2]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/testsuites/tools/generic'
>>> make[2]: Nothing to be done for `all'.
>>> make[2]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/testsuites/tools/generic'
>>> make[2]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/testsuites/tools'
>>> make[2]: Nothing to be done for `all-am'.
>>> make[2]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/testsuites/tools'
>>> make[1]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/testsuites/tools'
>>> Making all in sparc-rtems4.12/c
>>> make[1]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/sparc-rtems4.12/c'
>>> Making all in .
>>> make[2]: Entering directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/sparc-rtems4.12/c'
>>> make[2]: Nothing to be done for `all-am'.
>>> make[2]: Leaving directory `/home/thd/development/rtems/s
>>> rc/builds/erc32_test/sparc-rtems4.12/c'
>>> Making all in erc32
>>> make[2]: Entering directory `/home/thd/development/rtems/s
>>> rc/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/s
>>> rc/builds/erc32_test/sparc-rtems4.12/c/erc32'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory `/home/thd/development/rtems/s
>>> rc/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
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__git.rtems.org_rtems.git&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=HDiJ93ANMEQ32G5JGdpyUxbdebuwKHBbeiHMr3RbR74&m=elBFGM7Up_H75tt-b3VbfyK1iPdyr-jmME-Ab4rL2hk&s=ryMs7_iFDreSyA8ad3iXqtVo0QByXEG61ZeaU1r6J4A&e=>
>>>
>>> git status shows
>>>
>>> thd at 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.chen at 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/:
>>>
>>> 1.  qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -kernel
>>> \
>>>
>>> 2.  hello.exe -smp 4
>>>
>>>
>>>
>>> Best,
>>>
>>> Kuan-Hsun
>>>
>>>
>>>
>>> 2017-02-04 14:12 GMT+01:00 Kirspel, Kevin <Kevin-Kirspel at idexx.com>:
>>>
>>> I use the rtems tester.  ftp://ftp.rtems.org/pub/rtems/
>>> people/chrisj/rtems-tester/rtems-tester.html
>>> <https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.rtems.org_pub_rtems_people_chrisj_rtems-2Dtester_rtems-2Dtester.html&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=HDiJ93ANMEQ32G5JGdpyUxbdebuwKHBbeiHMr3RbR74&m=elBFGM7Up_H75tt-b3VbfyK1iPdyr-jmME-Ab4rL2hk&s=Gv6QEbMGt88773MgovVmHykfnOxbLOP5J32IzwNVNEc&e=>
>>>
>>> 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-bounces at rtems.org] On Behalf Of Tanu Hari
>>> Dixit
>>> Sent: Saturday, February 04, 2017 12:23 AM
>>> To: rtems-devel at rtems.org <devel at 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 at rtems.org
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.rt
>>> ems.org_mailman_listinfo_devel&d=DwICAg&c=2do6VJGs3LvEOe4OFF
>>> M1bA&r=HDiJ93ANMEQ32G5JGdpyUxbdebuwKHBbeiHMr3RbR74&m=zH4W9XS
>>> 8-wD5iyDXdo5SEtjZwr3gbIp9TJjx8-z2cS8&s=mU8IyO6GG8v94eNhQoI76
>>> FuuhiadOCFEoiJ3HdxyrrQ&e=
>>>
>>> _______________________________________________
>>> devel mailing list
>>> devel at rtems.org
>>>
>>> http://lists.rtems.org/mailman/listinfo/devel
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.rtems.org_mailman_listinfo_devel&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=HDiJ93ANMEQ32G5JGdpyUxbdebuwKHBbeiHMr3RbR74&m=elBFGM7Up_H75tt-b3VbfyK1iPdyr-jmME-Ab4rL2hk&s=2TitOf1dwrWdEOQH2NpO_av9kjH_jPk9KJdkJUNk2Js&e=>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> 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 <+49%20231%207556124>*
>>> Mail:   kuan-hsun.chen at tu-dortmund.de
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170204/f7cd8838/attachment-0002.html>


More information about the devel mailing list