RFC - Move all Native Tools from rtems to rtems-tools
Hi While setting up the Coverity build, I noticed that we have very few native tools in the rtems source tree. There are only these directories: ./c/src/lib/libbsp/i386/pc386/tools ./c/src/lib/libbsp/m68k/mcf5206elite/tools ./testsuites/tools ./tools pc386 has 1 C file. mcf5206elite has 1 shell script testsuites/tools has 2 shell scripts tools has 47 files I suspect some in tools/ can be obsoleted. Overall, I am curious if moving most of these to rtems-tools would simplify the build system and be more proper. There appear to be a few programs which are used in the build process so some evaluation would be needed. Thoughts? --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Regarding running one test
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 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 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 ..." to update what will be committed)
> (use "git checkout -- ..." 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
> 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
Re: Regarding running one test
On Feb 4, 2017 12:25 PM, "Tanu Hari Dixit" wrote:
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?
You either configure for no tests, samples or all tests.
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.
I am answering from my phone so can't give you an example of that. But
honestly, I just build from the top and use a fast machine.
Sorry.
Thanks,
Tanu Hari Dixit.
On Sat, Feb 4, 2017 at 10:24 PM, Joel Sherrill 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" 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@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
>>
Re: Regarding running one test
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 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" 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@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
Re: Regarding running one test
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" 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@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
> check
Re: Regarding running one test
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@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/src/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'
'targe
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@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 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 ..." to update what will be committed)
(use "git checkout -- ..." 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/:
>
>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 :
>
>> 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- ext. 81642
>> Direct: (770)-688-1642
>> Fax: (770)-510-4445
>>
>> -Original Mess
Re: Regarding running one test
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 : > 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- 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 > 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
RE: Regarding running one test
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- 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 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=mU8IyO6GG8v94eNhQoI76FuuhiadOCFEoiJ3HdxyrrQ&e= ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
