[PATCH v2 rtems-tools 2/2] misc: Add rtems-style command

[Ida Delphine]

This is the code for the rtems-style tool which checks for style differences 
and produces a report as well as reformats a given file or directory.

Signed-off-by: Ida Delphine 
---
 misc/rtems-style|  16 +
 misc/tools/style.py | 153 
 2 files changed, 169 insertions(+)
 create mode 100644 misc/rtems-style
 create mode 100644 misc/tools/style.py

diff --git a/misc/rtems-style b/misc/rtems-style
new file mode 100644
index 000..5a3e0e8
--- /dev/null
+++ b/misc/rtems-style
@@ -0,0 +1,16 @@
+#! /usr/bin/env python
+
+from __future__ import print_function
+
+import sys, os
+
+base = os.path.dirname(os.path.dirname(os.path.abspath(sys.argv[0])))
+rtems = os.path.join(base, 'share', 'rtems')
+sys.path = sys.path[0:1] + [rtems, base] + sys.path[1:]
+
+try:
+import misc.tools.style
+misc.tools.style.run()
+except ImportError:
+print("Incorrect RTEMS Tools installation", file = sys.stderr)
+sys.exit(1)
\ No newline at end of file
diff --git a/misc/tools/style.py b/misc/tools/style.py
new file mode 100644
index 000..fbd575e
--- /dev/null
+++ b/misc/tools/style.py
@@ -0,0 +1,153 @@
+import argparse
+import os
+import sys
+import re
+
+from rtemstoolkit import execute
+from rtemstoolkit import git
+
+
+def get_command():
+from rtemstoolkit import check
+
+for version in ['', '8', '9', '10', '11']:
+if check.check_exe(None, 'clang-format' + version):
+command = 'clang-format' + version
+return command
+print("Clang-format not found in your system")
+sys.exit(1)
+
+
+def arguments():
+parser = argparse.ArgumentParser(description="Tool for code formatting and 
style checking \
+for RTEMS")
+parser.add_argument("-c", "--check", dest="check", help="Check for style 
differences and \
+report the number of issues if found", action="store_true")
+parser.add_argument("-r", "--reformat", dest="reformat", help="Reformat 
the file/directory \
+with any style differences found", action="store_true")
+parser.add_argument("-p", "--path", dest="path", help="The path to be 
checked for style issues \
+or reformatted")
+parser.add_argument("-i", "--ignore", dest="ignore", help="Ignore files to 
be checked or \
+reformatted", nargs='*')
+parser.add_argument("-v", "--verbose", dest="verbose", help="A more 
detailed outline of the \
+style issues", action='store_true')
+return [parser.parse_args(), parser.print_usage()]
+
+
+def get_diff(path, ignore_file):
+diff = ""
+ex = execute.capture_execution()
+
+def clang_to_git_diff(clang_output, path):
+import os
+import tempfile
+
+fd, tmp_path = tempfile.mkstemp()
+try:
+with os.fdopen(fd, 'w') as tmp:
+
+tmp.write(clang_output)
+repo = git.repo(".")
+return repo.diff(['--no-index', path, tmp_path])
+
+finally:
+os.remove(tmp_path)
+
+if os.path.isfile(path) == True:
+cmd = get_command() + " --style=file " + path
+output_clang = ex.command(command=cmd, shell=True)
+output_clang = output_clang[2]
+diff = clang_to_git_diff(output_clang, path)
+else:
+onlyfiles = [f for f in os.listdir(path)]
+for file in onlyfiles:
+ig_match = False
+if ignore_file is not None:
+for f in ignore_file:
+if file == f:
+ig_match = True
+if ig_match == True:
+continue
+
+file = os.path.join(path, file)
+
+if file.endswith('.c') or file.endswith('.h'):
+cmd = get_command() + " --style=file " + file
+output_clang = ex.command(command=cmd, shell=True)
+output_clang = output_clang[2]
+diff += clang_to_git_diff(output_clang, os.path.join(path, 
file))
+return diff
+
+
+def color_text(string, col, style=1):
+return "\033[" + str(style) + ";" + str(col) + ";" + str(col) + "m" + 
string + "\033[0;0m"
+
+
+def handle_errors(path, output, verbose=False,):
+if len(output) < 1:
+print("Everything is clean - No style issues")
+else:
+print(color_text("Checking for style differences...", 34, style=3))
+
+out = output.split('\n')
+files = []
+num_diff = 0
+for line in out:
+
+if line.startswith("---"):
+file = str(re.sub('^---\s[ab]', 

[PATCH v2 rtems-tools 0/2] Command for code reformatting and style checking

[Ida Delphine]

The rtems-style command helps to check for style issues or reformat code given 
a file
or directory. There are 5 flags:
* -c, --check : Checks for style issues
* -r, --reformat : Reformats the code
* -p, --path : Path to file or dir to be checked or reformatted
* -i, --ignore : Files to be ignored when checking or reformatting
* -v, --verbose : Produces a more detailed output.

Ida Delphine (2):
  rt: Add diff method to git.py
  misc: Add rtems-style command

 misc/rtems-style|  16 +
 misc/tools/style.py | 153 
 rtemstoolkit/git.py |   5 ++
 3 files changed, 174 insertions(+)
 create mode 100644 misc/rtems-style
 create mode 100644 misc/tools/style.py

-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH v2 rtems-tools 1/2] rt: Add diff method to git.py

[Ida Delphine]

Signed-off-by: Ida Delphine 
---
 rtemstoolkit/git.py | 5 +
 1 file changed, 5 insertions(+)

diff --git a/rtemstoolkit/git.py b/rtemstoolkit/git.py
index f65300b..b544a9b 100644
--- a/rtemstoolkit/git.py
+++ b/rtemstoolkit/git.py
@@ -119,6 +119,10 @@ class repo:
 args = [args]
 ec, output = self._run(['clean'] + args, check = True)
 
+def diff(self, args = []):
+ec, output = self._run(['diff'] + args)
+return output
+
 def status(self):
 _status = {}
 if path.exists(self.path):
@@ -229,3 +233,4 @@ if __name__ == '__main__':
 print('remotes:', g.remotes())
 print('email:', g.email())
 print('head:', g.head())
+print('diff:', g.diff())
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-tools 1/2] rt: Add diff method to git.py

[Ida Delphine]

Signed-off-by: Ida Delphine 
---
 rtemstoolkit/git.py | 5 +
 1 file changed, 5 insertions(+)

diff --git a/rtemstoolkit/git.py b/rtemstoolkit/git.py
index f65300b..b544a9b 100644
--- a/rtemstoolkit/git.py
+++ b/rtemstoolkit/git.py
@@ -119,6 +119,10 @@ class repo:
 args = [args]
 ec, output = self._run(['clean'] + args, check = True)
 
+def diff(self, args = []):
+ec, output = self._run(['diff'] + args)
+return output
+
 def status(self):
 _status = {}
 if path.exists(self.path):
@@ -229,3 +233,4 @@ if __name__ == '__main__':
 print('remotes:', g.remotes())
 print('email:', g.email())
 print('head:', g.head())
+print('diff:', g.diff())
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-tools 2/2] misc: Add rtems-style command

[Ida Delphine]

Signed-off-by: Ida Delphine 

This command helps to check for style issues or reformat code given a file
or directory. There are 4 flags:
* -c, --check : Checks for style issues
* -r, --reformat : Reformats the code
* -p, --path : Path to file or dir to be checked or reformatted
* -i, --ignore : Files to be ignored when checking or reformatting
* -v, --verbose : Produces a more detailed output.
---
 misc/rtems-style|  16 +
 misc/tools/style.py | 144 
 2 files changed, 160 insertions(+)
 create mode 100644 misc/rtems-style
 create mode 100644 misc/tools/style.py

diff --git a/misc/rtems-style b/misc/rtems-style
new file mode 100644
index 000..5a3e0e8
--- /dev/null
+++ b/misc/rtems-style
@@ -0,0 +1,16 @@
+#! /usr/bin/env python
+
+from __future__ import print_function
+
+import sys, os
+
+base = os.path.dirname(os.path.dirname(os.path.abspath(sys.argv[0])))
+rtems = os.path.join(base, 'share', 'rtems')
+sys.path = sys.path[0:1] + [rtems, base] + sys.path[1:]
+
+try:
+import misc.tools.style
+misc.tools.style.run()
+except ImportError:
+print("Incorrect RTEMS Tools installation", file = sys.stderr)
+sys.exit(1)
\ No newline at end of file
diff --git a/misc/tools/style.py b/misc/tools/style.py
new file mode 100644
index 000..a101146
--- /dev/null
+++ b/misc/tools/style.py
@@ -0,0 +1,144 @@
+import argparse
+import os
+import sys
+import re
+
+from rtemstoolkit import execute
+from rtemstoolkit import git
+
+
+def get_command():
+from rtemstoolkit import check
+
+for version in ['', '8', '9', '10', '11']:
+if check.check_exe(None, 'clang-format' + version):
+command = 'clang-format' + version
+return command
+print("Clang-format not found in your system")
+sys.exit(1)
+
+
+def arguments():
+parser = argparse.ArgumentParser(description="Tool for code formatting and 
style checking \
+for RTEMS")
+parser.add_argument("-c", "--check", dest="check", help="Check for style 
differences and \
+report the number of issues if found", action="store_true")
+parser.add_argument("-r", "--reformat", dest="reformat", help="Reformat 
the file/directory \
+with any style differences found", action="store_true")
+parser.add_argument("-p", "--path", dest="path", help="The path to be 
checked for style issues \
+or reformatted")
+parser.add_argument("--ignore", dest="ignore", help="Ignore files to be 
checked or reformatted")
+parser.add_argument("-v", "--verbose", dest="verbose", help="A more 
detailed outline of the \
+style issues", action='store_true')
+return [parser.parse_args(), parser.print_usage()]
+
+
+
+def get_diff(path, ignore_file=None):
+diff = ""
+ex = execute.capture_execution()
+
+
+def clang_to_git_diff(clang_output, path):
+import os
+import tempfile
+
+fd, tmp_path = tempfile.mkstemp()
+try:
+with os.fdopen(fd, 'w') as tmp:
+
+tmp.write(clang_output)
+repo = git.repo(".")
+return repo.diff(['--no-index', path, tmp_path])
+
+finally:
+os.remove(tmp_path)
+
+if os.path.isfile(path) == True:
+cmd = get_command() + " --style=file " + path
+output_clang = ex.command(command=cmd, shell=True)
+output_clang = output_clang[2]
+diff = clang_to_git_diff(output_clang, path)
+else:
+onlyfiles = [f for f in os.listdir(path)]
+for file in onlyfiles:
+file = os.path.join(path, file)
+
+if ignore_file is not None and file == ignore_file:
+continue
+
+if file.endswith('.c') or file.endswith('.h'):
+cmd = get_command() + " --style=file " + file
+output_clang = ex.command(command=cmd, shell=True)
+output_clang = output_clang[2]
+diff += clang_to_git_diff(output_clang, os.path.join(path, 
file))
+return diff
+
+
+def color_text(string, col, style=1):
+return f"\033[{style};{col};{col}m{string}\033[0;0m"
+
+
+def handle_errors(path, output, verbose=False,):
+if len(output) < 1:
+print("Everything is clean - No style issues")
+else:
+print(color_text("Checking for style differences...", 34, style=3))
+
+out = output.split('\n')
+files = []
+num_diff = 0
+for line in out:
+
+if line.startswith("---"):
+file = str(re.sub('^---\s[ab]', '', line))
+files.append(file)
+
+elif li

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,
I wrote the style checking tool and looking forward to some feedback to
improve it...
https://github.com/Idadelveloper/rtems-tools/blob/master/misc/tools/style.py

On Wed, 11 Aug 2021, 5:07 pm Gedare Bloom,  wrote:

> On Tue, Aug 10, 2021 at 3:21 PM Ida Delphine  wrote:
> >
> > Hi everyone,
> > I was able to successfully build LLVM from source using "ninja" instead
> of "make" after a couple of failed attempts because I kept running out of
> resources.
> >
> > Is there anything else I am supposed to do as far building LLVM is
> concerned? Or will every user first have to clone the llvm repo and build
> it from source like I did?
> >
> I think it would be good to update/provide RSB recipe for newer
> version(s) of LLVM. If you can do that after the GSoC coding period
> ends, that would be great.
>
> > On Fri, 16 Jul 2021, 5:28 am Chris Johns,  wrote:
> >>
> >> Hi,
> >>
> >> I will bring the discussion to the devel list and I hope the comments
> are in
> >> line with the purpose of the project. Please correct what I say if it
> is not.
> >>
> >> The pre-commit script that is in github review is a good base and I
> believe it
> >> solves that problem for those on Linux. It is a great start and it is
> nice to see.
> >>
> >> The work needs to mature and progress and that means a few things. I was
> >> approached by Joel about where this would live in rtems-tools. As the
> script
> >> stands it is not suitable for rtems-tool because the format is specific
> to the
> >> score code in rtems.git.
> >>
> >> I think a pre-commit script needs to live in the repo it is for in a
> spot a user
> >> can copy to the hooks directory of their repo. For example `git-hooks`.
> >>
> >> A git hooks script for rtems.git needs to run on all the supported
> hosts or we
> >> may result in patches being left on the floor. If a contributor's host
> OS is not
> >> supported and the patch is rejected for formatting reasons picked up by
> the
> >> check the contributor may just walk away.
> >>
> >> The script should use `/usr/bin/env python3` and it needs to check for
> a range
> >> of `clang-format` instances. FreeBSD has a package that installs the
> format
> >> command as `clang-format10` for LLVM 10 and `clang-format11` for
> version 11.
> >>
> >> A contributor being able to run the script may depend on the host
> having a
> >> package or packages installed. Given this is for RTEMS development that
> is fine.
> >> The script needs to handle any set up errors nicely if something is
> missing. I
> >> prefer we avoid the "experts" approach to error management.
> >>
> >> There is possible future work adding a command to rtems-tools. Ida and I
> >> discussed this on discord and we decided a command called `rtems-style`
> would be
> >> nice. It would be nice if that command checked, ie `--mode=check`, a
> style as
> >> well as `--mode=reformat` to automatically reformat a source file.
> >>
> >> A command for rtems-tools has to support python2 and python3 and it has
> to
> >> handle errors in suitable manner. Printing uncaught exception is not
> OK. It
> >> should also be self contained and not depend on any pip python packages.
> >>
> >> If an `rtems-style` command is created and installed when rtems-tool is
> >> installed the pre-commit git script could be made to use it and so the
> style is
> >> held in a single location.
> >>
> >> Finally an rtems-style command could be extended to support python
> >> (--lang=python) or other styles for other code formats. This is inline
> with our
> >> other eco-system interfaces we provide.
> >>
> >> I hope this helps.
> >>
> >> Chris
> >>
> >> On 16/7/21 5:13 am, Ida Delphine wrote:
> >> > I will check on this
> >> >
> >> > On Thu, Jul 15, 2021 at 3:39 PM Gedare Bloom  >> > <mailto:ged...@rtems.org>> wrote:
> >> >
> >> > On Thu, Jul 15, 2021 at 5:19 AM Ida Delphine  >> > <mailto:idad...@gmail.com>> wrote:
> >> > >
> >> > > Hello everyone,
> >> > > From the discussion on discord it looks like clang-format
> cannot be
> >> > installed on MacOS and FreeBSD. Is there any alternative or way
> to have it
> >> > on these operating systems?
> >> 

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hi everyone,
I was able to successfully build LLVM from source using "ninja" instead of
"make" after a couple of failed attempts because I kept running out of
resources.

Is there anything else I am supposed to do as far building LLVM is
concerned? Or will every user first have to clone the llvm repo and build
it from source like I did?

On Fri, 16 Jul 2021, 5:28 am Chris Johns,  wrote:

> Hi,
>
> I will bring the discussion to the devel list and I hope the comments are
> in
> line with the purpose of the project. Please correct what I say if it is
> not.
>
> The pre-commit script that is in github review is a good base and I
> believe it
> solves that problem for those on Linux. It is a great start and it is nice
> to see.
>
> The work needs to mature and progress and that means a few things. I was
> approached by Joel about where this would live in rtems-tools. As the
> script
> stands it is not suitable for rtems-tool because the format is specific to
> the
> score code in rtems.git.
>
> I think a pre-commit script needs to live in the repo it is for in a spot
> a user
> can copy to the hooks directory of their repo. For example `git-hooks`.
>
> A git hooks script for rtems.git needs to run on all the supported hosts
> or we
> may result in patches being left on the floor. If a contributor's host OS
> is not
> supported and the patch is rejected for formatting reasons picked up by the
> check the contributor may just walk away.
>
> The script should use `/usr/bin/env python3` and it needs to check for a
> range
> of `clang-format` instances. FreeBSD has a package that installs the format
> command as `clang-format10` for LLVM 10 and `clang-format11` for version
> 11.
>
> A contributor being able to run the script may depend on the host having a
> package or packages installed. Given this is for RTEMS development that is
> fine.
> The script needs to handle any set up errors nicely if something is
> missing. I
> prefer we avoid the "experts" approach to error management.
>
> There is possible future work adding a command to rtems-tools. Ida and I
> discussed this on discord and we decided a command called `rtems-style`
> would be
> nice. It would be nice if that command checked, ie `--mode=check`, a style
> as
> well as `--mode=reformat` to automatically reformat a source file.
>
> A command for rtems-tools has to support python2 and python3 and it has to
> handle errors in suitable manner. Printing uncaught exception is not OK. It
> should also be self contained and not depend on any pip python packages.
>
> If an `rtems-style` command is created and installed when rtems-tool is
> installed the pre-commit git script could be made to use it and so the
> style is
> held in a single location.
>
> Finally an rtems-style command could be extended to support python
> (--lang=python) or other styles for other code formats. This is inline
> with our
> other eco-system interfaces we provide.
>
> I hope this helps.
>
> Chris
>
> On 16/7/21 5:13 am, Ida Delphine wrote:
> > I will check on this
> >
> > On Thu, Jul 15, 2021 at 3:39 PM Gedare Bloom  > <mailto:ged...@rtems.org>> wrote:
> >
> > On Thu, Jul 15, 2021 at 5:19 AM Ida Delphine  > <mailto:idad...@gmail.com>> wrote:
> > >
> > > Hello everyone,
> > > From the discussion on discord it looks like clang-format cannot be
> > installed on MacOS and FreeBSD. Is there any alternative or way to
> have it
> > on these operating systems?
> > >
> > What are the challenges with them? Can clang-format be built from
> > source on those hosts?
> >
> > > On Wed, 5 May 2021, 10:21 pm Ida Delphine,  > <mailto:idad...@gmail.com>> wrote:
> > >>
> > >> Hello everyone,
> > >>
> > >> Regarding this project (https://devel.rtems.org/ticket/3860
> > <https://devel.rtems.org/ticket/3860>) I went with clang-format as
> we all
> > agreed. I have tested it on some "score" files and it made some
> changes
> > which I don't think are very much in line with the RTEMS coding
> style.
> > However, it wasn't really clear if we will chage the RTEMS coding
> style or
> > try to make changes to clang-format to fit the style.
> > >> Please will love to know the best option.
> > >>
> > >> Cheers,
> > >> Ida.
> > >
> > > ___
> > > devel mailing list
> > > devel@rtems.org <mailto:devel@rtems.org>
> > > http://lists.rtems.org/mailman/listinfo/devel
> > <http://lists.rtems.org/mailman/listinfo/devel>
> >
> >
> > ___
> > 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

Re: Error when trying to build llvm

[Ida Delphine]

Hello,
After several attempts of passing that command in the wrong build
directory, I finally was able to find the right build directory, and here's
what I found in ida.log:
https://pastebin.com/hPMmFCyj

I really can't make out what's going on or what to do next. Please help

On Fri, Jul 30, 2021 at 8:57 PM Joel Sherrill  wrote:

> On Fri, Jul 30, 2021 at 1:32 PM Ida Delphine  wrote:
> >
> > Just installed swig and now met with another error. Can't find what is
> really wrong.
> > RTEMS Source Builder - Set Builder, 6 (c938bd7cbe16)
> > Build Set: 6/rtems-llvm
> > Build Set: devel/swig.bset
> > Build Set: devel/autotools-internal.bset
> > config: devel/autoconf-2.69-1.cfg
> > package: autoconf-2.69-x86_64-linux-gnu-1
> > building: autoconf-2.69-x86_64-linux-gnu-1
> > sizes: autoconf-2.69-x86_64-linux-gnu-1: 7.493MB (installed: 0.000B)
> > cleaning: autoconf-2.69-x86_64-linux-gnu-1
> > config: devel/automake-1.12.6-1.cfg
> > package: automake-1.12.6-x86_64-linux-gnu-1
> > building: automake-1.12.6-x86_64-linux-gnu-1
> > sizes: automake-1.12.6-x86_64-linux-gnu-1: 8.085MB (installed: 0.000B)
> > cleaning: automake-1.12.6-x86_64-linux-gnu-1
> > config: devel/libtool-2.4.2-1.cfg
> > package: libtool-2.4.2-x86_64-linux-gnu-1
> > building: libtool-2.4.2-x86_64-linux-gnu-1
> > sizes: libtool-2.4.2-x86_64-linux-gnu-1: 12.775MB (installed: 0.000B)
> > cleaning: libtool-2.4.2-x86_64-linux-gnu-1
> > cleaning: autoconf-2.69-x86_64-linux-gnu-1
> > cleaning: automake-1.12.6-x86_64-linux-gnu-1
> > cleaning: libtool-2.4.2-x86_64-linux-gnu-1
> > Build Sizes: usage: 12.775MB total: 79.327MB (sources: 79.308MB,
> patches: 19.412KB, installed 0.000B)
> > Build Set: Time 0:00:17.154758
> > config: devel/swig-4.0.1.cfg
> > package: swig-4.0.1-x86_64-linux-gnu-1
> > building: swig-4.0.1-x86_64-linux-gnu-1
> > sizes: swig-4.0.1-x86_64-linux-gnu-1: 106.899MB (installed: 0.000B)
> > cleaning: swig-4.0.1-x86_64-linux-gnu-1
> > cleaning: swig-4.0.1-x86_64-linux-gnu-1
> > Build Set: Time 0:01:27.065144
> > config: tools/rtems-llvm-8.0.1.cfg
> > package: rtems-llvm-8.0.1-x86_64-linux-gnu-1
> > building: rtems-llvm-8.0.1-x86_64-linux-gnu-1
> > error: building rtems-llvm-8.0.1-x86_64-linux-gnu-1
> > Build FAILED
> >   See error report: rsb-report-rtems-llvm-8.0.1-x86_64-linux-gnu-1.txt
> > error: building rtems-llvm-8.0.1-x86_64-linux-gnu-1
> > Build Set: Time 0:04:53.632167
> > Build FAILED
> > The error report: https://pastebin.com/nFYzqWqY
>
> I don't see any compiler errors. I see warnings and if they built with
> -Werror,
> then it would fail.
>
> I think there is a way to force a cmake build to show the command invoked.
> This
> has lots of details:
>
>
> https://stackoverflow.com/questions/2670121/using-cmake-with-gnu-make-how-can-i-see-the-exact-commands
>
> I think you can manually go down into the build directory which is left
> after the build failure, and type "make VERBOSE=1" >ida.log 2>&1"
>
> Then the file ida.log should show all the commands.
>
> The URL above shows how to do it via cmake. But in this case, I think
> going into the RSB build/ directory and doing the make by hand will
> give us the next bit of into -- does it compile with -Werror.
>
> >
> > On Fri, Jul 30, 2021 at 2:24 PM Joel Sherrill  wrote:
> >>
> >> On Fri, Jul 30, 2021 at 12:46 AM Ida Delphine 
> wrote:
> >> >
> >> > Hello everyone,
> >> > I have been trying to build llvm using the command
> >> > ../source-builder/sb-set-builder --prefix=$HOME/development/rtems/6
> 6/rtems-llvm
> >> > Here's the error report
> >> > https://pastebin.com/vAXgwXMW
> >>
> >> It would have been helpful to have put the error lines in the email
> >> and a link to the full log.
> >>
> >> -- Could NOT find libedit (missing: libedit_INCLUDE_DIRS
> libedit_LIBRARIES)
> >> -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
> >> CMake Error at
> /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146
> >> (message):
> >> Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
> >> Call Stack (most recent call first):
> >> /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393
> >> (_FPHSA_FAILURE_MESSAGE)
> >> /usr/share/cmake-3.16/Modules/FindSWIG.cmake:64
> >> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
> >> tools/lldb/scripts/CMakeLists.txt:18 (find_package)
> >>
> >> > Please what am I missing?
> >>
> >> Based on goo

Re: Error when trying to build llvm

[Ida Delphine]

Just installed swig and now met with another error. Can't find what is
really wrong.
RTEMS Source Builder - Set Builder, 6 (c938bd7cbe16)
Build Set: 6/rtems-llvm
Build Set: devel/swig.bset
Build Set: devel/autotools-internal.bset
config: devel/autoconf-2.69-1.cfg
package: autoconf-2.69-x86_64-linux-gnu-1
building: autoconf-2.69-x86_64-linux-gnu-1
sizes: autoconf-2.69-x86_64-linux-gnu-1: 7.493MB (installed: 0.000B)
cleaning: autoconf-2.69-x86_64-linux-gnu-1
config: devel/automake-1.12.6-1.cfg
package: automake-1.12.6-x86_64-linux-gnu-1
building: automake-1.12.6-x86_64-linux-gnu-1
sizes: automake-1.12.6-x86_64-linux-gnu-1: 8.085MB (installed: 0.000B)
cleaning: automake-1.12.6-x86_64-linux-gnu-1
config: devel/libtool-2.4.2-1.cfg
package: libtool-2.4.2-x86_64-linux-gnu-1
building: libtool-2.4.2-x86_64-linux-gnu-1
sizes: libtool-2.4.2-x86_64-linux-gnu-1: 12.775MB (installed: 0.000B)
cleaning: libtool-2.4.2-x86_64-linux-gnu-1
cleaning: autoconf-2.69-x86_64-linux-gnu-1
cleaning: automake-1.12.6-x86_64-linux-gnu-1
cleaning: libtool-2.4.2-x86_64-linux-gnu-1
Build Sizes: usage: 12.775MB total: 79.327MB (sources: 79.308MB, patches:
19.412KB, installed 0.000B)
Build Set: Time 0:00:17.154758
config: devel/swig-4.0.1.cfg
package: swig-4.0.1-x86_64-linux-gnu-1
building: swig-4.0.1-x86_64-linux-gnu-1
sizes: swig-4.0.1-x86_64-linux-gnu-1: 106.899MB (installed: 0.000B)
cleaning: swig-4.0.1-x86_64-linux-gnu-1
cleaning: swig-4.0.1-x86_64-linux-gnu-1
Build Set: Time 0:01:27.065144
config: tools/rtems-llvm-8.0.1.cfg
package: rtems-llvm-8.0.1-x86_64-linux-gnu-1
building: rtems-llvm-8.0.1-x86_64-linux-gnu-1
error: building rtems-llvm-8.0.1-x86_64-linux-gnu-1
Build FAILED
  See error report: rsb-report-rtems-llvm-8.0.1-x86_64-linux-gnu-1.txt
error: building rtems-llvm-8.0.1-x86_64-linux-gnu-1
Build Set: Time 0:04:53.632167
Build FAILED
The error report: https://pastebin.com/nFYzqWqY

On Fri, Jul 30, 2021 at 2:24 PM Joel Sherrill  wrote:

> On Fri, Jul 30, 2021 at 12:46 AM Ida Delphine  wrote:
> >
> > Hello everyone,
> > I have been trying to build llvm using the command
> > ../source-builder/sb-set-builder --prefix=$HOME/development/rtems/6
> 6/rtems-llvm
> > Here's the error report
> > https://pastebin.com/vAXgwXMW
>
> It would have been helpful to have put the error lines in the email
> and a link to the full log.
>
> -- Could NOT find libedit (missing: libedit_INCLUDE_DIRS libedit_LIBRARIES)
> -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
> CMake Error at
> /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146
> (message):
> Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
> Call Stack (most recent call first):
> /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393
> (_FPHSA_FAILURE_MESSAGE)
> /usr/share/cmake-3.16/Modules/FindSWIG.cmake:64
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
> tools/lldb/scripts/CMakeLists.txt:18 (find_package)
>
> > Please what am I missing?
>
> Based on google results and other people having the same issue, you may not
> have swig installed. It is something to install with npm from what I
> see. Other people
> have it but need to set some variables to let cmake know where it is.
>
> Hopefully installing it will help. Chris should comment on this from
> an RSB perspective.
>
> --joel
>
> >
> > ___
> > 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

Error when trying to build llvm

[Ida Delphine]

Hello everyone,
I have been trying to build llvm using the command
../source-builder/sb-set-builder --prefix=$HOME/development/rtems/6
6/rtems-llvm
Here's the error report
https://pastebin.com/vAXgwXMW
Please what am I missing?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

I will check on this

On Thu, Jul 15, 2021 at 3:39 PM Gedare Bloom  wrote:

> On Thu, Jul 15, 2021 at 5:19 AM Ida Delphine  wrote:
> >
> > Hello everyone,
> > From the discussion on discord it looks like clang-format cannot be
> installed on MacOS and FreeBSD. Is there any alternative or way to have it
> on these operating systems?
> >
> What are the challenges with them? Can clang-format be built from
> source on those hosts?
>
> > On Wed, 5 May 2021, 10:21 pm Ida Delphine,  wrote:
> >>
> >> Hello everyone,
> >>
> >> Regarding this project (https://devel.rtems.org/ticket/3860) I went
> with clang-format as we all agreed. I have tested it on some "score" files
> and it made some changes which I don't think are very much in line with the
> RTEMS coding style. However, it wasn't really clear if we will chage the
> RTEMS coding style or try to make changes to clang-format to fit the style.
> >> Please will love to know the best option.
> >>
> >> Cheers,
> >> Ida.
> >
> > ___
> > 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

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,
>From the discussion on discord it looks like clang-format cannot be
installed on MacOS and FreeBSD. Is there any alternative or way to have it
on these operating systems?

On Wed, 5 May 2021, 10:21 pm Ida Delphine,  wrote:

> Hello everyone,
>
> Regarding this project (https://devel.rtems.org/ticket/3860) I went with
> clang-format as we all agreed. I have tested it on some "score" files and
> it made some changes which I don't think are very much in line with the
> RTEMS coding style. However, it wasn't really clear if we will chage the
> RTEMS coding style or try to make changes to clang-format to fit the style.
> Please will love to know the best option.
>
> Cheers,
> Ida.
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello,
What I did was copy and paste the script into my local
rtems/.git/hooks/pre-commit file, intentionally made some wrong style
changes in some files and tried making a commit. I have documented how it
works here
https://github.com/Idadelveloper/rtems-docs/commit/a30407e159726ce745df7ab4813c5b3a58b34f93
Will love feedback to also make it better.

On Mon, Jul 12, 2021 at 8:22 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> Hello Ida,
>
> On 10/07/2021 01:08, Ida Delphine wrote:
> > I added the functionality for my script to ignore certain directories
> > like /bsps/, /testsuites/, '/cpukit/zlib', '/cpukit/mghttpd'.
> > https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
> > <https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit>
> > Are there any extra directories I should exclude?
> >
> > Also open to more suggestions and feedback to make my code better :)
>
> what do I have to do to test this pre-commit hook?
>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.hu...@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,
I added the functionality for my script to ignore certain directories like
/bsps/, /testsuites/, '/cpukit/zlib', '/cpukit/mghttpd'.
https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
Are there any extra directories I should exclude?

Also open to more suggestions and feedback to make my code better :)

Cheers,
Ida.

On Sun, Jul 4, 2021 at 12:40 AM Ida Delphine  wrote:

> Hello mentors,
>
> I got some feedback and I have improved my code based on it -
> https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
> Will love to get some more feedback and ways to make it look better.
> And is it okay I start working on its documentation though it hasn't been
> approved yet?
>
> Cheers,
> Ida
>
> On Thu, Jul 1, 2021 at 6:42 PM Ida Delphine  wrote:
>
>> Thank you. I will make changes accordingly.
>>
>> On Thu, 1 Jul 2021, 5:31 pm Gedare Bloom,  wrote:
>>
>>> Hi Ida,
>>>
>>> On Tue, Jun 29, 2021 at 1:11 PM Ida Delphine  wrote:
>>> >
>>> > Hello mentors,
>>> >
>>> > Here is the code for my pre-commit hook script. How it works is by
>>> default, upon commiting it outputs a warning stating the number of style
>>> issues in case there are mismatches.
>>> > The user can trigger the strict mode which gives a more detailed
>>> output of the style issues by running adding the mode to the config file (
>>> git config mode "strict") - will document this.
>>> >
>>> > https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
>>> >
>>> I made comments on your commit that added this:
>>>
>>> https://github.com/Idadelveloper/rtems/commit/6bfc4802d17b3aab260190d53467b750848f0002
>>>
>>> > I had already sent some screenshots here on how the outcome looks
>>> like. Will love to improve my code based on your feedback and get more
>>> suggestions.
>>> >
>>> >
>>> > On Mon, Jun 21, 2021 at 7:05 PM Gedare Bloom  wrote:
>>> >>
>>> >>
>>> >>
>>> >> On Sun, Jun 20, 2021 at 1:13 AM Ida Delphine 
>>> wrote:
>>> >>>
>>> >>> Hello everyone,
>>> >>> I updated the hooks script. About the modes, we have the default,
>>> "strict" and "nonstrict" (couldn't think of better names). With the default
>>> mode, it prints a warning specifying the number of style issues if any and
>>> aborts the commit. With the strict mode, it goes into more detail showing
>>> both the formatted and unformatted patch, the number of style issues, and
>>> aborts the commit. In the non-strict mode, it simply displays the warning
>>> with the style issues and the commit happens.
>>> >>>
>>> >>> The default mode basically happens when you run
>>> >>>>
>>> >>>> git commit -m "Commit message"
>>> >>>
>>> >>> The best method I could find to pass arguments to a script was via
>>> environment variables. So the nonstrict mode applies when you run
>>> >>>>
>>> >>>> STYLEMODE=nonstrict git commit -m "Commit message"
>>> >>>
>>> >>> The strict mode applies when you run
>>> >>>>
>>> >>>> STYLEMODE=strict git commit -m "Commit message"
>>> >>>
>>> >>>
>>> >> What are the possible options to pass arguments? (Maybe, a blog post
>>> :)) Reading from a git-config file would be better than environment
>>> variables.
>>> >>
>>> >> It might be better to share screenshots by a link (e.g., a blog post
>>> :)) to avoid hitting the mailing list attachment limits.
>>> >>
>>> >> Gedare
>>>
>>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello mentors,

I got some feedback and I have improved my code based on it -
https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
Will love to get some more feedback and ways to make it look better.
And is it okay I start working on its documentation though it hasn't been
approved yet?

Cheers,
Ida

On Thu, Jul 1, 2021 at 6:42 PM Ida Delphine  wrote:

> Thank you. I will make changes accordingly.
>
> On Thu, 1 Jul 2021, 5:31 pm Gedare Bloom,  wrote:
>
>> Hi Ida,
>>
>> On Tue, Jun 29, 2021 at 1:11 PM Ida Delphine  wrote:
>> >
>> > Hello mentors,
>> >
>> > Here is the code for my pre-commit hook script. How it works is by
>> default, upon commiting it outputs a warning stating the number of style
>> issues in case there are mismatches.
>> > The user can trigger the strict mode which gives a more detailed output
>> of the style issues by running adding the mode to the config file ( git
>> config mode "strict") - will document this.
>> >
>> > https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
>> >
>> I made comments on your commit that added this:
>>
>> https://github.com/Idadelveloper/rtems/commit/6bfc4802d17b3aab260190d53467b750848f0002
>>
>> > I had already sent some screenshots here on how the outcome looks like.
>> Will love to improve my code based on your feedback and get more
>> suggestions.
>> >
>> >
>> > On Mon, Jun 21, 2021 at 7:05 PM Gedare Bloom  wrote:
>> >>
>> >>
>> >>
>> >> On Sun, Jun 20, 2021 at 1:13 AM Ida Delphine 
>> wrote:
>> >>>
>> >>> Hello everyone,
>> >>> I updated the hooks script. About the modes, we have the default,
>> "strict" and "nonstrict" (couldn't think of better names). With the default
>> mode, it prints a warning specifying the number of style issues if any and
>> aborts the commit. With the strict mode, it goes into more detail showing
>> both the formatted and unformatted patch, the number of style issues, and
>> aborts the commit. In the non-strict mode, it simply displays the warning
>> with the style issues and the commit happens.
>> >>>
>> >>> The default mode basically happens when you run
>> >>>>
>> >>>> git commit -m "Commit message"
>> >>>
>> >>> The best method I could find to pass arguments to a script was via
>> environment variables. So the nonstrict mode applies when you run
>> >>>>
>> >>>> STYLEMODE=nonstrict git commit -m "Commit message"
>> >>>
>> >>> The strict mode applies when you run
>> >>>>
>> >>>> STYLEMODE=strict git commit -m "Commit message"
>> >>>
>> >>>
>> >> What are the possible options to pass arguments? (Maybe, a blog post
>> :)) Reading from a git-config file would be better than environment
>> variables.
>> >>
>> >> It might be better to share screenshots by a link (e.g., a blog post
>> :)) to avoid hitting the mailing list attachment limits.
>> >>
>> >> Gedare
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Thank you. I will make changes accordingly.

On Thu, 1 Jul 2021, 5:31 pm Gedare Bloom,  wrote:

> Hi Ida,
>
> On Tue, Jun 29, 2021 at 1:11 PM Ida Delphine  wrote:
> >
> > Hello mentors,
> >
> > Here is the code for my pre-commit hook script. How it works is by
> default, upon commiting it outputs a warning stating the number of style
> issues in case there are mismatches.
> > The user can trigger the strict mode which gives a more detailed output
> of the style issues by running adding the mode to the config file ( git
> config mode "strict") - will document this.
> >
> > https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit
> >
> I made comments on your commit that added this:
>
> https://github.com/Idadelveloper/rtems/commit/6bfc4802d17b3aab260190d53467b750848f0002
>
> > I had already sent some screenshots here on how the outcome looks like.
> Will love to improve my code based on your feedback and get more
> suggestions.
> >
> >
> > On Mon, Jun 21, 2021 at 7:05 PM Gedare Bloom  wrote:
> >>
> >>
> >>
> >> On Sun, Jun 20, 2021 at 1:13 AM Ida Delphine  wrote:
> >>>
> >>> Hello everyone,
> >>> I updated the hooks script. About the modes, we have the default,
> "strict" and "nonstrict" (couldn't think of better names). With the default
> mode, it prints a warning specifying the number of style issues if any and
> aborts the commit. With the strict mode, it goes into more detail showing
> both the formatted and unformatted patch, the number of style issues, and
> aborts the commit. In the non-strict mode, it simply displays the warning
> with the style issues and the commit happens.
> >>>
> >>> The default mode basically happens when you run
> >>>>
> >>>> git commit -m "Commit message"
> >>>
> >>> The best method I could find to pass arguments to a script was via
> environment variables. So the nonstrict mode applies when you run
> >>>>
> >>>> STYLEMODE=nonstrict git commit -m "Commit message"
> >>>
> >>> The strict mode applies when you run
> >>>>
> >>>> STYLEMODE=strict git commit -m "Commit message"
> >>>
> >>>
> >> What are the possible options to pass arguments? (Maybe, a blog post
> :)) Reading from a git-config file would be better than environment
> variables.
> >>
> >> It might be better to share screenshots by a link (e.g., a blog post
> :)) to avoid hitting the mailing list attachment limits.
> >>
> >> Gedare
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello mentors,

Here is the code for my pre-commit hook script. How it works is by default,
upon commiting it outputs a warning stating the number of style issues in
case there are mismatches.
The user can trigger the strict mode which gives a more detailed output of
the style issues by running adding the mode to the config file ( git config
mode "strict") - will document this.

https://github.com/Idadelveloper/rtems/blob/master/hooks/pre-commit

I had already sent some screenshots here on how the outcome looks like.
Will love to improve my code based on your feedback and get more
suggestions.


On Mon, Jun 21, 2021 at 7:05 PM Gedare Bloom  wrote:

>
>
> On Sun, Jun 20, 2021 at 1:13 AM Ida Delphine  wrote:
>
>> Hello everyone,
>> I updated the hooks script. About the modes, we have the default,
>> "strict" and "nonstrict" (couldn't think of better names). With the default
>> mode, it prints a warning specifying the number of style issues if any and
>> aborts the commit. With the strict mode, it goes into more detail showing
>> both the formatted and unformatted patch, the number of style issues, and
>> aborts the commit. In the non-strict mode, it simply displays the warning
>> with the style issues and the commit happens.
>>
>> The default mode basically happens when you run
>>
>>> git commit -m "Commit message"
>>>
>> The best method I could find to pass arguments to a script was via
>> environment variables. So the nonstrict mode applies when you run
>>
>>> STYLEMODE=nonstrict git commit -m "Commit message"
>>>
>> The strict mode applies when you run
>>
>>> STYLEMODE=strict git commit -m "Commit message"
>>>
>>
>> What are the possible options to pass arguments? (Maybe, a blog post :))
> Reading from a git-config file would be better than environment variables.
>
> It might be better to share screenshots by a link (e.g., a blog post :))
> to avoid hitting the mailing list attachment limits.
>
> Gedare
>
>>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH] user: Fixed typo to build hello application

[Ida Delphine]

---
 user/start/app.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/user/start/app.rst b/user/start/app.rst
index 2bb0a9e..19ae3e1 100644
--- a/user/start/app.rst
+++ b/user/start/app.rst
@@ -209,7 +209,7 @@ Run the executable:
 
 .. code-block:: none
 
-$HOME/quick-start/rtems/6/bin/rtems-run --rtems-bsps=erc32-sis 
build/sparc-rtems-erc32/hello.exe
+$HOME/quick-start/rtems/6/bin/rtems-run --rtems-bsps=erc32-sis 
build/sparc-rtems6-erc32/hello.exe
 
 The output will be something close to:
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

How to write a build script to the rsb

[Ida Delphine]

Hi everyone,

So I'm working on automatic style checking for RTEMS score and some time
ago we agreed on using clang-format. Since I will be making some costum
changes to the source code of clang-format, I intend using the rsb to build
it before it can be used to format files to match the RTEMS style.

I'm not sure how to go about writing this script to build clang-format
using the rsb. Please I will love some guidance on how to go about it...
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Okay. I will do that.

On Fri, 4 Jun 2021, 10:48 pm Gedare Bloom,  wrote:

> On Fri, Jun 4, 2021 at 2:57 PM Ida Delphine  wrote:
> >
> > Okay, I will take a look.
> >
> > Regarding me asking a question in the appropriate clang-format mailing
> list should it be just regarding the parentheses and braces being aligned?
> >
> That would be the right question to ask, if you can't find a way to
> align the closing parenthesis.
>
> You might also follow-up that old thread related to alignment of the
> pointers.
>
> > On Fri, Jun 4, 2021 at 8:41 PM Joel Sherrill  wrote:
> >>
> >>
> >>
> >> On Fri, Jun 4, 2021 at 12:39 PM Gedare Bloom  wrote:
> >>>
> >>> On Fri, Jun 4, 2021 at 8:47 AM Joel Sherrill  wrote:
> >>> >
> >>> >
> >>> >
> >>> > On Fri, Jun 4, 2021 at 12:24 AM Ida Delphine 
> wrote:
> >>> >>
> >>> >> Hello everyone,
> >>> >>
> >>> >> I applied the configuration Sebastian used and ran clang-format on
> cpukit/score/src/threadqenque.c and so far these are the differences I
> could notice...
> >>> >> Below are some example areas in the code you can spot the
> differences:
> >>> >>
> >>> >> In line 68, the ")" at the end of the parameter list needs to be in
> a new row, but this doesn't seem to be supported in clang-format.
> >>> >
> >>> > If I understand correctly, clang-format does not like:
> >>> >
> >>> > https://git.rtems.org/rtems/tree/cpukit/score/src/threadqenqueue.c
> >>> >
> >>> > which has the first parameter on its one line but wants the first
> parameter
> >>> > after the open parenthesis?
> >>> >
> >>> > The RTEMS style would seem to correspond to AlignAfterOpenBracket
> being
> >>> > set to AlwaysBreak
> >>> >
> >>> >>
> >>> >> In line 142, if the function call is split into multiple rows, the
> ");" should always be in a new row.
> >>> >
> >>> > Having the closing parenthesis on its own line may end up being
> something
> >>> > we have to change the RTEMS style on. I do not see an option in their
> >>> > documentation to do this. Unfortunate, since I like the symmetry
> between
> >>> > braces and parentheses.
> >>> >
> >>> >  Could you file an issue with them and/or ask a question the
> appropriate
> >>> > mailing list? Please cc Gedara and me. Give them an example. Maybe
> >>> > we are missing something.
> >>> >>
> >>> >> In line 201-202, we can see that the "*" of the pointers are not
> aligned to the right.
> >>> >
> >>> >
> >>> > This seems to be the issue Gedare mentioned which might have a patch.
> >>> > Follow up on that.
> >>> >
> >>> > But I think we had previously discussed this as a point we may have
> to
> >>> > concede and change RTEMS style on.
> >>> >>
> >>> >> You can check out the formatted file here -
> https://pastebin.com/nDBrSSCP
> >>> >
> >>> >
> >>> > Is it just the website or are blank line differences? It may just be
> an
> >>> > illusion. I think the spacing between the numbered lines is greater
> >>> > than in the git view. Just odd.
> >>> >
> >>> That's just the pastebin having more vertical padding between
> consecutive lines.
> >>
> >>
> >> That's what I thought but it did make the code look funny.
> >>
> >> Ida/Gedare.. does this mean there are only 3 style mismatch issues? Or
> only
> >> three in this file?
> >>
> >> Probably should try a few more files and see if there are other
> discrepancies.
> >>
> >> And obviously work on the integration/automation of using the tools. :)
> >>
> >> --joel
> >>
> >>>
> >>>
> >>> > --joel
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Tue, Jun 1, 2021 at 5:36 PM Gedare Bloom 
> wrote:
> >>> >>>
> >>> >>> On Mon, May 31, 2021 at 2:59 PM Ida Delphine 
> wrote:
> >>> >>> >
> >>> >>> > Hi Gedare,
> >>> >>&g

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Okay, I will take a look.

Regarding me asking a question in the appropriate clang-format mailing list
should it be just regarding the parentheses and braces being aligned?

On Fri, Jun 4, 2021 at 8:41 PM Joel Sherrill  wrote:

>
>
> On Fri, Jun 4, 2021 at 12:39 PM Gedare Bloom  wrote:
>
>> On Fri, Jun 4, 2021 at 8:47 AM Joel Sherrill  wrote:
>> >
>> >
>> >
>> > On Fri, Jun 4, 2021 at 12:24 AM Ida Delphine  wrote:
>> >>
>> >> Hello everyone,
>> >>
>> >> I applied the configuration Sebastian used and ran clang-format on
>> cpukit/score/src/threadqenque.c and so far these are the differences I
>> could notice...
>> >> Below are some example areas in the code you can spot the differences:
>> >>
>> >> In line 68, the ")" at the end of the parameter list needs to be in a
>> new row, but this doesn't seem to be supported in clang-format.
>> >
>> > If I understand correctly, clang-format does not like:
>> >
>> > https://git.rtems.org/rtems/tree/cpukit/score/src/threadqenqueue.c
>> >
>> > which has the first parameter on its one line but wants the first
>> parameter
>> > after the open parenthesis?
>> >
>> > The RTEMS style would seem to correspond to AlignAfterOpenBracket being
>> > set to AlwaysBreak
>> >
>> >>
>> >> In line 142, if the function call is split into multiple rows, the
>> ");" should always be in a new row.
>> >
>> > Having the closing parenthesis on its own line may end up being
>> something
>> > we have to change the RTEMS style on. I do not see an option in their
>> > documentation to do this. Unfortunate, since I like the symmetry between
>> > braces and parentheses.
>> >
>> >  Could you file an issue with them and/or ask a question the appropriate
>> > mailing list? Please cc Gedara and me. Give them an example. Maybe
>> > we are missing something.
>> >>
>> >> In line 201-202, we can see that the "*" of the pointers are not
>> aligned to the right.
>> >
>> >
>> > This seems to be the issue Gedare mentioned which might have a patch.
>> > Follow up on that.
>> >
>> > But I think we had previously discussed this as a point we may have to
>> > concede and change RTEMS style on.
>> >>
>> >> You can check out the formatted file here -
>> https://pastebin.com/nDBrSSCP
>> >
>> >
>> > Is it just the website or are blank line differences? It may just be an
>> > illusion. I think the spacing between the numbered lines is greater
>> > than in the git view. Just odd.
>> >
>> That's just the pastebin having more vertical padding between consecutive
>> lines.
>>
>
> That's what I thought but it did make the code look funny.
>
> Ida/Gedare.. does this mean there are only 3 style mismatch issues? Or
> only
> three in this file?
>
> Probably should try a few more files and see if there are other
> discrepancies.
>
> And obviously work on the integration/automation of using the tools. :)
>
> --joel
>
>
>>
>> > --joel
>> >>
>> >>
>> >>
>> >> On Tue, Jun 1, 2021 at 5:36 PM Gedare Bloom  wrote:
>> >>>
>> >>> On Mon, May 31, 2021 at 2:59 PM Ida Delphine 
>> wrote:
>> >>> >
>> >>> > Hi Gedare,
>> >>> >
>> >>> > With regards to your comment on discord on me looking for a tool
>> that works on both patches and source files, it turns out clang-format has
>> that functionality already. Here's what I found -
>> https://clang.llvm.org/docs/ClangFormat.html#script-for-patch-reformatting
>> >>> >
>> >>> > Does it match what you have in mind?
>> >>> >
>> >>> Yes. I think we would want to not use the `-i` option but instead pass
>> >>> through and check the changes. I don't think we should rewrite the
>> >>> patches themselves, but instead we want to use a tool that can be used
>> >>> to check and approve the style of submitted patches. You might need to
>> >>> write a modified version of the clang-format-diff.py to use as a
>> >>> "checker" with ability to provide exceptions to the rules.
>> >>>
>> >>> Gedare
>> >>>
>> >>> > On Thu, May 13, 2021 at 3:49 PM Gedare Bloom 

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,

I applied the configuration Sebastian used and ran clang-format on
cpukit/score/src/threadqenque.c and so far these are the differences I
could notice...
Below are some example areas in the code you can spot the differences:

   - In line 68, the ")" at the end of the parameter list needs to be in a
   new row, but this doesn't seem to be supported in clang-format.
   - In line 142, if the function call is split into multiple rows, the
   ");" should always be in a new row.
   - In line 201-202, we can see that the "*" of the pointers are not
   aligned to the right.

You can check out the formatted file here - https://pastebin.com/nDBrSSCP



On Tue, Jun 1, 2021 at 5:36 PM Gedare Bloom  wrote:

> On Mon, May 31, 2021 at 2:59 PM Ida Delphine  wrote:
> >
> > Hi Gedare,
> >
> > With regards to your comment on discord on me looking for a tool that
> works on both patches and source files, it turns out clang-format has that
> functionality already. Here's what I found -
> https://clang.llvm.org/docs/ClangFormat.html#script-for-patch-reformatting
> >
> > Does it match what you have in mind?
> >
> Yes. I think we would want to not use the `-i` option but instead pass
> through and check the changes. I don't think we should rewrite the
> patches themselves, but instead we want to use a tool that can be used
> to check and approve the style of submitted patches. You might need to
> write a modified version of the clang-format-diff.py to use as a
> "checker" with ability to provide exceptions to the rules.
>
> Gedare
>
> > On Thu, May 13, 2021 at 3:49 PM Gedare Bloom  wrote:
> >>
> >> On Wed, May 12, 2021 at 2:18 PM Ida Delphine  wrote:
> >> >
> >> > Hello everyone,
> >> > Still waiting for some feedback :)
> >> >
> >> > Cheers,
> >> > Ida.
> >> >
> >> > On Mon, 10 May 2021, 5:59 am Ida Delphine,  wrote:
> >> >>
> >> >> Hello everyone,
> >> >> Went through some previous emails and it turns out Sebastian already
> came up with a configuration for clang format which works well for RTEMS
> except for the fact that some configurations haven't been implemented into
> clang-format yet. Using
> >> >>
> >> >> AlignConsecutiveDeclarations: false
> >> >> PointerAlignment: Right
> >> >>
> >> >> Doesn't seem to work.
> >> >> For example in the cpukit/score/src/threadq.c file, something like
> >> >>
> >> >> RTEMS_STATIC_ASSERT(
> >> >> offsetof( Thread_queue_Syslock_queue, Queue.name )
> >> >> == offsetof( struct _Thread_queue_Queue, _name ),
> >> >> THREAD_QUEUE_SYSLOCK_QUEUE_NAME
> >> >> );
> >> >>
> >> >> RTEMS_STATIC_ASSERT(
> >> >> sizeof( Thread_queue_Syslock_queue )
> >> >> == sizeof( struct _Thread_queue_Queue ),
> >> >> THREAD_QUEUE_SYSLOCK_QUEUE_SIZE
> >> >> );
> >> >>
> >> >> #if defined(RTEMS_SMP)
> >> >> void _Thread_queue_Do_acquire_critical(
> >> >> Thread_queue_Control *the_thread_queue,
> >> >> ISR_lock_Context *lock_context
> >> >> )
> >> >> {
> >> >> _Thread_queue_Queue_acquire_critical(
> >> >> _thread_queue->Queue,
> >> >> _thread_queue->Lock_stats,
> >> >> lock_context
> >> >> );
> >> >>
> >> >> becomes this after using the given configuration
> >> >>
> >> >> RTEMS_STATIC_ASSERT(sizeof(Thread_queue_Syslock_queue) ==
> >> >> sizeof(struct _Thread_queue_Queue),
> >> >> THREAD_QUEUE_SYSLOCK_QUEUE_SIZE);
> >> >>
> >> >> #if defined(RTEMS_SMP)
> >> >> void _Thread_queue_Do_acquire_critical(Thread_queue_Control
> *the_thread_queue,
> >> >> ISR_lock_Context *lock_context) {
> >> >> _Thread_queue_Queue_acquire_critical(
> >> >> _thread_queue->Queue, _thread_queue->Lock_stats,
> lock_context);
> >> >>
> >> >> Everything seems manageable except for this alignment issue...
> >> >> This also throws more light on the changes using clang-format (
> https://lists.rtems.org/pipermail/devel/2018-December/024145.html)
> >> >>
> >> I think we're willing to concede the pointer alignment. However, it
> >> would be worth spending some time to see if
> >> https://reviews.llvm.org/D27651 can be made

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hi Gedare,

With regards to your comment on discord on me looking for a tool that works
on both patches and source files, it turns out clang-format has that
functionality already. Here's what I found -
https://clang.llvm.org/docs/ClangFormat.html#script-for-patch-reformatting

Does it match what you have in mind?

On Thu, May 13, 2021 at 3:49 PM Gedare Bloom  wrote:

> On Wed, May 12, 2021 at 2:18 PM Ida Delphine  wrote:
> >
> > Hello everyone,
> > Still waiting for some feedback :)
> >
> > Cheers,
> > Ida.
> >
> > On Mon, 10 May 2021, 5:59 am Ida Delphine,  wrote:
> >>
> >> Hello everyone,
> >> Went through some previous emails and it turns out Sebastian already
> came up with a configuration for clang format which works well for RTEMS
> except for the fact that some configurations haven't been implemented into
> clang-format yet. Using
> >>
> >> AlignConsecutiveDeclarations: false
> >> PointerAlignment: Right
> >>
> >> Doesn't seem to work.
> >> For example in the cpukit/score/src/threadq.c file, something like
> >>
> >> RTEMS_STATIC_ASSERT(
> >> offsetof( Thread_queue_Syslock_queue, Queue.name )
> >> == offsetof( struct _Thread_queue_Queue, _name ),
> >> THREAD_QUEUE_SYSLOCK_QUEUE_NAME
> >> );
> >>
> >> RTEMS_STATIC_ASSERT(
> >> sizeof( Thread_queue_Syslock_queue )
> >> == sizeof( struct _Thread_queue_Queue ),
> >> THREAD_QUEUE_SYSLOCK_QUEUE_SIZE
> >> );
> >>
> >> #if defined(RTEMS_SMP)
> >> void _Thread_queue_Do_acquire_critical(
> >> Thread_queue_Control *the_thread_queue,
> >> ISR_lock_Context *lock_context
> >> )
> >> {
> >> _Thread_queue_Queue_acquire_critical(
> >> _thread_queue->Queue,
> >> _thread_queue->Lock_stats,
> >> lock_context
> >> );
> >>
> >> becomes this after using the given configuration
> >>
> >> RTEMS_STATIC_ASSERT(sizeof(Thread_queue_Syslock_queue) ==
> >> sizeof(struct _Thread_queue_Queue),
> >> THREAD_QUEUE_SYSLOCK_QUEUE_SIZE);
> >>
> >> #if defined(RTEMS_SMP)
> >> void _Thread_queue_Do_acquire_critical(Thread_queue_Control
> *the_thread_queue,
> >> ISR_lock_Context *lock_context) {
> >> _Thread_queue_Queue_acquire_critical(
> >> _thread_queue->Queue, _thread_queue->Lock_stats, lock_context);
> >>
> >> Everything seems manageable except for this alignment issue...
> >> This also throws more light on the changes using clang-format (
> https://lists.rtems.org/pipermail/devel/2018-December/024145.html)
> >>
> I think we're willing to concede the pointer alignment. However, it
> would be worth spending some time to see if
> https://reviews.llvm.org/D27651 can be made to work. The current state
> of the code would need to be compared to the patch on that review
> board.
>
> Beyond that, documenting the clang-format options to use is next, and
> then identifying a plan how to invoke clang-format during a git
> workflow is needed.
>
> >> On Thu, May 6, 2021 at 8:05 PM Joel Sherrill  wrote:
> >>>
> >>>
> >>>
> >>> On Thu, May 6, 2021 at 12:47 PM Christian Mauderer 
> wrote:
> >>>>
> >>>> Hello Ida and Gedare,
> >>>>
> >>>> On 06/05/2021 06:26, Gedare Bloom wrote:
> >>>> > hi Ida,
> >>>> >
> >>>> > On Wed, May 5, 2021 at 3:21 PM Ida Delphine 
> wrote:
> >>>> >>
> >>>> >> Hello everyone,
> >>>> >>
> >>>> >> Regarding this project (https://devel.rtems.org/ticket/3860) I
> went with clang-format as we all agreed. I have tested it on some "score"
> files and it made some changes which I don't think are very much in line
> with the RTEMS coding style. However, it wasn't really clear if we will
> chage the RTEMS coding style or try to make changes to clang-format to fit
> the style.
> >>>> >> Please will love to know the best option.
> >>>> >>
> >>>> > We will likely need to consider our choices carefully. If we can
> find
> >>>> > a suitably close style that is already well-supported by clang, and
> >>>> > get consensus from the maintainers on a change, then that might be
> the
> >>>> > best route forward.
> >>>>
> >>>> +1
> >>>>
> >>>> > I think the first thing to do is take the examples

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,
Still waiting for some feedback :)

Cheers,
Ida.

On Mon, 10 May 2021, 5:59 am Ida Delphine,  wrote:

> Hello everyone,
> Went through some previous emails and it turns out Sebastian already came
> up with a configuration for clang format which works well for RTEMS except
> for the fact that some configurations haven't been implemented into
> clang-format yet. Using
>
> AlignConsecutiveDeclarations: false
> PointerAlignment: Right
>
> Doesn't seem to work.
> For example in the cpukit/score/src/threadq.c file, something like
>
> RTEMS_STATIC_ASSERT(
> offsetof( Thread_queue_Syslock_queue, Queue.name )
> == offsetof( struct _Thread_queue_Queue, _name ),
> THREAD_QUEUE_SYSLOCK_QUEUE_NAME
> );
>
> RTEMS_STATIC_ASSERT(
> sizeof( Thread_queue_Syslock_queue )
> == sizeof( struct _Thread_queue_Queue ),
> THREAD_QUEUE_SYSLOCK_QUEUE_SIZE
> );
>
> #if defined(RTEMS_SMP)
> void _Thread_queue_Do_acquire_critical(
> Thread_queue_Control *the_thread_queue,
> ISR_lock_Context *lock_context
> )
> {
> _Thread_queue_Queue_acquire_critical(
> _thread_queue->Queue,
> _thread_queue->Lock_stats,
> lock_context
> );
>
> becomes this after using the given configuration
>
> RTEMS_STATIC_ASSERT(sizeof(Thread_queue_Syslock_queue) ==
> sizeof(struct _Thread_queue_Queue),
> THREAD_QUEUE_SYSLOCK_QUEUE_SIZE);
>
> #if defined(RTEMS_SMP)
> void _Thread_queue_Do_acquire_critical(Thread_queue_Control *
> the_thread_queue,
> ISR_lock_Context *lock_context) {
> _Thread_queue_Queue_acquire_critical(
> _thread_queue->Queue, _thread_queue->Lock_stats, lock_context);
>
> Everything seems manageable except for this alignment issue...
> This also throws more light on the changes using clang-format (
> https://lists.rtems.org/pipermail/devel/2018-December/024145.html)
>
> On Thu, May 6, 2021 at 8:05 PM Joel Sherrill  wrote:
>
>>
>>
>> On Thu, May 6, 2021 at 12:47 PM Christian Mauderer 
>> wrote:
>>
>>> Hello Ida and Gedare,
>>>
>>> On 06/05/2021 06:26, Gedare Bloom wrote:
>>> > hi Ida,
>>> >
>>> > On Wed, May 5, 2021 at 3:21 PM Ida Delphine  wrote:
>>> >>
>>> >> Hello everyone,
>>> >>
>>> >> Regarding this project (https://devel.rtems.org/ticket/3860) I went
>>> with clang-format as we all agreed. I have tested it on some "score" files
>>> and it made some changes which I don't think are very much in line with the
>>> RTEMS coding style. However, it wasn't really clear if we will chage the
>>> RTEMS coding style or try to make changes to clang-format to fit the style.
>>> >> Please will love to know the best option.
>>> >>
>>> > We will likely need to consider our choices carefully. If we can find
>>> > a suitably close style that is already well-supported by clang, and
>>> > get consensus from the maintainers on a change, then that might be the
>>> > best route forward.
>>>
>>> +1
>>>
>>> > I think the first thing to do is take the examples
>>> > that have been shown by Sebastian that are "close" but not quite
>>> > perfect, and identify the cases where they differ with RTEMS style in
>>> > order to present for discussion here. If consensus can't be reached to
>>> > change the style, then we would need to have a plan for how to improve
>>> > the existing tools for what we have.
>>>
>>> I also found the following tool quite useful to play with the clang
>>> style config:
>>>
>>> https://zed0.co.uk/clang-format-configurator/
>>>
>>> Maybe it can help a bit to find out what certain options mean.
>>>
>>> >
>>> > However, I think there is interest in doing less work on the tool
>>> > side, and more work on how to integrate it into our workflows better.
>>>
>>> +1
>>>
>>
>> I agree with all of this from the student perspective. But we will have
>> to come to some agreement on a machine producible format to
>> be able to use the integration. A report on what doesn't match would
>> give us something to chew on while Ida works the integration.
>>
>> --joel
>>
>>>
>>> >
>>> >> Cheers,
>>> >> Ida.
>>> >> ___
>>> >> 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
>>> >
>>> ___
>>> 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

Re: GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,
Went through some previous emails and it turns out Sebastian already came
up with a configuration for clang format which works well for RTEMS except
for the fact that some configurations haven't been implemented into
clang-format yet. Using

AlignConsecutiveDeclarations: false
PointerAlignment: Right

Doesn't seem to work.
For example in the cpukit/score/src/threadq.c file, something like

RTEMS_STATIC_ASSERT(
offsetof( Thread_queue_Syslock_queue, Queue.name )
== offsetof( struct _Thread_queue_Queue, _name ),
THREAD_QUEUE_SYSLOCK_QUEUE_NAME
);

RTEMS_STATIC_ASSERT(
sizeof( Thread_queue_Syslock_queue )
== sizeof( struct _Thread_queue_Queue ),
THREAD_QUEUE_SYSLOCK_QUEUE_SIZE
);

#if defined(RTEMS_SMP)
void _Thread_queue_Do_acquire_critical(
Thread_queue_Control *the_thread_queue,
ISR_lock_Context *lock_context
)
{
_Thread_queue_Queue_acquire_critical(
_thread_queue->Queue,
_thread_queue->Lock_stats,
lock_context
);

becomes this after using the given configuration

RTEMS_STATIC_ASSERT(sizeof(Thread_queue_Syslock_queue) ==
sizeof(struct _Thread_queue_Queue),
THREAD_QUEUE_SYSLOCK_QUEUE_SIZE);

#if defined(RTEMS_SMP)
void _Thread_queue_Do_acquire_critical(Thread_queue_Control *
the_thread_queue,
ISR_lock_Context *lock_context) {
_Thread_queue_Queue_acquire_critical(
_thread_queue->Queue, _thread_queue->Lock_stats, lock_context);

Everything seems manageable except for this alignment issue...
This also throws more light on the changes using clang-format (
https://lists.rtems.org/pipermail/devel/2018-December/024145.html)

On Thu, May 6, 2021 at 8:05 PM Joel Sherrill  wrote:

>
>
> On Thu, May 6, 2021 at 12:47 PM Christian Mauderer 
> wrote:
>
>> Hello Ida and Gedare,
>>
>> On 06/05/2021 06:26, Gedare Bloom wrote:
>> > hi Ida,
>> >
>> > On Wed, May 5, 2021 at 3:21 PM Ida Delphine  wrote:
>> >>
>> >> Hello everyone,
>> >>
>> >> Regarding this project (https://devel.rtems.org/ticket/3860) I went
>> with clang-format as we all agreed. I have tested it on some "score" files
>> and it made some changes which I don't think are very much in line with the
>> RTEMS coding style. However, it wasn't really clear if we will chage the
>> RTEMS coding style or try to make changes to clang-format to fit the style.
>> >> Please will love to know the best option.
>> >>
>> > We will likely need to consider our choices carefully. If we can find
>> > a suitably close style that is already well-supported by clang, and
>> > get consensus from the maintainers on a change, then that might be the
>> > best route forward.
>>
>> +1
>>
>> > I think the first thing to do is take the examples
>> > that have been shown by Sebastian that are "close" but not quite
>> > perfect, and identify the cases where they differ with RTEMS style in
>> > order to present for discussion here. If consensus can't be reached to
>> > change the style, then we would need to have a plan for how to improve
>> > the existing tools for what we have.
>>
>> I also found the following tool quite useful to play with the clang
>> style config:
>>
>> https://zed0.co.uk/clang-format-configurator/
>>
>> Maybe it can help a bit to find out what certain options mean.
>>
>> >
>> > However, I think there is interest in doing less work on the tool
>> > side, and more work on how to integrate it into our workflows better.
>>
>> +1
>>
>
> I agree with all of this from the student perspective. But we will have
> to come to some agreement on a machine producible format to
> be able to use the integration. A report on what doesn't match would
> give us something to chew on while Ida works the integration.
>
> --joel
>
>>
>> >
>> >> Cheers,
>> >> Ida.
>> >> ___
>> >> 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
>> >
>> ___
>> 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

GSoC - Code Formatting and Style Checking for RTEMS score

[Ida Delphine]

Hello everyone,

Regarding this project (https://devel.rtems.org/ticket/3860) I went with
clang-format as we all agreed. I have tested it on some "score" files and
it made some changes which I don't think are very much in line with the
RTEMS coding style. However, it wasn't really clear if we will chage the
RTEMS coding style or try to make changes to clang-format to fit the style.
Please will love to know the best option.

Cheers,
Ida.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello everyone,
Before submitting my final GSoC proposal will love it if my draft can be
reviewed one more time so that in case I still got errors I could fix them.
Just want to be sure everything is okay.
https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing

Thanks,
Ida.

On Mon, Apr 12, 2021 at 6:40 AM Ida Delphine  wrote:

> Hello all,
> I made some changes to my initial proposal draft based on some feedback I
> got. Here's is the modified version. Please help me review and suggest
> improvements.
>
> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
>
> Cheers,
> Ida.
>
> On Fri, Apr 9, 2021 at 1:51 AM Ida Delphine  wrote:
>
>> Hello All,
>>
>> Just a gentle reminder to please help me review this my proposal draft
>> and help me with ways to make it better :)
>>
>> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
>>
>> Cheers,
>> Ida
>>
>> On Thu, 8 Apr 2021, 6:51 am Ida Delphine,  wrote:
>>
>>> Hello everyone,
>>> Here is the link to my GSoC proposal. Will love if you leave comments on
>>> ways I could make it better or any corrections (Especially the *Proposesd
>>> Schedule* section so that I will be sure about my project deliverables
>>> when inputting them).
>>>
>>> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
>>> I will also love to know about any future improvements to this project.
>>>
>>> Cheers,
>>> Ida.
>>>
>>> On Wed, Apr 7, 2021 at 5:27 PM Gedare Bloom  wrote:
>>>
>>>> On Wed, Apr 7, 2021 at 10:11 AM Ida Delphine  wrote:
>>>> >
>>>> > Hello,
>>>> >
>>>> > In case I succeed with this project will I be required to do some
>>>> documentation on how it works?
>>>> >
>>>> Yes, in general we expect students to produce documentation while they
>>>> work on also creating code.
>>>>
>>>> I think the direction we're heading right now is toward using
>>>> clang-format, perhaps with an update to a common coding style. In this
>>>> case, we solve our problem by policy rather than technical solution,
>>>> and your work should focus on tool integration and automation without
>>>> concern about the coding style itself.
>>>>
>>>> >
>>>> > On Wed, Apr 7, 2021 at 9:51 AM Sebastian Huber <
>>>> sebastian.hu...@embedded-brains.de> wrote:
>>>> >>
>>>> >> On 07/04/2021 09:03, Chris Johns wrote:
>>>> >>
>>>> >> > Would it be pragmatic to review these cases and change the
>>>> standard?
>>>> >>
>>>> >> I sent a patch to review the format changes done by clang-format
>>>> recently:
>>>> >>
>>>> >> https://lists.rtems.org/pipermail/devel/2021-April/066311.html
>>>> >>
>>>> >> It doesn't look that bad from my point of view. Fixing the alignment
>>>> >> issue would make it even better:
>>>> >>
>>>> >> https://reviews.llvm.org/D27651
>>>> >>
>>>> >> >
>>>> >> > I understand the long history but as you point out we either
>>>> invest in the tools
>>>> >> > to support the format, we change what we have or we manage it
>>>> manually.
>>>> >> I would prefer to change the style and use a widely used formatting
>>>> >> tool. I think we spend to much time on the coding style in reviews.
>>>> This
>>>> >> is quite bad since we are all busy with all sorts of things and our
>>>> time
>>>> >> is better spent on more important tasks. A consistently formatted
>>>> source
>>>> >> code is very important, but enforcing this style manually is a waste
>>>> of
>>>> >> time.
>>>> >>
>>>> >> --
>>>> >> embedded brains GmbH
>>>> >> Herr Sebastian HUBER
>>>> >> Dornierstr. 4
>>>> >> 82178 Puchheim
>>>> >> Germany
>>>> >> email: sebastian.hu...@embedded-brains.de
>>>> >> phone: +49-89-18 94 741 - 16
>>>> >> fax:   +49-89-18 94 741 - 08
>>>> >>
>>>> >> Registergericht: Amtsgericht München
>>>> >> Registernummer: HRB 157899
>>>> >> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas
>>>> Dörfler
>>>> >> Unsere Datenschutzerklärung finden Sie hier:
>>>> >> https://embedded-brains.de/datenschutzerklaerung/
>>>> >>
>>>> >> ___
>>>> >> 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

Re: How to run the full RTEMS testsuite

[Ida Delphine]

Thanks, I'll check it out.

On Sun, Apr 11, 2021 at 6:57 AM Eshan Dhawan 
wrote:

>
> On 11-Apr-2021, at 1:15 AM, Ida Delphine  wrote:
>
> 
> For some reason I get this:
> rtems-test: command not found
> I've used this command a few times and it worked. I don't know what I
> am doing wrong now...
> Any idea what I am doing wrong?
>
> Did you add the path to the toolchain to your $PATH variable in the
> terminal ? (This might be a reason )
> Or rtems-test isn’t built for the bsp you are using try looking into
> rtems-testing repo
>
>
> On Sat, Apr 10, 2021 at 12:43 PM Eshan Dhawan 
> wrote:
>
>> Hi
>> You can use rtems-test to run tests in a directory
>> Eg :
>>
>> rtems-test --rtems-bsp=erc32-run --rtems-tools=$HOME/development/rtems/5 
>> ~/development/rtems/kernel/erc32/sparc-rtems5/c/erc32/testsuites/samples
>>
>> Thanks
>> Eshan
>>
>> On 10-Apr-2021, at 5:01 PM, Ida Delphine  wrote:
>>
>> 
>> Hello everyone,
>> I'm looking forward to work on automatic style checking and code
>> formatting for RTEMS as my GSoC project and will need to test that style
>> changes do not cause any implementation bugs. I will carryout this test by
>> running the full RTEMS testsuite. I've tried looking in the RTEMS
>> documentation for a detailed step by step guide on how to do this but I
>> can't find anything helpful. Can someone please guide me on how to achieve
>> this?
>>
>> Cheers,
>> Ida.
>> ___
>> 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello all,
I made some changes to my initial proposal draft based on some feedback I
got. Here's is the modified version. Please help me review and suggest
improvements.
https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing

Cheers,
Ida.

On Fri, Apr 9, 2021 at 1:51 AM Ida Delphine  wrote:

> Hello All,
>
> Just a gentle reminder to please help me review this my proposal draft and
> help me with ways to make it better :)
>
> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
>
> Cheers,
> Ida
>
> On Thu, 8 Apr 2021, 6:51 am Ida Delphine,  wrote:
>
>> Hello everyone,
>> Here is the link to my GSoC proposal. Will love if you leave comments on
>> ways I could make it better or any corrections (Especially the *Proposesd
>> Schedule* section so that I will be sure about my project deliverables
>> when inputting them).
>>
>> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
>> I will also love to know about any future improvements to this project.
>>
>> Cheers,
>> Ida.
>>
>> On Wed, Apr 7, 2021 at 5:27 PM Gedare Bloom  wrote:
>>
>>> On Wed, Apr 7, 2021 at 10:11 AM Ida Delphine  wrote:
>>> >
>>> > Hello,
>>> >
>>> > In case I succeed with this project will I be required to do some
>>> documentation on how it works?
>>> >
>>> Yes, in general we expect students to produce documentation while they
>>> work on also creating code.
>>>
>>> I think the direction we're heading right now is toward using
>>> clang-format, perhaps with an update to a common coding style. In this
>>> case, we solve our problem by policy rather than technical solution,
>>> and your work should focus on tool integration and automation without
>>> concern about the coding style itself.
>>>
>>> >
>>> > On Wed, Apr 7, 2021 at 9:51 AM Sebastian Huber <
>>> sebastian.hu...@embedded-brains.de> wrote:
>>> >>
>>> >> On 07/04/2021 09:03, Chris Johns wrote:
>>> >>
>>> >> > Would it be pragmatic to review these cases and change the standard?
>>> >>
>>> >> I sent a patch to review the format changes done by clang-format
>>> recently:
>>> >>
>>> >> https://lists.rtems.org/pipermail/devel/2021-April/066311.html
>>> >>
>>> >> It doesn't look that bad from my point of view. Fixing the alignment
>>> >> issue would make it even better:
>>> >>
>>> >> https://reviews.llvm.org/D27651
>>> >>
>>> >> >
>>> >> > I understand the long history but as you point out we either invest
>>> in the tools
>>> >> > to support the format, we change what we have or we manage it
>>> manually.
>>> >> I would prefer to change the style and use a widely used formatting
>>> >> tool. I think we spend to much time on the coding style in reviews.
>>> This
>>> >> is quite bad since we are all busy with all sorts of things and our
>>> time
>>> >> is better spent on more important tasks. A consistently formatted
>>> source
>>> >> code is very important, but enforcing this style manually is a waste
>>> of
>>> >> time.
>>> >>
>>> >> --
>>> >> embedded brains GmbH
>>> >> Herr Sebastian HUBER
>>> >> Dornierstr. 4
>>> >> 82178 Puchheim
>>> >> Germany
>>> >> email: sebastian.hu...@embedded-brains.de
>>> >> phone: +49-89-18 94 741 - 16
>>> >> fax:   +49-89-18 94 741 - 08
>>> >>
>>> >> Registergericht: Amtsgericht München
>>> >> Registernummer: HRB 157899
>>> >> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas
>>> Dörfler
>>> >> Unsere Datenschutzerklärung finden Sie hier:
>>> >> https://embedded-brains.de/datenschutzerklaerung/
>>> >>
>>> >> ___
>>> >> 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

Re: How to run the full RTEMS testsuite

[Ida Delphine]

For some reason I get this:
rtems-test: command not found
I've used this command a few times and it worked. I don't know what I
am doing wrong now...
Any idea what I am doing wrong?

On Sat, Apr 10, 2021 at 12:43 PM Eshan Dhawan 
wrote:

> Hi
> You can use rtems-test to run tests in a directory
> Eg :
>
> rtems-test --rtems-bsp=erc32-run --rtems-tools=$HOME/development/rtems/5 
> ~/development/rtems/kernel/erc32/sparc-rtems5/c/erc32/testsuites/samples
>
> Thanks
> Eshan
>
> On 10-Apr-2021, at 5:01 PM, Ida Delphine  wrote:
>
> 
> Hello everyone,
> I'm looking forward to work on automatic style checking and code
> formatting for RTEMS as my GSoC project and will need to test that style
> changes do not cause any implementation bugs. I will carryout this test by
> running the full RTEMS testsuite. I've tried looking in the RTEMS
> documentation for a detailed step by step guide on how to do this but I
> can't find anything helpful. Can someone please guide me on how to achieve
> this?
>
> Cheers,
> Ida.
> ___
> 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

How to run the full RTEMS testsuite

[Ida Delphine]

Hello everyone,
I'm looking forward to work on automatic style checking and code formatting
for RTEMS as my GSoC project and will need to test that style changes do
not cause any implementation bugs. I will carryout this test by running the
full RTEMS testsuite. I've tried looking in the RTEMS documentation for a
detailed step by step guide on how to do this but I can't find anything
helpful. Can someone please guide me on how to achieve this?

Cheers,
Ida.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello All,

Just a gentle reminder to please help me review this my proposal draft and
help me with ways to make it better :)
https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing

Cheers,
Ida

On Thu, 8 Apr 2021, 6:51 am Ida Delphine,  wrote:

> Hello everyone,
> Here is the link to my GSoC proposal. Will love if you leave comments on
> ways I could make it better or any corrections (Especially the *Proposesd
> Schedule* section so that I will be sure about my project deliverables
> when inputting them).
>
> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
> I will also love to know about any future improvements to this project.
>
> Cheers,
> Ida.
>
> On Wed, Apr 7, 2021 at 5:27 PM Gedare Bloom  wrote:
>
>> On Wed, Apr 7, 2021 at 10:11 AM Ida Delphine  wrote:
>> >
>> > Hello,
>> >
>> > In case I succeed with this project will I be required to do some
>> documentation on how it works?
>> >
>> Yes, in general we expect students to produce documentation while they
>> work on also creating code.
>>
>> I think the direction we're heading right now is toward using
>> clang-format, perhaps with an update to a common coding style. In this
>> case, we solve our problem by policy rather than technical solution,
>> and your work should focus on tool integration and automation without
>> concern about the coding style itself.
>>
>> >
>> > On Wed, Apr 7, 2021 at 9:51 AM Sebastian Huber <
>> sebastian.hu...@embedded-brains.de> wrote:
>> >>
>> >> On 07/04/2021 09:03, Chris Johns wrote:
>> >>
>> >> > Would it be pragmatic to review these cases and change the standard?
>> >>
>> >> I sent a patch to review the format changes done by clang-format
>> recently:
>> >>
>> >> https://lists.rtems.org/pipermail/devel/2021-April/066311.html
>> >>
>> >> It doesn't look that bad from my point of view. Fixing the alignment
>> >> issue would make it even better:
>> >>
>> >> https://reviews.llvm.org/D27651
>> >>
>> >> >
>> >> > I understand the long history but as you point out we either invest
>> in the tools
>> >> > to support the format, we change what we have or we manage it
>> manually.
>> >> I would prefer to change the style and use a widely used formatting
>> >> tool. I think we spend to much time on the coding style in reviews.
>> This
>> >> is quite bad since we are all busy with all sorts of things and our
>> time
>> >> is better spent on more important tasks. A consistently formatted
>> source
>> >> code is very important, but enforcing this style manually is a waste of
>> >> time.
>> >>
>> >> --
>> >> embedded brains GmbH
>> >> Herr Sebastian HUBER
>> >> Dornierstr. 4
>> >> 82178 Puchheim
>> >> Germany
>> >> email: sebastian.hu...@embedded-brains.de
>> >> phone: +49-89-18 94 741 - 16
>> >> fax:   +49-89-18 94 741 - 08
>> >>
>> >> Registergericht: Amtsgericht München
>> >> Registernummer: HRB 157899
>> >> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
>> >> Unsere Datenschutzerklärung finden Sie hier:
>> >> https://embedded-brains.de/datenschutzerklaerung/
>> >>
>> >> ___
>> >> 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

I just did.

On Thu, 8 Apr 2021, 7:11 am Gedare Bloom,  wrote:

> Please enable commenting
>
> On Wed, Apr 7, 2021 at 11:51 PM Ida Delphine  wrote:
> >
> > Hello everyone,
> > Here is the link to my GSoC proposal. Will love if you leave comments on
> ways I could make it better or any corrections (Especially the Proposesd
> Schedule section so that I will be sure about my project deliverables when
> inputting them).
> >
> https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
> > I will also love to know about any future improvements to this project.
> >
> > Cheers,
> > Ida.
> >
> > On Wed, Apr 7, 2021 at 5:27 PM Gedare Bloom  wrote:
> >>
> >> On Wed, Apr 7, 2021 at 10:11 AM Ida Delphine  wrote:
> >> >
> >> > Hello,
> >> >
> >> > In case I succeed with this project will I be required to do some
> documentation on how it works?
> >> >
> >> Yes, in general we expect students to produce documentation while they
> >> work on also creating code.
> >>
> >> I think the direction we're heading right now is toward using
> >> clang-format, perhaps with an update to a common coding style. In this
> >> case, we solve our problem by policy rather than technical solution,
> >> and your work should focus on tool integration and automation without
> >> concern about the coding style itself.
> >>
> >> >
> >> > On Wed, Apr 7, 2021 at 9:51 AM Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
> >> >>
> >> >> On 07/04/2021 09:03, Chris Johns wrote:
> >> >>
> >> >> > Would it be pragmatic to review these cases and change the
> standard?
> >> >>
> >> >> I sent a patch to review the format changes done by clang-format
> recently:
> >> >>
> >> >> https://lists.rtems.org/pipermail/devel/2021-April/066311.html
> >> >>
> >> >> It doesn't look that bad from my point of view. Fixing the alignment
> >> >> issue would make it even better:
> >> >>
> >> >> https://reviews.llvm.org/D27651
> >> >>
> >> >> >
> >> >> > I understand the long history but as you point out we either
> invest in the tools
> >> >> > to support the format, we change what we have or we manage it
> manually.
> >> >> I would prefer to change the style and use a widely used formatting
> >> >> tool. I think we spend to much time on the coding style in reviews.
> This
> >> >> is quite bad since we are all busy with all sorts of things and our
> time
> >> >> is better spent on more important tasks. A consistently formatted
> source
> >> >> code is very important, but enforcing this style manually is a waste
> of
> >> >> time.
> >> >>
> >> >> --
> >> >> embedded brains GmbH
> >> >> Herr Sebastian HUBER
> >> >> Dornierstr. 4
> >> >> 82178 Puchheim
> >> >> Germany
> >> >> email: sebastian.hu...@embedded-brains.de
> >> >> phone: +49-89-18 94 741 - 16
> >> >> fax:   +49-89-18 94 741 - 08
> >> >>
> >> >> Registergericht: Amtsgericht München
> >> >> Registernummer: HRB 157899
> >> >> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas
> Dörfler
> >> >> Unsere Datenschutzerklärung finden Sie hier:
> >> >> https://embedded-brains.de/datenschutzerklaerung/
> >> >>
> >> >> ___
> >> >> 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello everyone,
Here is the link to my GSoC proposal. Will love if you leave comments on
ways I could make it better or any corrections (Especially the *Proposesd
Schedule* section so that I will be sure about my project deliverables when
inputting them).
https://docs.google.com/document/d/1VADJh3_kIhs578IEmBJ98rjR6p5E1XcksUkq1Ms4jRA/edit?usp=sharing
I will also love to know about any future improvements to this project.

Cheers,
Ida.

On Wed, Apr 7, 2021 at 5:27 PM Gedare Bloom  wrote:

> On Wed, Apr 7, 2021 at 10:11 AM Ida Delphine  wrote:
> >
> > Hello,
> >
> > In case I succeed with this project will I be required to do some
> documentation on how it works?
> >
> Yes, in general we expect students to produce documentation while they
> work on also creating code.
>
> I think the direction we're heading right now is toward using
> clang-format, perhaps with an update to a common coding style. In this
> case, we solve our problem by policy rather than technical solution,
> and your work should focus on tool integration and automation without
> concern about the coding style itself.
>
> >
> > On Wed, Apr 7, 2021 at 9:51 AM Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
> >>
> >> On 07/04/2021 09:03, Chris Johns wrote:
> >>
> >> > Would it be pragmatic to review these cases and change the standard?
> >>
> >> I sent a patch to review the format changes done by clang-format
> recently:
> >>
> >> https://lists.rtems.org/pipermail/devel/2021-April/066311.html
> >>
> >> It doesn't look that bad from my point of view. Fixing the alignment
> >> issue would make it even better:
> >>
> >> https://reviews.llvm.org/D27651
> >>
> >> >
> >> > I understand the long history but as you point out we either invest
> in the tools
> >> > to support the format, we change what we have or we manage it
> manually.
> >> I would prefer to change the style and use a widely used formatting
> >> tool. I think we spend to much time on the coding style in reviews. This
> >> is quite bad since we are all busy with all sorts of things and our time
> >> is better spent on more important tasks. A consistently formatted source
> >> code is very important, but enforcing this style manually is a waste of
> >> time.
> >>
> >> --
> >> embedded brains GmbH
> >> Herr Sebastian HUBER
> >> Dornierstr. 4
> >> 82178 Puchheim
> >> Germany
> >> email: sebastian.hu...@embedded-brains.de
> >> phone: +49-89-18 94 741 - 16
> >> fax:   +49-89-18 94 741 - 08
> >>
> >> Registergericht: Amtsgericht München
> >> Registernummer: HRB 157899
> >> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> >> Unsere Datenschutzerklärung finden Sie hier:
> >> https://embedded-brains.de/datenschutzerklaerung/
> >>
> >> ___
> >> 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello,

In case I succeed with this project will I be required to do some
documentation on how it works?


On Wed, Apr 7, 2021 at 9:51 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 07/04/2021 09:03, Chris Johns wrote:
>
> > Would it be pragmatic to review these cases and change the standard?
>
> I sent a patch to review the format changes done by clang-format recently:
>
> https://lists.rtems.org/pipermail/devel/2021-April/066311.html
>
> It doesn't look that bad from my point of view. Fixing the alignment
> issue would make it even better:
>
> https://reviews.llvm.org/D27651
>
> >
> > I understand the long history but as you point out we either invest in
> the tools
> > to support the format, we change what we have or we manage it manually.
> I would prefer to change the style and use a widely used formatting
> tool. I think we spend to much time on the coding style in reviews. This
> is quite bad since we are all busy with all sorts of things and our time
> is better spent on more important tasks. A consistently formatted source
> code is very important, but enforcing this style manually is a waste of
> time.
>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.hu...@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
> ___
> 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

Does this mean I won't have to work with uncrustify anymore?

On Tue, 6 Apr 2021, 5:12 pm Gedare Bloom,  wrote:

> On Mon, Apr 5, 2021 at 10:37 PM Sebastian Huber
>  wrote:
> >
> > On 04/04/2021 22:18, Joel Sherrill wrote:
> >
> > >
> > >
> > > On Sun, Apr 4, 2021 at 2:25 PM Ida Delphine  > > <mailto:idad...@gmail.com>> wrote:
> > >
> > > Hello,
> > >
> > > Please who are the possible mentors for this project?
> > >
> > >
> > > IMO this is a project which has a larger potential potential set of
> > > mentors than
> > > one focused on say a single board.
> > >
> > >
> > > On Sun, 4 Apr 2021, 3:32 am Ida Delphine,  > > <mailto:idad...@gmail.com>> wrote:
> > >
> > > Regarding adding a script similar to linux/checkpatch.pl
> > > <http://checkpatch.pl> the criteria whether patches should
> > > need changes before being applied will be based on the output
> > > from running uncrustify right?
> > >
> > >
> > > Yes. Assuming we find a combination of uncrustify settings combined
> > > with changes to the RTEMS style and changes to uncrustify that put us
> > > in a place where we trust that the output wth the right settings
> > > matches our style.
> > >
> > > That is your goal. Find changes to the settlngs, uncrustify, and RTEMS
> > > code style where automated checking is possible. When you find a place
> > > where the coding style requires something uncrustify cannot currently
> > > do, the question is uncrustify changed or our coding style?
> > >
> > > Sebastian may have a list of some of those from his effort to create
> > > that configuration. But addressing the list of where the tooling and
> > > style guide do not align is a key part of your project.
> > I am not sure if tinkering code formatting tools to somehow produce the
> > RTEMS style is a suitable GSoC project. What has this to do with coding?
> > Also this task lingers around for years. Would it be a feasible task for
> > a student?
> >
> Setting the configuration is not a good task, but since we apparently
> can't find an out-of-the-box configuration, then there must be some
> coding that is required to make those style formatters able to support
> our style. (If not, then we should change our style later.)
>
> > --
> > embedded brains GmbH
> > Herr Sebastian HUBER
> > Dornierstr. 4
> > 82178 Puchheim
> > Germany
> > email: sebastian.hu...@embedded-brains.de
> > phone: +49-89-18 94 741 - 16
> > fax:   +49-89-18 94 741 - 08
> >
> > Registergericht: Amtsgericht München
> > Registernummer: HRB 157899
> > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> > Unsere Datenschutzerklärung finden Sie hier:
> > https://embedded-brains.de/datenschutzerklaerung/
> >
> > ___
> > 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello,

Please who are the possible mentors for this project?

On Sun, 4 Apr 2021, 3:32 am Ida Delphine,  wrote:

> Regarding adding a script similar to linux/checkpatch.pl the criteria
> whether patches should need changes before being applied will be based on
> the output from running uncrustify right?
>
> On Sat, Apr 3, 2021 at 2:32 AM Gedare Bloom  wrote:
>
>> On Fri, Apr 2, 2021 at 6:09 PM Joel Sherrill  wrote:
>> >
>> >
>> >
>> > On Fri, Apr 2, 2021, 6:59 PM Gedare Bloom  wrote:
>> >>
>> >> On Fri, Apr 2, 2021 at 4:48 PM Ida Delphine  wrote:
>> >> >
>> >> > Hello,
>> >> > Please can you help explain what you mean by Adding a "check-style"
>> target to the RTEMS build system?
>> >> > And how I could possibly go about this?
>> >> >
>> >> I don't know if this makes sense exactly to me.  When compiling RTEMS
>> >> it could be nice to have an option to check the style rules for
>> >> compliance. This would be something to integrate in the
>> >> rtems.git/wscript file most likely, as part of the waf build system.
>> >> However, since checking style does not generate a target file, I don't
>> >> know that this really is suitable as a way to verify style rules. It
>> >> may be suitable to add a standalone script in rtems-tools.git that can
>> >> be run over the rtems.git that creates a report about style problems.
>> >> Maybe, a way to configure it to ignore some files or to add exceptions
>> >> to the style rules for certain cases then could be possible.
>> >
>> >
>> > If you have a configuration that produces the code formatted as
>> expected in certain directories, then if a change is made as part of normal
>> development, running uncrustify will result in changes to the file needed.
>> In a way the goal is to have a directory full of files that an RTEMS
>> uncrustify configuration does not change.
>> >
>> > If you have a script that can do that manually then we can easily add
>> an automated check somewhere in the process to ensure that directories that
>> adhere to the style rules continue to adhere to them.
>> >
>> > One thing to keep in mind is that there there are places where
>> uncrustify does not have the ability to format code the way RTEMS has
>> historically done it. we want the rules to be as close as possible to the
>> existing practice but we are willing to adjust practice if it allows the
>> tool to produce formatted output we can trust.
>> >
>> Also on the table could be modifications to uncrustify.
>>
>> > On each point where this type of issue occurs, we'll have to have a
>> discussion about our Style versus what tool supports. It's likely indicates
>> we're doing something that's not common in the open source world.
>> >
>> > Once the delta between the output of uncrustify and the committed
>> source is zero, running uncrustify should produce no changes. Anything
>> uncrustify wants to change at that point would be a style violation and
>> flagged. In a perfect world it would prevent you from committing.
>> >
>> >>
>> >>
>> >> I think focus on 1 and 3 is better as a way to start, and perhaps
>> >> something like the above can be the phase 2 effort.
>> >>
>> >> Gedare
>> >>
>> >> > Cheers,
>> >> > Ida
>> >> >
>> >> > On Mon, Mar 29, 2021 at 9:45 PM Gedare Bloom 
>> wrote:
>> >> >>
>> >> >> On Mon, Mar 29, 2021 at 1:28 PM Ida Delphine 
>> wrote:
>> >> >> >
>> >> >> > Yes I have. But wondering how to run it with the given
>> configuration I saw in this thread(
>> https://lists.rtems.org/pipermail/devel/2020-October/062770.html).
>> >> >> >
>> >> >>
>> >> >> If you download/copy the configuration into a cfg file, then you can
>> >> >> use the examples from
>> >> >> https://github.com/uncrustify/uncrustify#running-the-program and
>> >> >> attempt to run it on some files within rtems.git/cpukit/score/src
>> >> >> would be my suggestion.
>> >> >>
>> >> >> > On Mon, Mar 29, 2021 at 3:37 PM Gedare Bloom 
>> wrote:
>> >> >> >>
>> >> >> >> Hi Ida,
>> >> >> >>
>> >> >> >> On Mon, Mar 29, 2021 

Re: #3860 - GSoC enquiries

[Ida Delphine]

Regarding adding a script similar to linux/checkpatch.pl the criteria
whether patches should need changes before being applied will be based on
the output from running uncrustify right?

On Sat, Apr 3, 2021 at 2:32 AM Gedare Bloom  wrote:

> On Fri, Apr 2, 2021 at 6:09 PM Joel Sherrill  wrote:
> >
> >
> >
> > On Fri, Apr 2, 2021, 6:59 PM Gedare Bloom  wrote:
> >>
> >> On Fri, Apr 2, 2021 at 4:48 PM Ida Delphine  wrote:
> >> >
> >> > Hello,
> >> > Please can you help explain what you mean by Adding a "check-style"
> target to the RTEMS build system?
> >> > And how I could possibly go about this?
> >> >
> >> I don't know if this makes sense exactly to me.  When compiling RTEMS
> >> it could be nice to have an option to check the style rules for
> >> compliance. This would be something to integrate in the
> >> rtems.git/wscript file most likely, as part of the waf build system.
> >> However, since checking style does not generate a target file, I don't
> >> know that this really is suitable as a way to verify style rules. It
> >> may be suitable to add a standalone script in rtems-tools.git that can
> >> be run over the rtems.git that creates a report about style problems.
> >> Maybe, a way to configure it to ignore some files or to add exceptions
> >> to the style rules for certain cases then could be possible.
> >
> >
> > If you have a configuration that produces the code formatted as expected
> in certain directories, then if a change is made as part of normal
> development, running uncrustify will result in changes to the file needed.
> In a way the goal is to have a directory full of files that an RTEMS
> uncrustify configuration does not change.
> >
> > If you have a script that can do that manually then we can easily add an
> automated check somewhere in the process to ensure that directories that
> adhere to the style rules continue to adhere to them.
> >
> > One thing to keep in mind is that there there are places where
> uncrustify does not have the ability to format code the way RTEMS has
> historically done it. we want the rules to be as close as possible to the
> existing practice but we are willing to adjust practice if it allows the
> tool to produce formatted output we can trust.
> >
> Also on the table could be modifications to uncrustify.
>
> > On each point where this type of issue occurs, we'll have to have a
> discussion about our Style versus what tool supports. It's likely indicates
> we're doing something that's not common in the open source world.
> >
> > Once the delta between the output of uncrustify and the committed source
> is zero, running uncrustify should produce no changes. Anything uncrustify
> wants to change at that point would be a style violation and flagged. In a
> perfect world it would prevent you from committing.
> >
> >>
> >>
> >> I think focus on 1 and 3 is better as a way to start, and perhaps
> >> something like the above can be the phase 2 effort.
> >>
> >> Gedare
> >>
> >> > Cheers,
> >> > Ida
> >> >
> >> > On Mon, Mar 29, 2021 at 9:45 PM Gedare Bloom 
> wrote:
> >> >>
> >> >> On Mon, Mar 29, 2021 at 1:28 PM Ida Delphine 
> wrote:
> >> >> >
> >> >> > Yes I have. But wondering how to run it with the given
> configuration I saw in this thread(
> https://lists.rtems.org/pipermail/devel/2020-October/062770.html).
> >> >> >
> >> >>
> >> >> If you download/copy the configuration into a cfg file, then you can
> >> >> use the examples from
> >> >> https://github.com/uncrustify/uncrustify#running-the-program and
> >> >> attempt to run it on some files within rtems.git/cpukit/score/src
> >> >> would be my suggestion.
> >> >>
> >> >> > On Mon, Mar 29, 2021 at 3:37 PM Gedare Bloom 
> wrote:
> >> >> >>
> >> >> >> Hi Ida,
> >> >> >>
> >> >> >> On Mon, Mar 29, 2021 at 7:36 AM Ida Delphine 
> wrote:
> >> >> >> >
> >> >> >> > Hello,
> >> >> >> > Please do you mind telling me how to run uncrustify with the
> given configuration with any sample file?
> >> >> >>
> >> >> >> What have you tried? Any directions followed/attempted or notes
> that
> >> >> >> yo

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello,
Please can you help explain what you mean by *Adding a "check-style" target
to the RTEMS build system*?
And how I could possibly go about this?

Cheers,
Ida

On Mon, Mar 29, 2021 at 9:45 PM Gedare Bloom  wrote:

> On Mon, Mar 29, 2021 at 1:28 PM Ida Delphine  wrote:
> >
> > Yes I have. But wondering how to run it with the given configuration I
> saw in this thread(
> https://lists.rtems.org/pipermail/devel/2020-October/062770.html).
> >
>
> If you download/copy the configuration into a cfg file, then you can
> use the examples from
> https://github.com/uncrustify/uncrustify#running-the-program and
> attempt to run it on some files within rtems.git/cpukit/score/src
> would be my suggestion.
>
> > On Mon, Mar 29, 2021 at 3:37 PM Gedare Bloom  wrote:
> >>
> >> Hi Ida,
> >>
> >> On Mon, Mar 29, 2021 at 7:36 AM Ida Delphine  wrote:
> >> >
> >> > Hello,
> >> > Please do you mind telling me how to run uncrustify with the given
> configuration with any sample file?
> >>
> >> What have you tried? Any directions followed/attempted or notes that
> >> you have taken would be helpful.
> >>
> >> I guess all the info that you should need is in Uncrustify's readme
> >> file. https://github.com/uncrustify/uncrustify
> >>
> >> Did you successfully compile uncrustify tool?
> >>
> >> > I'm a bit stuck.
> >> >
> >> > Thanks,
> >> > Ida.
> >> >
> >> > On Wed, Mar 17, 2021 at 10:34 PM Gedare Bloom 
> wrote:
> >> >>
> >> >> On Wed, Mar 17, 2021 at 2:28 PM Ida Delphine 
> wrote:
> >> >> >
> >> >> > Hello,
> >> >> > So I have gone through this configuration file and I think I'm
> getting it. However I'm a bit lost in the reading the messages in the
> thread. Do you mind explaining? Or we can start talking about a way forward.
> >> >> > Also can you help me with some steps on how to test this by myself
> if possible?
> >> >> >
> >> >>
> >> >> It may be easier if you go "up" a level to see the full thread
> >> >> context:
> https://lists.rtems.org/pipermail/devel/2020-October/thread.html#62769
> >> >> Then you can go through the messages non-linearly. Right now, the
> >> >> basic idea is to follow the steps outlined in the open project
> ticket.
> >> >> I think Christian has summarized it nicely in his recent email [1]:
> "I
> >> >> think the contributions from this project that would add value would
> >> >> be:
> >> >> 1. Finding a tool and a configuration that can do an RTEMS style or
> an
> >> >> acceptable close one.
> >> >> 2. Adding a "check-style" target to our build system.
> >> >> 3. Maybe add some kind of script similar to Linux "checkpatch.pl"
> that
> >> >> could check whether patches would need changes _before_ they are
> >> >> applied.
> >> >> "
> >> >>
> >> >> The proposal preparation phase should work through identifying the
> >> >> options and pros/cons for different tools while preparing a plan for
> >> >> how to integrate style checks in 2, 3 and thinking through the coding
> >> >> tasks for the summer.
> >> >>
> >> >> Getting the style checking tool's configuration to match with the
> >> >> RTEMS style will be some effort, and testing it out and submitting
> >> >> some patches based on it could be a good proposal activity also to
> >> >> build some confidence about the tools that will be used.
> >> >>
> >> >> We also have some Python style guidelines that might be worth
> >> >> addressing. Those are harder maybe, since the style refactoring might
> >> >> be challenging to review for correctness.
> >> >>
> >> >> For getting started, I would recommend that you try running
> uncrustify
> >> >> with the given configuration on some files in RTEMS, see what it
> >> >> results in. Play around.
> >> >>
> >> >> [1] https://lists.rtems.org/pipermail/devel/2021-March/065547.html
> >> >>
> >> >> -Gedare
> >> >>
> >> >> > Thanks,
> >> >> > Ida
> >> >> >
> >> >> > On Mon, Mar 15, 2021 at 9:39 PM Gedare Bloom 
> 

Re: #3860 - GSoC enquiries

[Ida Delphine]

Yes I have. But wondering how to run it with the given configuration I saw
in this thread(
https://lists.rtems.org/pipermail/devel/2020-October/062770.html).

On Mon, Mar 29, 2021 at 3:37 PM Gedare Bloom  wrote:

> Hi Ida,
>
> On Mon, Mar 29, 2021 at 7:36 AM Ida Delphine  wrote:
> >
> > Hello,
> > Please do you mind telling me how to run uncrustify with the given
> configuration with any sample file?
>
> What have you tried? Any directions followed/attempted or notes that
> you have taken would be helpful.
>
> I guess all the info that you should need is in Uncrustify's readme
> file. https://github.com/uncrustify/uncrustify
>
> Did you successfully compile uncrustify tool?
>
> > I'm a bit stuck.
> >
> > Thanks,
> > Ida.
> >
> > On Wed, Mar 17, 2021 at 10:34 PM Gedare Bloom  wrote:
> >>
> >> On Wed, Mar 17, 2021 at 2:28 PM Ida Delphine  wrote:
> >> >
> >> > Hello,
> >> > So I have gone through this configuration file and I think I'm
> getting it. However I'm a bit lost in the reading the messages in the
> thread. Do you mind explaining? Or we can start talking about a way forward.
> >> > Also can you help me with some steps on how to test this by myself if
> possible?
> >> >
> >>
> >> It may be easier if you go "up" a level to see the full thread
> >> context:
> https://lists.rtems.org/pipermail/devel/2020-October/thread.html#62769
> >> Then you can go through the messages non-linearly. Right now, the
> >> basic idea is to follow the steps outlined in the open project ticket.
> >> I think Christian has summarized it nicely in his recent email [1]: "I
> >> think the contributions from this project that would add value would
> >> be:
> >> 1. Finding a tool and a configuration that can do an RTEMS style or an
> >> acceptable close one.
> >> 2. Adding a "check-style" target to our build system.
> >> 3. Maybe add some kind of script similar to Linux "checkpatch.pl" that
> >> could check whether patches would need changes _before_ they are
> >> applied.
> >> "
> >>
> >> The proposal preparation phase should work through identifying the
> >> options and pros/cons for different tools while preparing a plan for
> >> how to integrate style checks in 2, 3 and thinking through the coding
> >> tasks for the summer.
> >>
> >> Getting the style checking tool's configuration to match with the
> >> RTEMS style will be some effort, and testing it out and submitting
> >> some patches based on it could be a good proposal activity also to
> >> build some confidence about the tools that will be used.
> >>
> >> We also have some Python style guidelines that might be worth
> >> addressing. Those are harder maybe, since the style refactoring might
> >> be challenging to review for correctness.
> >>
> >> For getting started, I would recommend that you try running uncrustify
> >> with the given configuration on some files in RTEMS, see what it
> >> results in. Play around.
> >>
> >> [1] https://lists.rtems.org/pipermail/devel/2021-March/065547.html
> >>
> >> -Gedare
> >>
> >> > Thanks,
> >> > Ida
> >> >
> >> > On Mon, Mar 15, 2021 at 9:39 PM Gedare Bloom 
> wrote:
> >> >>
> >> >> See the related thread, and we'll have to discuss how to move
> forward.
> >> >> The existing approach provides an uncrustify script:
> >> >> https://lists.rtems.org/pipermail/devel/2020-October/062769.html
> >> >>
> >> >>
> >> >> On Sun, Mar 14, 2021 at 9:47 PM Ida Delphine 
> wrote:
> >> >> >
> >> >> > Hello everyone,
> >> >> > This ticket(https://devel.rtems.org/ticket/3860) was proposed to
> me and I'm interested in it for GSoC.
> >> >> > The first task there is to find a code checker or formater that
> can produce results that match the RTEMS coding conventions. It also made
> mention some tools have been discussed in the past. Please I will love
> suggestions on possible tools I could use to achieve this.
> >> >> >
> >> >> >
> >> >> > Cheers,
> >> >> > Ida.
> >> >> > ___
> >> >> > 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

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello,
Please do you mind telling me how to run uncrustify with the given
configuration with any sample file?
I'm a bit stuck.

Thanks,
Ida.

On Wed, Mar 17, 2021 at 10:34 PM Gedare Bloom  wrote:

> On Wed, Mar 17, 2021 at 2:28 PM Ida Delphine  wrote:
> >
> > Hello,
> > So I have gone through this configuration file and I think I'm getting
> it. However I'm a bit lost in the reading the messages in the thread. Do
> you mind explaining? Or we can start talking about a way forward.
> > Also can you help me with some steps on how to test this by myself if
> possible?
> >
>
> It may be easier if you go "up" a level to see the full thread
> context:
> https://lists.rtems.org/pipermail/devel/2020-October/thread.html#62769
> Then you can go through the messages non-linearly. Right now, the
> basic idea is to follow the steps outlined in the open project ticket.
> I think Christian has summarized it nicely in his recent email [1]: "I
> think the contributions from this project that would add value would
> be:
> 1. Finding a tool and a configuration that can do an RTEMS style or an
> acceptable close one.
> 2. Adding a "check-style" target to our build system.
> 3. Maybe add some kind of script similar to Linux "checkpatch.pl" that
> could check whether patches would need changes _before_ they are
> applied.
> "
>
> The proposal preparation phase should work through identifying the
> options and pros/cons for different tools while preparing a plan for
> how to integrate style checks in 2, 3 and thinking through the coding
> tasks for the summer.
>
> Getting the style checking tool's configuration to match with the
> RTEMS style will be some effort, and testing it out and submitting
> some patches based on it could be a good proposal activity also to
> build some confidence about the tools that will be used.
>
> We also have some Python style guidelines that might be worth
> addressing. Those are harder maybe, since the style refactoring might
> be challenging to review for correctness.
>
> For getting started, I would recommend that you try running uncrustify
> with the given configuration on some files in RTEMS, see what it
> results in. Play around.
>
> [1] https://lists.rtems.org/pipermail/devel/2021-March/065547.html
>
> -Gedare
>
> > Thanks,
> > Ida
> >
> > On Mon, Mar 15, 2021 at 9:39 PM Gedare Bloom  wrote:
> >>
> >> See the related thread, and we'll have to discuss how to move forward.
> >> The existing approach provides an uncrustify script:
> >> https://lists.rtems.org/pipermail/devel/2020-October/062769.html
> >>
> >>
> >> On Sun, Mar 14, 2021 at 9:47 PM Ida Delphine  wrote:
> >> >
> >> > Hello everyone,
> >> > This ticket(https://devel.rtems.org/ticket/3860) was proposed to me
> and I'm interested in it for GSoC.
> >> > The first task there is to find a code checker or formater that can
> produce results that match the RTEMS coding conventions. It also made
> mention some tools have been discussed in the past. Please I will love
> suggestions on possible tools I could use to achieve this.
> >> >
> >> >
> >> > Cheers,
> >> > Ida.
> >> > ___
> >> > 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

Re: [PATCH rtems-docs v3 4/6] bsp-build: Update manual bsp build command

[Ida Delphine]

Regarding this patch I focused just on the Manual BSP build section.

On Sat, 20 Mar 2021, 7:55 pm Ida Delphine,  wrote:

> ---
>  user/start/bsp-build.rst | 10 +-
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/user/start/bsp-build.rst b/user/start/bsp-build.rst
> index 137b3ab..335962b 100644
> --- a/user/start/bsp-build.rst
> +++ b/user/start/bsp-build.rst
> @@ -11,7 +11,7 @@ Build a Board Support Package (BSP)
>  You installed the tool suite in your installation prefix, made ready the
> source
>  for two RTEMS source packages and if you are using a Git clone
> bootstrapped the
>  RTEMS sources in the previous sections.  We installed the tool suite in
> -:file:`$HOME/quick-start/rtems/5` and unpacked the source in
> +:file:`$HOME/quick-start/rtems/6` and unpacked the source in
>  :file:`$HOME/quick-start/src`.
>
>  You are now able to build :ref:`Board Support Packages (BSPs) ` for
> all
> @@ -112,13 +112,13 @@ directory to your ``$PATH`` throughout the remaining
> steps. Run the command:
>
>  .. code-block:: none
>
> -export PATH=$HOME/quick-start/rtems/5/bin:"$PATH"
> +export PATH=$HOME/quick-start/rtems/6/bin:"$PATH"
>
>  Check your installed tools can be found by running:
>
>  .. code-block:: none
>
> -command -v sparc-rtems5-gcc && echo "found" || echo "not found"
> +command -v sparc-rtems6-gcc && echo "found" || echo "not found"
>
>  The output should be:
>
> @@ -128,7 +128,7 @@ The output should be:
>
>  If ``not found`` is printed the tools are not correctly installed or the
> path
>  has not been correctly set. Check the contents of the path
> -:file:`$HOME/quick-start/rtems/5/bin` manually and if
> :file:`sparc-rtems5-gcc`
> +:file:`$HOME/quick-start/rtems/6/bin` manually and if
> :file:`sparc-rtems6-gcc`
>  is present the path is wrong. If the file cannot be found return to
>  :ref:`QuickStartTools` and install the tools again.
>
> @@ -145,7 +145,7 @@ everything else.  For detailed information about the
> BSP build system, see
>  cd $HOME/quick-start/src/rtems
>  echo "[sparc/erc32]" > config.ini
>  echo "BUILD_TESTS = True" >> config.ini
> -./waf configure --prefix=$HOME/quick-start/rtems/5
> +./waf configure --prefix=$HOME/quick-start/rtems/6
>
>  The first invocation of ``./waf`` needs a bit of time (e.g. 10 seconds)
> since an
>  internal cache file is populated.  This command should output something
> like
> --
> 2.25.1
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v3 6/6] start: Console output example updates

[Ida Delphine]

---
 user/start/app.rst   | 119 +++
 user/start/bsp-build.rst |  93 +++---
 user/start/bsp-test.rst  |  50 
 user/start/sources.rst   |  12 ++--
 user/start/tools.rst |  35 ++--
 5 files changed, 159 insertions(+), 150 deletions(-)

diff --git a/user/start/app.rst b/user/start/app.rst
index b04f8e1..2bb0a9e 100644
--- a/user/start/app.rst
+++ b/user/start/app.rst
@@ -148,47 +148,46 @@ The output will be something close to:
 
 .. code-block:: none
 
- Setting top to   : $BASE/app/hello
- Setting out to   : $BASE/app/hello/build
- RTEMS Version: 5
- Architectures: sparc-rtems5
- Board Support Package (BSP)  : sparc-rtems5-erc32
- Show commands: no
- Long commands: no
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
- Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'sparc-rtems5-nm'   : 
$BASE/rtems/5/bin/sparc-rtems5-nm
- Checking for program 'sparc-rtems5-objdump' : 
$BASE/rtems/5/bin/sparc-rtems5-objdump
- Checking for program 'sparc-rtems5-objcopy' : 
$BASE/rtems/5/bin/sparc-rtems5-objcopy
- Checking for program 'sparc-rtems5-readelf' : 
$BASE/rtems/5/bin/sparc-rtems5-readelf
- Checking for program 'sparc-rtems5-strip'   : 
$BASE/rtems/5/bin/sparc-rtems5-strip
- Checking for program 'sparc-rtems5-ranlib'  : 
$BASE/rtems/5/bin/sparc-rtems5-ranlib
- Checking for program 'rtems-ld' : $BASE/rtems/5/bin/rtems-ld
- Checking for program 'rtems-tld': $BASE/rtems/5/bin/rtems-tld
- Checking for program 'rtems-syms'   : $BASE/rtems/5/bin/rtems-syms
- Checking for program 'rtems-bin2c'  : 
$BASE/rtems/5/bin/rtems-bin2c
- Checking for program 'tar'  : /usr/bin/tar
- Checking for program 'gcc, cc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'g++, c++' : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'gas, gcc' : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for c flags '-MMD' : yes
- Checking for cxx flags '-MMD'   : yes
- Compiler version (sparc-rtems5-gcc) : 7.5.0 20191114 (RTEMS 5, 
RSB 5.1.0, Newlib fbaa096)
- Checking for a valid RTEMS BSP installation : yes
- Checking for RTEMS_DEBUG: no
- Checking for RTEMS_MULTIPROCESSING  : no
- Checking for RTEMS_NEWLIB   : yes
- Checking for RTEMS_POSIX_API: yes
- Checking for RTEMS_SMP  : no
- Checking for RTEMS_NETWORKING   : no
- 'configure' finished successfully (0.686s)
-
+ Setting top to   : $BASE/app/hello 
+ Setting out to   : $BASE/app/hello/build 
+ RTEMS Version: 6 
+ Architectures: sparc-rtems6 
+ Board Support Package (BSP)  : sparc-rtems6-erc32 
+ Show commands: no 
+ Long commands: no 
+ Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+ Checking for program 'sparc-rtems6-g++'  : 
$BASE/rtems/6/bin/sparc-rtems6-g++ 
+ Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+ Checking for program 'sparc-rtems6-ld'   : 
$BASE/rtems/6/bin/sparc-rtems6-ld 
+ Checking for program 'sparc-rtems6-ar'   : 
$BASE/rtems/6/bin/sparc-rtems6-ar 
+ Checking for program 'sparc-rtems6-nm'   : 
$BASE/rtems/6/bin/sparc-rtems6-nm 
+ Checking for program 'sparc-rtems6-objdump' : 
$BASE/rtems/6/bin/sparc-rtems6-objdump 
+ Checking for program 'sparc-rtems6-objcopy' : 
$BASE/rtems/6/bin/sparc-rtems6-objcopy 
+ Checking for program 'sparc-rtems6-readelf' : 
$BASE/rtems/6/bin/sparc-rtems6-readelf 
+ Checking for program 'sparc-rtems6-strip'   : 
$BASE/rtems/6/bin/sparc-rtems6-strip 
+ Checking for program 'sparc-rtems6-ranlib'  : 
$BASE/rtems/6/bin/sparc-rtems6-ranlib 
+ Checking for program 'rtems-ld' : $BASE/rtems/6/bin/rtems-ld 
+ Checking 

[PATCH rtems-docs v3 2/6] sourses: Update source download command

[Ida Delphine]

---
 user/start/sources.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/user/start/sources.rst b/user/start/sources.rst
index 8c40aa0..669505d 100644
--- a/user/start/sources.rst
+++ b/user/start/sources.rst
@@ -10,7 +10,7 @@ Obtain the Sources
 ==
 
 You have considered and chosen a suitable installation prefix in the previous
-section.  We have chosen :file:`$HOME/quick-start/rtems/5` as the installation
+section.  We have chosen :file:`$HOME/quick-start/rtems/6` as the installation
 prefix. We will show how to use a released version of RTEMS and then as an
 alternative we will show you using the :ref:`RSB Git repository
 `. Consider using a Git clone if you wish to make
@@ -114,7 +114,7 @@ the sources to build the ERC 32 BSP before building run the 
following commands:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
+../source-builder/sb-set-builder --source-only-download 6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ``...``):
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v3 5/6] app: Update command to configure app

[Ida Delphine]

---
 user/start/app.rst | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/user/start/app.rst b/user/start/app.rst
index 8900f78..b04f8e1 100644
--- a/user/start/app.rst
+++ b/user/start/app.rst
@@ -8,7 +8,7 @@ Build Your Application
 ==
 
 You tested a BSP in the previous section.  We built the ``erc32`` BSP
-and it is installed under :file:`$HOME/quick-start/rtems/5`.
+and it is installed under :file:`$HOME/quick-start/rtems/6`.
 
 We will now create a simple Hello World application with a Git
 repository and using the `Waf `_ build system.
@@ -107,7 +107,7 @@ and copy the Waf script:
 #
 from __future__ import print_function
 
-rtems_version = "5"
+rtems_version = "6"
 
 try:
 import rtems_waf.rtems as rtems
@@ -142,7 +142,7 @@ Configure the application using Waf's ``configure`` command:
 
 .. code-block:: none
 
-./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
+./waf configure --rtems=$HOME/quick-start/rtems/6 --rtems-bsp=sparc/erc32
 
 The output will be something close to:
 
@@ -210,7 +210,7 @@ Run the executable:
 
 .. code-block:: none
 
-$HOME/quick-start/rtems/5/bin/rtems-run --rtems-bsps=erc32-sis 
build/sparc-rtems5-erc32/hello.exe
+$HOME/quick-start/rtems/6/bin/rtems-run --rtems-bsps=erc32-sis 
build/sparc-rtems6-erc32/hello.exe
 
 The output will be something close to:
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v3 1/6] prefixes: Update installation prefix

[Ida Delphine]

---
 user/start/prefixes.rst | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/user/start/prefixes.rst b/user/start/prefixes.rst
index 67255d0..826ce85 100644
--- a/user/start/prefixes.rst
+++ b/user/start/prefixes.rst
@@ -40,7 +40,7 @@ applications and systems.
 You build and install the tool suite with the :ref:`RTEMS Source Builder (RSB)
 `.  By default, the RSB will start the prefix path with a host operating
 system specific path plus :file:`rtems`, and the RTEMS version, e.g.
-:file:`/opt/rtems/5` on Linux, and :file:`/usr/local/rtems/5` on FreeBSD and
+:file:`/opt/rtems/6` on Linux, and :file:`/usr/local/rtems/6` on FreeBSD and
 macOS. Placing the RTEMS version number in the path lets you manage and
 migrate RTEMS versions as they are released.
 
@@ -50,10 +50,10 @@ make sure that your normal user has sufficient privileges 
to create files and
 directories under the prefix.  For example, you can create a directory
 :file:`/opt/rtems` and give it to a developer group with read, write, and
 execute permissions.  Alternatively, you can choose a prefix in your home
-directory, e.g. :file:`$HOME/rtems/5` or with a project-specific component
-:file:`$HOME/project-x/rtems/5`.  For more ideas, see the :ref:`project
+directory, e.g. :file:`$HOME/rtems/6` or with a project-specific component
+:file:`$HOME/project-x/rtems/6`.  For more ideas, see the :ref:`project
 sandboxing ` section.  In this quick start chapter, we will
-choose :file:`$HOME/quick-start/rtems/5` for the RTEMS tool suite prefix.
+choose :file:`$HOME/quick-start/rtems/6` for the RTEMS tool suite prefix.
 
 .. warning::
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v3 4/6] bsp-build: Update manual bsp build command

[Ida Delphine]

---
 user/start/bsp-build.rst | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/user/start/bsp-build.rst b/user/start/bsp-build.rst
index 137b3ab..335962b 100644
--- a/user/start/bsp-build.rst
+++ b/user/start/bsp-build.rst
@@ -11,7 +11,7 @@ Build a Board Support Package (BSP)
 You installed the tool suite in your installation prefix, made ready the source
 for two RTEMS source packages and if you are using a Git clone bootstrapped the
 RTEMS sources in the previous sections.  We installed the tool suite in
-:file:`$HOME/quick-start/rtems/5` and unpacked the source in
+:file:`$HOME/quick-start/rtems/6` and unpacked the source in
 :file:`$HOME/quick-start/src`.
 
 You are now able to build :ref:`Board Support Packages (BSPs) ` for all
@@ -112,13 +112,13 @@ directory to your ``$PATH`` throughout the remaining 
steps. Run the command:
 
 .. code-block:: none
 
-export PATH=$HOME/quick-start/rtems/5/bin:"$PATH"
+export PATH=$HOME/quick-start/rtems/6/bin:"$PATH"
 
 Check your installed tools can be found by running:
 
 .. code-block:: none
 
-command -v sparc-rtems5-gcc && echo "found" || echo "not found"
+command -v sparc-rtems6-gcc && echo "found" || echo "not found"
 
 The output should be:
 
@@ -128,7 +128,7 @@ The output should be:
 
 If ``not found`` is printed the tools are not correctly installed or the path
 has not been correctly set. Check the contents of the path
-:file:`$HOME/quick-start/rtems/5/bin` manually and if :file:`sparc-rtems5-gcc`
+:file:`$HOME/quick-start/rtems/6/bin` manually and if :file:`sparc-rtems6-gcc`
 is present the path is wrong. If the file cannot be found return to
 :ref:`QuickStartTools` and install the tools again.
 
@@ -145,7 +145,7 @@ everything else.  For detailed information about the BSP 
build system, see
 cd $HOME/quick-start/src/rtems
 echo "[sparc/erc32]" > config.ini
 echo "BUILD_TESTS = True" >> config.ini
-./waf configure --prefix=$HOME/quick-start/rtems/5
+./waf configure --prefix=$HOME/quick-start/rtems/6
 
 The first invocation of ``./waf`` needs a bit of time (e.g. 10 seconds) since 
an
 internal cache file is populated.  This command should output something like
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v3 3/6] tools: Update command to install toolsuite

[Ida Delphine]

---
 user/start/tools.rst | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/user/start/tools.rst b/user/start/tools.rst
index baa2387..6c5aa83 100644
--- a/user/start/tools.rst
+++ b/user/start/tools.rst
@@ -12,12 +12,12 @@ Install the Tool Suite
 
 You have chosen an installation prefix, the BSP to build, the tool's
 architecure and prepared the source for the RSB in the previous sections.  We
-have chosen :file:`$HOME/quick-start/rtems/5` as the installation prefix, the
-``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``, and unpacked
+have chosen :file:`$HOME/quick-start/rtems/6` as the installation prefix, the
+``erc32`` BSP and the SPARC architecture name of ``sparc-rtems6``, and unpacked
 the RSB source in :file:`$HOME/quick-start/src`.
 
 The tool suite for RTEMS and the RTEMS sources are tightly coupled.  For
-example, do not use a RTEMS version 5 tool suite with RTEMS version 4.11
+example, do not use a RTEMS version 6 tool suite with RTEMS version 4.11 or 5
 sources and vice versa.
 
 Build and install the tool suite:
@@ -25,7 +25,7 @@ Build and install the tool suite:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 
5/rtems-sparc
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 
6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ...). The build host appears as part of the name of the package being
@@ -55,7 +55,7 @@ works with the following command:
 
 .. code-block:: none
 
-$HOME/quick-start/rtems/5/bin/sparc-rtems5-gcc --version
+$HOME/quick-start/rtems/6/bin/sparc-rtems6-gcc --version
 
 This command should output something like below.  The version informtion helps
 you to identify the exact sources used to build the cross compiler of your
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-docs v2 3/6] rtems-docs: Edit command to install toolsuite

[Ida Delphine]

Hi Vijay,

Will send a v3 soon

On Sat, 20 Mar 2021, 7:07 am Gedare Bloom,  wrote:

> Hi Ida,
>
> On Wed, Mar 17, 2021 at 11:36 PM Gedare Bloom  wrote:
> >
> > On Wed, Mar 17, 2021 at 9:04 PM Vijay Kumar Banerjee 
> wrote:
> > >
> > > Hello Ida,
> > >
> > >
> > > On Wed, Mar 17, 2021 at 8:42 PM Ida Delphine 
> wrote:
> > > >
> > > > I just installed texlive and trying to do a top level build using
> ./waf configure. But looks like it doesn't work well...I get this error at
> the end:
> > > > Setting top to   :
> /home/idadel/Desktop/gsoc/docs/rtems-docs
> > > > Setting out to   :
> /home/idadel/Desktop/gsoc/docs/rtems-docs/build
> > > > Checking for program 'git'   : /usr/bin/git
> > > > Checking for program 'sphinx-build'  :
> /home/idadel/anaconda3/bin/sphinx-build
> > > > Checking for program 'aspell': /usr/bin/aspell
> > > > Checking if Sphinx is at least 1.3   : yes (3.5)
> > > > Checking Sphinx Options  : none
> > > > Checking Sphinx Nit-Pick mode: no
> > > > Checking for 'sphinx.ext.autodoc': found
> > > > Checking for 'sphinx.ext.coverage'   : found
> > > > Checking for 'sphinx.ext.doctest': found
> > > > Checking for 'sphinx.ext.graphviz'   : found
> > > > Checking for 'sphinx.ext.intersphinx': found
> > > > Checking for 'sphinx.ext.mathjax': found
> > > > Checking for 'sphinxcontrib.bibtex'  : not found (see README.txt)
> > >
>
> Did you manage to get past this yet? After you confirm you can build
> and see the changes for your pending documentation (example output)
> patch series, if you're happy with the ones on the list just ping one
> of them, or if you want to resend another version then prepare it with
> the -v3 I guess it would be by now.
>
> > > This looks like a helpful error message ;)
> > > In the README.txt you'll find the "Host set up" section that has some
> instructions about the required packages:
> https://git.rtems.org/rtems-docs/tree/README.txt#n92
> > >
> > > The short answer to your question:
> > > pip install sphinx
> > > pip install sphinxcontrib-bibtex
> > >
> >
> > I also strongly recommend following those README directions to do the
> > build within a virtualenv if you haven't been. This will help better
> > manage the python versions in use. (My host's native python
> > installation is broken quite badly, but virtualenv works well.)
> >
> > >
> > > Best regards,
> > > Vijay
> > >
> > > > The configuration failed
> > > > (complete log in
> /home/idadel/Desktop/gsoc/docs/rtems-docs/build/config.log)
> > > >
> > > > On Wed, Mar 17, 2021 at 9:37 PM Ida Delphine 
> wrote:
> > > >>
> > > >> Ok, I will do that.
> > > >>
> > > >> On Tue, Mar 16, 2021 at 7:56 PM Gedare Bloom 
> wrote:
> > > >>>
> > > >>> On Tue, Mar 16, 2021 at 12:16 PM Ida Delphine 
> wrote:
> > > >>> >
> > > >>> > I ran the commands and copied and pasted wherever there were
> mismatches especially with respect to the version numbers.
> > > >>> >
> > > >>> OK, I noticed some inconsistencies and was wondering. It would be
> > > >>> better to provide the actual output for the entire snippets, see
> > > >>> further below what I noticed.
> > > >>>
> > > >>> > Should I resend the patchset with a better commit message?
> > > >>> >
> > > >>> Yes. I think it would be better to also update the entire output
> > > >>> examples, and to separate them from the manual changes you make to
> the
> > > >>> version numbers. In other words, update the version numbers by hand
> > > >>> for some things, and update the console output examples separately.
> > > >>> You can put multiple changes together in one patch that are
> related,
> > > >>> for example you might just send one patch with all the console
> output
> > > >>> example updates.
> > > >>>
> > > >>> > On Tue, 16 Mar 2021, 6:50 pm Gedare Bloom, 
> wrote:
> > > >>> >>
> > > >>> >> Hi Ida,
> > > >>

Re: [PATCH rtems-docs v2 3/6] rtems-docs: Edit command to install toolsuite

[Ida Delphine]

I just installed texlive and trying to do a top level build using ./waf
configure. But looks like it doesn't work well...I get this error at the
end:
Setting top to   :
/home/idadel/Desktop/gsoc/docs/rtems-docs
Setting out to   :
/home/idadel/Desktop/gsoc/docs/rtems-docs/build
Checking for program 'git'   : /usr/bin/git
Checking for program 'sphinx-build'  :
/home/idadel/anaconda3/bin/sphinx-build
Checking for program 'aspell': /usr/bin/aspell
Checking if Sphinx is at least 1.3   : yes (3.5)
Checking Sphinx Options  : none
Checking Sphinx Nit-Pick mode: no
Checking for 'sphinx.ext.autodoc': found
Checking for 'sphinx.ext.coverage'   : found
Checking for 'sphinx.ext.doctest': found
Checking for 'sphinx.ext.graphviz'   : found
Checking for 'sphinx.ext.intersphinx': found
Checking for 'sphinx.ext.mathjax': found
Checking for 'sphinxcontrib.bibtex'  : not found (see README.txt)
The configuration failed
(complete log in /home/idadel/Desktop/gsoc/docs/rtems-docs/build/config.log)

On Wed, Mar 17, 2021 at 9:37 PM Ida Delphine  wrote:

> Ok, I will do that.
>
> On Tue, Mar 16, 2021 at 7:56 PM Gedare Bloom  wrote:
>
>> On Tue, Mar 16, 2021 at 12:16 PM Ida Delphine  wrote:
>> >
>> > I ran the commands and copied and pasted wherever there were mismatches
>> especially with respect to the version numbers.
>> >
>> OK, I noticed some inconsistencies and was wondering. It would be
>> better to provide the actual output for the entire snippets, see
>> further below what I noticed.
>>
>> > Should I resend the patchset with a better commit message?
>> >
>> Yes. I think it would be better to also update the entire output
>> examples, and to separate them from the manual changes you make to the
>> version numbers. In other words, update the version numbers by hand
>> for some things, and update the console output examples separately.
>> You can put multiple changes together in one patch that are related,
>> for example you might just send one patch with all the console output
>> example updates.
>>
>> > On Tue, 16 Mar 2021, 6:50 pm Gedare Bloom,  wrote:
>> >>
>> >> Hi Ida,
>> >>
>> >> Since the patches now indicate rtems-docs, you don't need to include
>> >> that in the commit message. Instead, it is recommended to put the
>> >> manual directory name that is modified as the first part of the
>> >> commit, e.g., "user: bump version 5 to 6 in start/tools.rst"
>> >>
>> >> More below:
>> >>
>> >> On Tue, Mar 16, 2021 at 2:16 AM Ida Delphine 
>> wrote:
>> >> >
>> >> > Edit edit sample output of tool suite installation.
>> >> > Edit command to check if C cross compiler works and sample output of
>> this command.
>> >> > ---
>> >> >  user/start/tools.rst | 26 +-
>> >> >  1 file changed, 13 insertions(+), 13 deletions(-)
>> >> >
>> >> > diff --git a/user/start/tools.rst b/user/start/tools.rst
>> >> > index baa2387..9a915ab 100644
>> >> > --- a/user/start/tools.rst
>> >> > +++ b/user/start/tools.rst
>> >> > @@ -12,7 +12,7 @@ Install the Tool Suite
>> >> >
>> >> >  You have chosen an installation prefix, the BSP to build, the tool's
>> >> >  architecure and prepared the source for the RSB in the previous
>> sections.  We
>> unrelated, fix typo: architecture
>>
>> >> > -have chosen :file:`$HOME/quick-start/rtems/5` as the installation
>> prefix, the
>> >> > +have chosen :file:`$HOME/quick-start/rtems/6` as the installation
>> prefix, the
>> >> >  ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``,
>> and unpacked
>> >> >  the RSB source in :file:`$HOME/quick-start/src`.
>> >> >
>> >> > @@ -25,7 +25,7 @@ Build and install the tool suite:
>> >> >  .. code-block:: none
>> >> >
>> >> >  cd $HOME/quick-start/src/rsb/rtems
>> >> > -../source-builder/sb-set-builder
>> --prefix=$HOME/quick-start/rtems/5 5/rtems-sparc
>> >> > +../source-builder/sb-set-builder
>> --prefix=$HOME/quick-start/rtems/6 6/rtems-sparc
>> >> >
>> >> >  This command should output something like this (omitted lines are
>> denoted by
>> >> >  ...). The build host appears as part of the name 

Re: [PATCH rtems-docs v2 2/6] rtems-docs: Update command for offline download

[Ida Delphine]

Yes. It was intended.

On Wed, 17 Mar 2021, 2:36 am Chris Johns,  wrote:

> On 16/3/21 7:15 pm, Ida Delphine wrote:
> > Changed command from ../source-builder/sb-set-builder
> --source-only-download 5/rtems-sparc to ../source-builder/sb-set-builder
> --source-only-download 6/rtems-sparc.
> > Updated sample output as well
>
> The commit message line is too long. Please break it up.
>
> > ---
> >  user/start/sources.rst | 10 +-
> >  1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/user/start/sources.rst b/user/start/sources.rst
> > index 8c40aa0..f4cb8ae 100644
> > --- a/user/start/sources.rst
> > +++ b/user/start/sources.rst
> > @@ -10,7 +10,7 @@ Obtain the Sources
> >  ==
> >
> >  You have considered and chosen a suitable installation prefix in the
> previous
> > -section.  We have chosen :file:`$HOME/quick-start/rtems/5` as the
> installation
> > +section.  We have chosen :file:`$HOME/quick-start/rtems/6` as the
> installation
> >  prefix. We will show how to use a released version of RTEMS and then as
> an
> >  alternative we will show you using the :ref:`RSB Git repository
> >  `. Consider using a Git clone if you wish to make
> > @@ -114,17 +114,17 @@ the sources to build the ERC 32 BSP before
> building run the following commands:
> >  .. code-block:: none
> >
> >  cd $HOME/quick-start/src/rsb/rtems
> > -../source-builder/sb-set-builder --source-only-download
> 5/rtems-sparc
> > +../source-builder/sb-set-builder --source-only-download
> 6/rtems-sparc
> >
> >  This command should output something like this (omitted lines are
> denoted by
> >  ``...``):
> >
> >  .. code-block:: none
> >
> > -RTEMS Source Builder - Set Builder, 5.1.0
> > -Build Set: 5/rtems-sparc
> > +RTEMS Source Builder - Set Builder, 6
> > +Build Set: 6/rtems-sparc
> >  ...
> > -download:
> https://ftp.rtems.org/pub/rtems/releases/5/5.1.0/5.1.0/sources/gcc-7.5.0.tar.xz
> -> sources/gcc-7.5.0.tar.xz
> > +download:
> https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2 ->
> sources/gmp-6.1.0.tar.bz2
>
> Probability a good idea to move away from using a released version in the
> part.
> Is that intended?
>
> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-docs v2 3/6] rtems-docs: Edit command to install toolsuite

[Ida Delphine]

Ok, I will do that.

On Tue, Mar 16, 2021 at 7:56 PM Gedare Bloom  wrote:

> On Tue, Mar 16, 2021 at 12:16 PM Ida Delphine  wrote:
> >
> > I ran the commands and copied and pasted wherever there were mismatches
> especially with respect to the version numbers.
> >
> OK, I noticed some inconsistencies and was wondering. It would be
> better to provide the actual output for the entire snippets, see
> further below what I noticed.
>
> > Should I resend the patchset with a better commit message?
> >
> Yes. I think it would be better to also update the entire output
> examples, and to separate them from the manual changes you make to the
> version numbers. In other words, update the version numbers by hand
> for some things, and update the console output examples separately.
> You can put multiple changes together in one patch that are related,
> for example you might just send one patch with all the console output
> example updates.
>
> > On Tue, 16 Mar 2021, 6:50 pm Gedare Bloom,  wrote:
> >>
> >> Hi Ida,
> >>
> >> Since the patches now indicate rtems-docs, you don't need to include
> >> that in the commit message. Instead, it is recommended to put the
> >> manual directory name that is modified as the first part of the
> >> commit, e.g., "user: bump version 5 to 6 in start/tools.rst"
> >>
> >> More below:
> >>
> >> On Tue, Mar 16, 2021 at 2:16 AM Ida Delphine  wrote:
> >> >
> >> > Edit edit sample output of tool suite installation.
> >> > Edit command to check if C cross compiler works and sample output of
> this command.
> >> > ---
> >> >  user/start/tools.rst | 26 +-
> >> >  1 file changed, 13 insertions(+), 13 deletions(-)
> >> >
> >> > diff --git a/user/start/tools.rst b/user/start/tools.rst
> >> > index baa2387..9a915ab 100644
> >> > --- a/user/start/tools.rst
> >> > +++ b/user/start/tools.rst
> >> > @@ -12,7 +12,7 @@ Install the Tool Suite
> >> >
> >> >  You have chosen an installation prefix, the BSP to build, the tool's
> >> >  architecure and prepared the source for the RSB in the previous
> sections.  We
> unrelated, fix typo: architecture
>
> >> > -have chosen :file:`$HOME/quick-start/rtems/5` as the installation
> prefix, the
> >> > +have chosen :file:`$HOME/quick-start/rtems/6` as the installation
> prefix, the
> >> >  ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``,
> and unpacked
> >> >  the RSB source in :file:`$HOME/quick-start/src`.
> >> >
> >> > @@ -25,7 +25,7 @@ Build and install the tool suite:
> >> >  .. code-block:: none
> >> >
> >> >  cd $HOME/quick-start/src/rsb/rtems
> >> > -../source-builder/sb-set-builder
> --prefix=$HOME/quick-start/rtems/5 5/rtems-sparc
> >> > +../source-builder/sb-set-builder
> --prefix=$HOME/quick-start/rtems/6 6/rtems-sparc
> >> >
> >> >  This command should output something like this (omitted lines are
> denoted by
> >> >  ...). The build host appears as part of the name of the package being
> >> > @@ -33,19 +33,19 @@ built. The name you see may vary depending on the
> host you are using:
> >> >
> >> >  .. code-block:: none
> >> >
> >> > -RTEMS Source Builder - Set Builder, 5.1.0
> >> > -Build Set: 5/rtems-sparc
> >> > +RTEMS Source Builder - Set Builder, 6
> >> > +Build Set: 6/rtems-sparc
> >> >  ...
> >> >  config: tools/rtems-binutils-2.34.cfg
> >> > -package: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
> >> > -building: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
> >> > -sizes: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1:
> 305.866MB (installed: 29.966MB)
> >> > -cleaning: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
> >> > +package: sparc-rtems6=-binutils-2.34-x86_64-freebsd12.1-1
>
> The = sign here is what got me thinking something odd is going on.
> Please copy-paste the entire output/snippet you get, and update the
> examples completely so that each snippet is self-consistent at least.
>
> >> > +building: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
> >> > +sizes: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1:
> 305.866MB (installed: 29.966MB)
> >> > +cleaning: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
> >> >

Re: #3860 - GSoC enquiries

[Ida Delphine]

Hello,
So I have gone through this configuration file and I think I'm getting it.
However I'm a bit lost in the reading the messages in the thread. Do you
mind explaining? Or we can start talking about a way forward.
Also can you help me with some steps on how to test this by myself if
possible?

Thanks,
Ida

On Mon, Mar 15, 2021 at 9:39 PM Gedare Bloom  wrote:

> See the related thread, and we'll have to discuss how to move forward.
> The existing approach provides an uncrustify script:
> https://lists.rtems.org/pipermail/devel/2020-October/062769.html
>
>
> On Sun, Mar 14, 2021 at 9:47 PM Ida Delphine  wrote:
> >
> > Hello everyone,
> > This ticket(https://devel.rtems.org/ticket/3860) was proposed to me and
> I'm interested in it for GSoC.
> > The first task there is to find a code checker or formater that can
> produce results that match the RTEMS coding conventions. It also made
> mention some tools have been discussed in the past. Please I will love
> suggestions on possible tools I could use to achieve this.
> >
> >
> > Cheers,
> > Ida.
> > ___
> > 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

Re: [PATCH rtems-docs] eng/vc-users: Set up patch message with repo name

[Ida Delphine]

Yay!!!
Thanks for the feedback. Will try building the docs.

On Tue, 16 Mar 2021, 8:08 pm Gedare Bloom,  wrote:

> Hi Ida,
>
> I have built and checked the output, it looks good but I did make a
> tiny change to remove HEAD^ with ... to be a bit non-specific, and
> fixed a typo in your commit message. I would however like you to
> confirm that you can build the docs :) as your next step, it is best
> to confirm that patches you send build properly. Pull the updated repo
> and build it to confirm you see your change properly made.
>
> When I applied this patch, I got
> warning: 2 lines add whitespace errors.
> I have fixed those two lines where there was a whitespace character at
> the end of the line. Although that is not such a big deal in the docs,
> we prefer to avoid those trailing spaces in code. Keep that in mind.
> Maybe someday we'll have a proper style checker to help ;)
>
> Congratulations on your first contribution :)
>
> Gedare
>
> On Tue, Mar 16, 2021 at 12:31 PM Ida Delphine  wrote:
> >
> > From: Meh Mbeh Ida Delphine 
> >
> > Added instructions on how to set up a patch messahe with a repo name.
> >
> > Author:Meh Mbeh Ida Delphine 
> > Date:  Tue Mar 16 19:11:23 2021 +0100
> > ---
> >  eng/vc-users.rst | 8 
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/eng/vc-users.rst b/eng/vc-users.rst
> > index 31de516..772019e 100644
> > --- a/eng/vc-users.rst
> > +++ b/eng/vc-users.rst
> > @@ -458,6 +458,14 @@ specify a version number for your patch, for
> example, use
> >
> >  to indicate the second version of a patch, ``-v3`` for a third, and so
> forth.
> >
> > +Also, in order to create a patch specifying the repo name in the patch
> message,
> > +you should use the``--subject-prefix`` flag. For example, if
> contributing to
> > +the rtems-docs repo, use
> > +
> > +.. code-block:: shell
> > +
> > +  git format-patch HEAD^ --subject-prefix="PATCH rtems-docs"
> > +
> >  Patches created using ``git format-patch`` are formatted so they can be
> emailed
> >  and rely on having Git configured with your name and email address, for
> example
> >
> > --
> > 2.25.1
> >
> > ___
> > 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

[PATCH rtems-docs] eng/vc-users: Set up patch message with repo name

[Ida Delphine]

From: Meh Mbeh Ida Delphine 

Added instructions on how to set up a patch messahe with a repo name.

Author:Meh Mbeh Ida Delphine 
Date:  Tue Mar 16 19:11:23 2021 +0100
---
 eng/vc-users.rst | 8 
 1 file changed, 8 insertions(+)

diff --git a/eng/vc-users.rst b/eng/vc-users.rst
index 31de516..772019e 100644
--- a/eng/vc-users.rst
+++ b/eng/vc-users.rst
@@ -458,6 +458,14 @@ specify a version number for your patch, for example, use
 
 to indicate the second version of a patch, ``-v3`` for a third, and so forth.
 
+Also, in order to create a patch specifying the repo name in the patch 
message, 
+you should use the``--subject-prefix`` flag. For example, if contributing to 
+the rtems-docs repo, use
+
+.. code-block:: shell
+
+  git format-patch HEAD^ --subject-prefix="PATCH rtems-docs"
+
 Patches created using ``git format-patch`` are formatted so they can be emailed
 and rely on having Git configured with your name and email address, for example
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-docs v2 3/6] rtems-docs: Edit command to install toolsuite

[Ida Delphine]

I ran the commands and copied and pasted wherever there were mismatches
especially with respect to the version numbers.

Should I resend the patchset with a better commit message?

On Tue, 16 Mar 2021, 6:50 pm Gedare Bloom,  wrote:

> Hi Ida,
>
> Since the patches now indicate rtems-docs, you don't need to include
> that in the commit message. Instead, it is recommended to put the
> manual directory name that is modified as the first part of the
> commit, e.g., "user: bump version 5 to 6 in start/tools.rst"
>
> More below:
>
> On Tue, Mar 16, 2021 at 2:16 AM Ida Delphine  wrote:
> >
> > Edit edit sample output of tool suite installation.
> > Edit command to check if C cross compiler works and sample output of
> this command.
> > ---
> >  user/start/tools.rst | 26 +-
> >  1 file changed, 13 insertions(+), 13 deletions(-)
> >
> > diff --git a/user/start/tools.rst b/user/start/tools.rst
> > index baa2387..9a915ab 100644
> > --- a/user/start/tools.rst
> > +++ b/user/start/tools.rst
> > @@ -12,7 +12,7 @@ Install the Tool Suite
> >
> >  You have chosen an installation prefix, the BSP to build, the tool's
> >  architecure and prepared the source for the RSB in the previous
> sections.  We
> > -have chosen :file:`$HOME/quick-start/rtems/5` as the installation
> prefix, the
> > +have chosen :file:`$HOME/quick-start/rtems/6` as the installation
> prefix, the
> >  ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``, and
> unpacked
> >  the RSB source in :file:`$HOME/quick-start/src`.
> >
> > @@ -25,7 +25,7 @@ Build and install the tool suite:
> >  .. code-block:: none
> >
> >  cd $HOME/quick-start/src/rsb/rtems
> > -../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5
> 5/rtems-sparc
> > +../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6
> 6/rtems-sparc
> >
> >  This command should output something like this (omitted lines are
> denoted by
> >  ...). The build host appears as part of the name of the package being
> > @@ -33,19 +33,19 @@ built. The name you see may vary depending on the
> host you are using:
> >
> >  .. code-block:: none
> >
> > -RTEMS Source Builder - Set Builder, 5.1.0
> > -Build Set: 5/rtems-sparc
> > +RTEMS Source Builder - Set Builder, 6
> > +Build Set: 6/rtems-sparc
> >  ...
> >  config: tools/rtems-binutils-2.34.cfg
> > -package: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
> > -building: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
> > -sizes: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB
> (installed: 29.966MB)
> > -cleaning: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
> > +package: sparc-rtems6=-binutils-2.34-x86_64-freebsd12.1-1
> > +building: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
> > +sizes: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB
> (installed: 29.966MB)
> > +cleaning: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
> >  reporting: tools/rtems-binutils-2.34.cfg ->
> sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.txt
> >  reporting: tools/rtems-binutils-2.34.cfg ->
> sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.xml
> >  config: tools/rtems-gcc-7.5.0-newlib-fbaa096.cfg
> > -package: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
> > -building: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
> > +package: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
> > +building: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
> >  
> >  Build Sizes: usage: 5.684GB total: 1.112GB (sources: 143.803MB,
> patches: 21.348KB, installed 995.188MB)
> >  Build Set: Time 0:21:35.626294
>
> Did you run the command and capture the sample output, or do you edit
> the sample output manually?
>
> It would be better to copy-paste the actual sample output. Making this
> version change update automatic could be a nice small scripting
> exercise.
>
> > @@ -55,7 +55,7 @@ works with the following command:
> >
> >  .. code-block:: none
> >
> > -$HOME/quick-start/rtems/5/bin/sparc-rtems5-gcc --version
> > +$HOME/quick-start/rtems/6/bin/sparc-rtems6-gcc --version
> >
> >  This command should output something like below.  The version
> informtion helps
> Unrelated, but can you fix this typo: information
>
> >  you to identify the exact sources used to build the cross compiler of
> your
> > @@ -69,8 +69,8 @@ source code 

Re: [PATCH 6/6] rtems-docs: Edit commands to build first app

[Ida Delphine]

Regarding the patch to add instructions on how to set up a  patch message
in which file should I create this patch or make changes?

On Mon, Mar 15, 2021 at 8:57 PM Gedare Bloom  wrote:

> Hi Ida,
>
> On Mon, Mar 15, 2021 at 1:50 PM Gedare Bloom  wrote:
> >
> > Hi Ida,
> >
> > did you send the same set of patches twice, or are there changes
> > between the two sets?
> >
>
> Since I'm not quite sure what to look at here, please do me a favor
> and send a new patchset with a -v2 indicator [1], and also set the
> patch message to specify rtems-docs. git format patch supports to set
> the prefix with:
>  git format-patch HEAD^ --subject-prefix="PATCH rtems-docs"
> You can also create an alias to make this simpler [2]. In fact, if you
> can send a patch to add instructions how to set up patch message with
> the repo name to the text at [1] that would be another nice
> contribution :)
>
> [1]
> https://docs.rtems.org/branches/master/eng/vc-users.html#creating-a-patch
> [2] https://lists.rtems.org/pipermail/devel/2020-April/059308.html
>
> Thank you,
> Gedare
>
> > On Sun, Mar 14, 2021 at 8:26 PM Ida Delphine  wrote:
> > >
> > > ---
> > >  user/start/app.rst | 104 ++---
> > >  1 file changed, 52 insertions(+), 52 deletions(-)
> > >
> > > diff --git a/user/start/app.rst b/user/start/app.rst
> > > index 8900f78..c343551 100644
> > > --- a/user/start/app.rst
> > > +++ b/user/start/app.rst
> > > @@ -8,7 +8,7 @@ Build Your Application
> > >  ==
> > >
> > >  You tested a BSP in the previous section.  We built the ``erc32`` BSP
> > > -and it is installed under :file:`$HOME/quick-start/rtems/5`.
> > > +and it is installed under :file:`$HOME/quick-start/rtems/6`.
> > >
> > >  We will now create a simple Hello World application with a Git
> > >  repository and using the `Waf <https://waf.io>`_ build system.
> > > @@ -107,7 +107,7 @@ and copy the Waf script:
> > >  #
> > >  from __future__ import print_function
> > >
> > > -rtems_version = "5"
> > > +rtems_version = "6"
> > >
> > >  try:
> > >  import rtems_waf.rtems as rtems
> > > @@ -142,52 +142,52 @@ Configure the application using Waf's
> ``configure`` command:
> > >
> > >  .. code-block:: none
> > >
> > > -./waf configure --rtems=$HOME/quick-start/rtems/5
> --rtems-bsp=sparc/erc32
> > > +./waf configure --rtems=$HOME/quick-start/rtems/6
> --rtems-bsp=sparc/erc32 --rtems-version=6
> > >
> > >  The output will be something close to:
> > >
> > >  .. code-block:: none
> > >
> > > - Setting top to   : $BASE/app/hello
> > > - Setting out to   : $BASE/app/hello/build
> > > - RTEMS Version: 5
> > > - Architectures: sparc-rtems5
> > > - Board Support Package (BSP)  : sparc-rtems5-erc32
> > > - Show commands: no
> > > - Long commands: no
> > > - Checking for program 'sparc-rtems5-gcc'  :
> $BASE/rtems/5/bin/sparc-rtems5-gcc
> > > - Checking for program 'sparc-rtems5-g++'  :
> $BASE/rtems/5/bin/sparc-rtems5-g++
> > > - Checking for program 'sparc-rtems5-gcc'  :
> $BASE/rtems/5/bin/sparc-rtems5-gcc
> > > - Checking for program 'sparc-rtems5-ld'   :
> $BASE/rtems/5/bin/sparc-rtems5-ld
> > > - Checking for program 'sparc-rtems5-ar'   :
> $BASE/rtems/5/bin/sparc-rtems5-ar
> > > - Checking for program 'sparc-rtems5-nm'   :
> $BASE/rtems/5/bin/sparc-rtems5-nm
> > > - Checking for program 'sparc-rtems5-objdump' :
> $BASE/rtems/5/bin/sparc-rtems5-objdump
> > > - Checking for program 'sparc-rtems5-objcopy' :
> $BASE/rtems/5/bin/sparc-rtems5-objcopy
> > > - Checking for program 'sparc-rtems5-readelf' :
> $BASE/rtems/5/bin/sparc-rtems5-readelf
> > > - Checking for program 'sparc-rtems5-strip'   :
> $BASE/rtems/5/bin/sparc-rtems5-strip
> > > - Checking for program 'sparc-rtems5-ranlib'  :
> $BASE/rtems/5/bin/sparc-rtems5-ranlib
> > > - Checking for program 'rtems-ld' :
> $BASE/rtems/5/bin/rtems-ld
> > > - Checking for program 'rtems-tld':
> $BASE/rtems/5/bin/rtems-tld
> > > - Checking for program 'rtems

[PATCH rtems-docs v2 6/6] rtems-docs: Edit commands to build first app

[Ida Delphine]

---
 user/start/app.rst | 110 ++---
 1 file changed, 55 insertions(+), 55 deletions(-)

diff --git a/user/start/app.rst b/user/start/app.rst
index 8900f78..8cbf6fc 100644
--- a/user/start/app.rst
+++ b/user/start/app.rst
@@ -8,7 +8,7 @@ Build Your Application
 ==
 
 You tested a BSP in the previous section.  We built the ``erc32`` BSP
-and it is installed under :file:`$HOME/quick-start/rtems/5`.
+and it is installed under :file:`$HOME/quick-start/rtems/6`.
 
 We will now create a simple Hello World application with a Git
 repository and using the `Waf `_ build system.
@@ -107,7 +107,7 @@ and copy the Waf script:
 #
 from __future__ import print_function
 
-rtems_version = "5"
+rtems_version = "6"
 
 try:
 import rtems_waf.rtems as rtems
@@ -142,52 +142,52 @@ Configure the application using Waf's ``configure`` 
command:
 
 .. code-block:: none
 
-./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
+./waf configure --rtems=$HOME/quick-start/rtems/6 --rtems-bsp=sparc/erc32 
--rtems-version=6
 
 The output will be something close to:
 
 .. code-block:: none
 
- Setting top to   : $BASE/app/hello
- Setting out to   : $BASE/app/hello/build
- RTEMS Version: 5
- Architectures: sparc-rtems5
- Board Support Package (BSP)  : sparc-rtems5-erc32
- Show commands: no
- Long commands: no
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
- Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'sparc-rtems5-nm'   : 
$BASE/rtems/5/bin/sparc-rtems5-nm
- Checking for program 'sparc-rtems5-objdump' : 
$BASE/rtems/5/bin/sparc-rtems5-objdump
- Checking for program 'sparc-rtems5-objcopy' : 
$BASE/rtems/5/bin/sparc-rtems5-objcopy
- Checking for program 'sparc-rtems5-readelf' : 
$BASE/rtems/5/bin/sparc-rtems5-readelf
- Checking for program 'sparc-rtems5-strip'   : 
$BASE/rtems/5/bin/sparc-rtems5-strip
- Checking for program 'sparc-rtems5-ranlib'  : 
$BASE/rtems/5/bin/sparc-rtems5-ranlib
- Checking for program 'rtems-ld' : $BASE/rtems/5/bin/rtems-ld
- Checking for program 'rtems-tld': $BASE/rtems/5/bin/rtems-tld
- Checking for program 'rtems-syms'   : $BASE/rtems/5/bin/rtems-syms
- Checking for program 'rtems-bin2c'  : 
$BASE/rtems/5/bin/rtems-bin2c
- Checking for program 'tar'  : /usr/bin/tar
- Checking for program 'gcc, cc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'g++, c++' : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'gas, gcc' : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for c flags '-MMD' : yes
- Checking for cxx flags '-MMD'   : yes
- Compiler version (sparc-rtems5-gcc) : 7.5.0 20191114 (RTEMS 5, 
RSB 5.1.0, Newlib fbaa096)
- Checking for a valid RTEMS BSP installation : yes
- Checking for RTEMS_DEBUG: no
- Checking for RTEMS_MULTIPROCESSING  : no
- Checking for RTEMS_NEWLIB   : yes
- Checking for RTEMS_POSIX_API: yes
- Checking for RTEMS_SMP  : no
- Checking for RTEMS_NETWORKING   : no
- 'configure' finished successfully (0.686s)
+Setting top to   : $BASE/app/hello 
+Setting out to   : $BASE/app/hello/build 
+RTEMS Version: 6 
+Architectures: sparc-rtems6 
+Board Support Package (BSP)  : sparc-rtems6-erc32 
+Show commands: no 
+Long commands: no 
+Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+Checking for program 'sparc-rtems6-g++'  : 
$BASE/rtems/6/bin/sparc-rtems6-g++ 
+Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+Checking for program 'sparc-rtems6-ld'   : 
$BASE/rtems/6/bin/sparc-rtems6-ld 
+Checking for program 'sparc-rtems6-ar'   : 

[PATCH rtems-docs v2 5/6] rtems-docs: Edit command to test BSP and sample output

[Ida Delphine]

---
 user/start/bsp-test.rst | 49 +++--
 1 file changed, 27 insertions(+), 22 deletions(-)

diff --git a/user/start/bsp-test.rst b/user/start/bsp-test.rst
index 9243f5d..cad6f23 100644
--- a/user/start/bsp-test.rst
+++ b/user/start/bsp-test.rst
@@ -30,37 +30,42 @@ by ``$BASE``.
 .. code-block:: none
 
 RTEMS Testing - Tester, 5.1.0
- Command Line: $BASE/rtems/5/bin/rtems-test --rtems-bsp=erc32-sis 
build/sparc/erc32
- Python: 2.7.15 (default, Jan 10 2019, 01:14:47) [GCC 4.2.1 Compatible 
FreeBSD Clang 6.0.1 (tags/RELEASE_601/final 335540)]
+ Command Line: $BASE/rtems/6/bin/rtems-test --rtems-bsp=erc32-sis 
build/sparc/erc32
+ Python: 3.8.5 (default, Jan 27 2021, 15:41:15) [GCC 9.3.0]
 Host: FreeBSD-12.0-RELEASE-p2-amd64-64bit-ELF (FreeBSD Build_FreeBSD12 
12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC amd64 amd64)
-[  1/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | 
sparc/erc32: dhrystone.exe
+[  1/570] p:0   f:0   u:0   e:0   I:0   B:0   t:0   L:0   i:0   W:0   | 
sparc/erc32: dhrystone.exe
 ...
-[589/589] p:574 f:0   u:5   e:0   I:0   B:3   t:0   i:0   W:0   | 
sparc/erc32: tmtimer01.exe
+[570/570] p:554 f:2   u:6   e:1   I:0   B:3   t:0   L:0   i:0   W:0   | 
sparc/erc32: ts-validation-1.exe
 
-Passed:580
-Failed:  0
-User Input:  5
-Expected Fail:   0
+Passed:558
+Failed:  2
+User Input:  6
+Expected Fail:   1
 Indeterminate:   0
 Benchmark:   3
-Timeout: 1
+Timeout: 0
+Test too long:   0
 Invalid: 0
 Wrong Version:   0
 Wrong Build: 0
 Wrong Tools: 0
 --
-Total: 589
+Total: 570
+Failures:
+dl06.exe
+minimum.exe
 User Input:
- monitor.exe
- termios.exe
- top.exe
- fileio.exe
- capture.exe
+dl10.exe
+monitor.exe
+termios.exe
+top.exe
+capture.exe
+fileio.exe
+Expected Fail:
+psxfenv01.exe
 Benchmark:
- whetstone.exe
- linpack.exe
- dhrystone.exe
-Timeouts:
- pppd.exe
-Average test time: 0:00:00.437773
-Testing time : 0:04:17.848557
+dhrystone.exe
+linpack.exe
+whetstone.exe
+Average test time: 0:00:00.371256
+Testing time : 0:03:31.616055
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v2 4/6] rtems-docs: Edit command to build BSP and

[Ida Delphine]

Edit sample output output as well substituting "5" with "6"
with regards to the current branch.

---
 user/start/bsp-build.rst | 74 
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/user/start/bsp-build.rst b/user/start/bsp-build.rst
index 137b3ab..c4d6db6 100644
--- a/user/start/bsp-build.rst
+++ b/user/start/bsp-build.rst
@@ -11,7 +11,7 @@ Build a Board Support Package (BSP)
 You installed the tool suite in your installation prefix, made ready the source
 for two RTEMS source packages and if you are using a Git clone bootstrapped the
 RTEMS sources in the previous sections.  We installed the tool suite in
-:file:`$HOME/quick-start/rtems/5` and unpacked the source in
+:file:`$HOME/quick-start/rtems/6` and unpacked the source in
 :file:`$HOME/quick-start/src`.
 
 You are now able to build :ref:`Board Support Packages (BSPs) ` for all
@@ -44,24 +44,24 @@ To build the BSP with all the tests run this command:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 \
---target=sparc-rtems5 --with-rtems-bsp=erc32 --with-rtems-tests=yes 
5/rtems-kernel
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 \
+--target=sparc-rtems6 --with-rtems-bsp=erc32 --with-rtems-tests=yes 
6/rtems-kernel
 
 This command should output something like this:
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-kernel
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-kernel
 config: tools/rtems-kernel-5.cfg
-package: sparc-rtems5-kernel-erc32-1
-building: sparc-rtems5-kernel-erc32-1
-sizes: sparc-rtems5-kernel-erc32-1: 2.279GB (installed: 44.612MB)
-cleaning: sparc-rtems5-kernel-erc32-1
-reporting: tools/rtems-kernel-5.cfg -> sparc-rtems5-kernel-erc32-1.txt
-reporting: tools/rtems-kernel-5.cfg -> sparc-rtems5-kernel-erc32-1.xml
-installing: sparc-rtems5-kernel-erc32-1 -> $BASE/
-cleaning: sparc-rtems5-kernel-erc32-1
+package: sparc-rtems6-kernel-erc32-1
+building: sparc-rtems6-kernel-erc32-1
+sizes: sparc-rtems6-kernel-erc32-1: 2.279GB (installed: 44.612MB)
+cleaning: sparc-rtems6-kernel-erc32-1
+reporting: tools/rtems-kernel-5.cfg -> sparc-rtems6-kernel-erc32-1.txt
+reporting: tools/rtems-kernel-5.cfg -> sparc-rtems6-kernel-erc32-1.xml
+installing: sparc-rtems6-kernel-erc32-1 -> $BASE/
+cleaning: sparc-rtems6-kernel-erc32-1
 Build Set: Time 0:03:09.896961
 
 The RSB BSP build can be customised with following RSB command line options:
@@ -112,13 +112,13 @@ directory to your ``$PATH`` throughout the remaining 
steps. Run the command:
 
 .. code-block:: none
 
-export PATH=$HOME/quick-start/rtems/5/bin:"$PATH"
+export PATH=$HOME/quick-start/rtems/6/bin:"$PATH"
 
 Check your installed tools can be found by running:
 
 .. code-block:: none
 
-command -v sparc-rtems5-gcc && echo "found" || echo "not found"
+command -v sparc-rtems6-gcc && echo "found" || echo "not found"
 
 The output should be:
 
@@ -128,7 +128,7 @@ The output should be:
 
 If ``not found`` is printed the tools are not correctly installed or the path
 has not been correctly set. Check the contents of the path
-:file:`$HOME/quick-start/rtems/5/bin` manually and if :file:`sparc-rtems5-gcc`
+:file:`$HOME/quick-start/rtems/6/bin` manually and if :file:`sparc-rtems6-gcc`
 is present the path is wrong. If the file cannot be found return to
 :ref:`QuickStartTools` and install the tools again.
 
@@ -145,7 +145,7 @@ everything else.  For detailed information about the BSP 
build system, see
 cd $HOME/quick-start/src/rtems
 echo "[sparc/erc32]" > config.ini
 echo "BUILD_TESTS = True" >> config.ini
-./waf configure --prefix=$HOME/quick-start/rtems/5
+./waf configure --prefix=$HOME/quick-start/rtems/6
 
 The first invocation of ``./waf`` needs a bit of time (e.g. 10 seconds) since 
an
 internal cache file is populated.  This command should output something like
@@ -158,24 +158,24 @@ by ``$BASE``.
 Setting out to   : $BASE/src/rtems/build
 Regenerate build specification cache (needs a couple of seconds)...
 Configure board support package (BSP): sparc/erc32
-Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
-Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
-Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'g++, c++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'gas, gcc'  : 

[PATCH rtems-docs v2 3/6] rtems-docs: Edit command to install toolsuite

[Ida Delphine]

Edit edit sample output of tool suite installation.
Edit command to check if C cross compiler works and sample output of this 
command.
---
 user/start/tools.rst | 26 +-
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/user/start/tools.rst b/user/start/tools.rst
index baa2387..9a915ab 100644
--- a/user/start/tools.rst
+++ b/user/start/tools.rst
@@ -12,7 +12,7 @@ Install the Tool Suite
 
 You have chosen an installation prefix, the BSP to build, the tool's
 architecure and prepared the source for the RSB in the previous sections.  We
-have chosen :file:`$HOME/quick-start/rtems/5` as the installation prefix, the
+have chosen :file:`$HOME/quick-start/rtems/6` as the installation prefix, the
 ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``, and unpacked
 the RSB source in :file:`$HOME/quick-start/src`.
 
@@ -25,7 +25,7 @@ Build and install the tool suite:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 
5/rtems-sparc
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 
6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ...). The build host appears as part of the name of the package being
@@ -33,19 +33,19 @@ built. The name you see may vary depending on the host you 
are using:
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-sparc
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-sparc
 ...
 config: tools/rtems-binutils-2.34.cfg
-package: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
-building: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
-sizes: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB 
(installed: 29.966MB)
-cleaning: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
+package: sparc-rtems6=-binutils-2.34-x86_64-freebsd12.1-1
+building: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
+sizes: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB 
(installed: 29.966MB)
+cleaning: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
 reporting: tools/rtems-binutils-2.34.cfg -> 
sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.txt
 reporting: tools/rtems-binutils-2.34.cfg -> 
sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.xml
 config: tools/rtems-gcc-7.5.0-newlib-fbaa096.cfg
-package: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
-building: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
+package: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
+building: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
 
 Build Sizes: usage: 5.684GB total: 1.112GB (sources: 143.803MB, patches: 
21.348KB, installed 995.188MB)
 Build Set: Time 0:21:35.626294
@@ -55,7 +55,7 @@ works with the following command:
 
 .. code-block:: none
 
-$HOME/quick-start/rtems/5/bin/sparc-rtems5-gcc --version
+$HOME/quick-start/rtems/6/bin/sparc-rtems6-gcc --version
 
 This command should output something like below.  The version informtion helps
 you to identify the exact sources used to build the cross compiler of your
@@ -69,8 +69,8 @@ source code used.
 
 .. code-block:: none
 
-sparc-rtems5-gcc (GCC) 7.5.0 20191114 (RTEMS 5, RSB 5.1.0, Newlib fbaa096)
-Copyright (C) 2017 Free Software Foundation, Inc.
+sparc-rtems6-gcc (GCC) 10.2.1 20210309 (RTEMS 6, RSB 
5e449fb5c2cb6812a238f9f9764fd339cbbf05c2, Newlib d10d0d9)
+Copyright (C) 2020 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v2 1/6] rtems-docs: Update installation prefix

[Ida Delphine]

---
 user/start/prefixes.rst | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/user/start/prefixes.rst b/user/start/prefixes.rst
index 67255d0..826ce85 100644
--- a/user/start/prefixes.rst
+++ b/user/start/prefixes.rst
@@ -40,7 +40,7 @@ applications and systems.
 You build and install the tool suite with the :ref:`RTEMS Source Builder (RSB)
 `.  By default, the RSB will start the prefix path with a host operating
 system specific path plus :file:`rtems`, and the RTEMS version, e.g.
-:file:`/opt/rtems/5` on Linux, and :file:`/usr/local/rtems/5` on FreeBSD and
+:file:`/opt/rtems/6` on Linux, and :file:`/usr/local/rtems/6` on FreeBSD and
 macOS. Placing the RTEMS version number in the path lets you manage and
 migrate RTEMS versions as they are released.
 
@@ -50,10 +50,10 @@ make sure that your normal user has sufficient privileges 
to create files and
 directories under the prefix.  For example, you can create a directory
 :file:`/opt/rtems` and give it to a developer group with read, write, and
 execute permissions.  Alternatively, you can choose a prefix in your home
-directory, e.g. :file:`$HOME/rtems/5` or with a project-specific component
-:file:`$HOME/project-x/rtems/5`.  For more ideas, see the :ref:`project
+directory, e.g. :file:`$HOME/rtems/6` or with a project-specific component
+:file:`$HOME/project-x/rtems/6`.  For more ideas, see the :ref:`project
 sandboxing ` section.  In this quick start chapter, we will
-choose :file:`$HOME/quick-start/rtems/5` for the RTEMS tool suite prefix.
+choose :file:`$HOME/quick-start/rtems/6` for the RTEMS tool suite prefix.
 
 .. warning::
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-docs v2 2/6] rtems-docs: Update command for offline download

[Ida Delphine]

Changed command from ../source-builder/sb-set-builder --source-only-download 
5/rtems-sparc to ../source-builder/sb-set-builder --source-only-download 
6/rtems-sparc.
Updated sample output as well
---
 user/start/sources.rst | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/user/start/sources.rst b/user/start/sources.rst
index 8c40aa0..f4cb8ae 100644
--- a/user/start/sources.rst
+++ b/user/start/sources.rst
@@ -10,7 +10,7 @@ Obtain the Sources
 ==
 
 You have considered and chosen a suitable installation prefix in the previous
-section.  We have chosen :file:`$HOME/quick-start/rtems/5` as the installation
+section.  We have chosen :file:`$HOME/quick-start/rtems/6` as the installation
 prefix. We will show how to use a released version of RTEMS and then as an
 alternative we will show you using the :ref:`RSB Git repository
 `. Consider using a Git clone if you wish to make
@@ -114,17 +114,17 @@ the sources to build the ERC 32 BSP before building run 
the following commands:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
+../source-builder/sb-set-builder --source-only-download 6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ``...``):
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-sparc
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-sparc
 ...
-download: 
https://ftp.rtems.org/pub/rtems/releases/5/5.1.0/5.1.0/sources/gcc-7.5.0.tar.xz 
-> sources/gcc-7.5.0.tar.xz
+download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2 -> 
sources/gmp-6.1.0.tar.bz2
 ...
 Build Sizes: usage: 0.000B total: 143.814MB (sources: 143.793MB, patches: 
21.348KB, installed 0.000B)
 Build Set: Time 0:05:52.617958
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Regarding gsoc project 3860

[Ida Delphine]

Umm...did you bring up a discussion regarding this project earlier?

On Mon, 15 Mar 2021, 8:10 am Ayushman Mishra, 
wrote:

> AYUSHMAN MISHRA
>
> Hello Ida delphini AYUSHMAN here , Can you please select any other project
> for gsoc as I am also currently working on proposal for the same project
> https://devel.rtems.org/ticket/3860 for gsoc 2021
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

#3860 - GSoC enquiries

[Ida Delphine]

Hello everyone,
This ticket(https://devel.rtems.org/ticket/3860) was proposed to me and I'm
interested in it for GSoC.
The first task there is to find a code checker or formater that can produce
results that match the RTEMS coding conventions. It also made mention some
tools have been discussed in the past. Please I will love suggestions on
possible tools I could use to achieve this.


Cheers,
Ida.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 1/1] Hello World - Ida's proof to work on rtems

[Ida Delphine]

Thanks for the feedback!

On Sun, Mar 14, 2021 at 5:32 PM Gedare Bloom  wrote:

> Hi Ida,
>
> This is acceptable for your proof and no further revisions are
> required, but please see my notes below:
>
> On Fri, Mar 12, 2021 at 9:13 PM Ida Delphine  wrote:
> >
> > From: Meh Mbeh Ida Delphine 
> >
> Author info looks good, thanks.
>
> > Modified rtems/testsuites/samples/hello/init.c to prove I can work on
> the RTEMS project for GSoC.
> See https://devel.rtems.org/wiki/Developer/Git#GitCommits for more
> about preparing "real commits" in the future. This one is acceptable
> for the proof.
>
> (We need to merge that text from
> https://devel.rtems.org/wiki/Developer/Git#GitCommits into a suitable
> subsection in
> https://docs.rtems.org/branches/master/eng/vc-users.html#creating-a-patch
> someday.)
>
> > ---
> >  testsuites/samples/hello/init.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/testsuites/samples/hello/init.c
> b/testsuites/samples/hello/init.c
> > index 34ded37c55..fa581fd447 100644
> > --- a/testsuites/samples/hello/init.c
> > +++ b/testsuites/samples/hello/init.c
> > @@ -22,7 +22,7 @@ static rtems_task Init(
> >  {
> >rtems_print_printer_fprintf_putc(_test_printer);
> >TEST_BEGIN();
> > -  printf( "Hello World\n" );
> > +  printf( "Hello World, I'm Ida Deslphine and this is th main proof I
> can officially work on the RTEMS Project for GSoC. I'm so excited. Thank
> you all for the help you rendered when I ran into several errors!\n" );
>
> The message is great! :) Now you can start to see why we make this
> task part of our proposal preparation!
>
> Note that our code style adheres to a maximum of 80 characters per
> line: https://docs.rtems.org/branches/master/eng/coding.html
>
> We are still working toward automated code style checking (which is by
> the way a GSoC project: https://devel.rtems.org/ticket/3860 that does
> not require strong C/asm skills).
>
> Please add your info to
> https://devel.rtems.org/wiki/GSoC/2021#StudentsProposals
>
> I guess so far none of the other students who did the proof have added
> themselves, but feel free to be first! If you need help on the
> formatting, you can go in the prior year's GSoC and see how the table
> is set up. (Click Edit on the bottom of the page to find the wiki
> source.)
>
> Gedare
>
> >TEST_END();
> >rtems_test_exit( 0 );
> >  }
> > --
> > 2.25.1
> >
> > ___
> > 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

[PATCH 2/6] rtems-docs: Update command for offline download

[Ida Delphine]

Changed command from ../source-builder/sb-set-builder --source-only-download 
5/rtems-sparc to ../source-builder/sb-set-builder --source-only-download 
6/rtems-sparc.
Updated sample output as well
---
 user/start/sources.rst | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/user/start/sources.rst b/user/start/sources.rst
index 8c40aa0..f4cb8ae 100644
--- a/user/start/sources.rst
+++ b/user/start/sources.rst
@@ -10,7 +10,7 @@ Obtain the Sources
 ==
 
 You have considered and chosen a suitable installation prefix in the previous
-section.  We have chosen :file:`$HOME/quick-start/rtems/5` as the installation
+section.  We have chosen :file:`$HOME/quick-start/rtems/6` as the installation
 prefix. We will show how to use a released version of RTEMS and then as an
 alternative we will show you using the :ref:`RSB Git repository
 `. Consider using a Git clone if you wish to make
@@ -114,17 +114,17 @@ the sources to build the ERC 32 BSP before building run 
the following commands:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
+../source-builder/sb-set-builder --source-only-download 6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ``...``):
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-sparc
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-sparc
 ...
-download: 
https://ftp.rtems.org/pub/rtems/releases/5/5.1.0/5.1.0/sources/gcc-7.5.0.tar.xz 
-> sources/gcc-7.5.0.tar.xz
+download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2 -> 
sources/gmp-6.1.0.tar.bz2
 ...
 Build Sizes: usage: 0.000B total: 143.814MB (sources: 143.793MB, patches: 
21.348KB, installed 0.000B)
 Build Set: Time 0:05:52.617958
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 1/6] rtems-docs: Update installation prefix

[Ida Delphine]

---
 user/start/prefixes.rst | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/user/start/prefixes.rst b/user/start/prefixes.rst
index 67255d0..826ce85 100644
--- a/user/start/prefixes.rst
+++ b/user/start/prefixes.rst
@@ -40,7 +40,7 @@ applications and systems.
 You build and install the tool suite with the :ref:`RTEMS Source Builder (RSB)
 `.  By default, the RSB will start the prefix path with a host operating
 system specific path plus :file:`rtems`, and the RTEMS version, e.g.
-:file:`/opt/rtems/5` on Linux, and :file:`/usr/local/rtems/5` on FreeBSD and
+:file:`/opt/rtems/6` on Linux, and :file:`/usr/local/rtems/6` on FreeBSD and
 macOS. Placing the RTEMS version number in the path lets you manage and
 migrate RTEMS versions as they are released.
 
@@ -50,10 +50,10 @@ make sure that your normal user has sufficient privileges 
to create files and
 directories under the prefix.  For example, you can create a directory
 :file:`/opt/rtems` and give it to a developer group with read, write, and
 execute permissions.  Alternatively, you can choose a prefix in your home
-directory, e.g. :file:`$HOME/rtems/5` or with a project-specific component
-:file:`$HOME/project-x/rtems/5`.  For more ideas, see the :ref:`project
+directory, e.g. :file:`$HOME/rtems/6` or with a project-specific component
+:file:`$HOME/project-x/rtems/6`.  For more ideas, see the :ref:`project
 sandboxing ` section.  In this quick start chapter, we will
-choose :file:`$HOME/quick-start/rtems/5` for the RTEMS tool suite prefix.
+choose :file:`$HOME/quick-start/rtems/6` for the RTEMS tool suite prefix.
 
 .. warning::
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 6/6] rtems-docs: Edit commands to build first app

[Ida Delphine]

---
 user/start/app.rst | 104 ++---
 1 file changed, 52 insertions(+), 52 deletions(-)

diff --git a/user/start/app.rst b/user/start/app.rst
index 8900f78..c343551 100644
--- a/user/start/app.rst
+++ b/user/start/app.rst
@@ -8,7 +8,7 @@ Build Your Application
 ==
 
 You tested a BSP in the previous section.  We built the ``erc32`` BSP
-and it is installed under :file:`$HOME/quick-start/rtems/5`.
+and it is installed under :file:`$HOME/quick-start/rtems/6`.
 
 We will now create a simple Hello World application with a Git
 repository and using the `Waf `_ build system.
@@ -107,7 +107,7 @@ and copy the Waf script:
 #
 from __future__ import print_function
 
-rtems_version = "5"
+rtems_version = "6"
 
 try:
 import rtems_waf.rtems as rtems
@@ -142,52 +142,52 @@ Configure the application using Waf's ``configure`` 
command:
 
 .. code-block:: none
 
-./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
+./waf configure --rtems=$HOME/quick-start/rtems/6 --rtems-bsp=sparc/erc32 
--rtems-version=6
 
 The output will be something close to:
 
 .. code-block:: none
 
- Setting top to   : $BASE/app/hello
- Setting out to   : $BASE/app/hello/build
- RTEMS Version: 5
- Architectures: sparc-rtems5
- Board Support Package (BSP)  : sparc-rtems5-erc32
- Show commands: no
- Long commands: no
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
- Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'sparc-rtems5-nm'   : 
$BASE/rtems/5/bin/sparc-rtems5-nm
- Checking for program 'sparc-rtems5-objdump' : 
$BASE/rtems/5/bin/sparc-rtems5-objdump
- Checking for program 'sparc-rtems5-objcopy' : 
$BASE/rtems/5/bin/sparc-rtems5-objcopy
- Checking for program 'sparc-rtems5-readelf' : 
$BASE/rtems/5/bin/sparc-rtems5-readelf
- Checking for program 'sparc-rtems5-strip'   : 
$BASE/rtems/5/bin/sparc-rtems5-strip
- Checking for program 'sparc-rtems5-ranlib'  : 
$BASE/rtems/5/bin/sparc-rtems5-ranlib
- Checking for program 'rtems-ld' : $BASE/rtems/5/bin/rtems-ld
- Checking for program 'rtems-tld': $BASE/rtems/5/bin/rtems-tld
- Checking for program 'rtems-syms'   : $BASE/rtems/5/bin/rtems-syms
- Checking for program 'rtems-bin2c'  : 
$BASE/rtems/5/bin/rtems-bin2c
- Checking for program 'tar'  : /usr/bin/tar
- Checking for program 'gcc, cc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'g++, c++' : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'gas, gcc' : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for c flags '-MMD' : yes
- Checking for cxx flags '-MMD'   : yes
- Compiler version (sparc-rtems5-gcc) : 7.5.0 20191114 (RTEMS 5, 
RSB 5.1.0, Newlib fbaa096)
- Checking for a valid RTEMS BSP installation : yes
- Checking for RTEMS_DEBUG: no
- Checking for RTEMS_MULTIPROCESSING  : no
- Checking for RTEMS_NEWLIB   : yes
- Checking for RTEMS_POSIX_API: yes
- Checking for RTEMS_SMP  : no
- Checking for RTEMS_NETWORKING   : no
- 'configure' finished successfully (0.686s)
+Setting top to   : $BASE/app/hello 
+Setting out to   : $BASE/app/hello/build 
+RTEMS Version: 6 
+Architectures: sparc-rtems6 
+Board Support Package (BSP)  : sparc-rtems6-erc32 
+Show commands: no 
+Long commands: no 
+Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+Checking for program 'sparc-rtems6-g++'  : 
$BASE/rtems/6/bin/sparc-rtems6-g++ 
+Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+Checking for program 'sparc-rtems6-ld'   : 
$BASE/rtems/6/bin/sparc-rtems6-ld 
+Checking for program 'sparc-rtems6-ar'   : 

[PATCH 1/6] rtems-docs: Update installation prefix

[Ida Delphine]

---
 user/start/prefixes.rst | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/user/start/prefixes.rst b/user/start/prefixes.rst
index 67255d0..826ce85 100644
--- a/user/start/prefixes.rst
+++ b/user/start/prefixes.rst
@@ -40,7 +40,7 @@ applications and systems.
 You build and install the tool suite with the :ref:`RTEMS Source Builder (RSB)
 `.  By default, the RSB will start the prefix path with a host operating
 system specific path plus :file:`rtems`, and the RTEMS version, e.g.
-:file:`/opt/rtems/5` on Linux, and :file:`/usr/local/rtems/5` on FreeBSD and
+:file:`/opt/rtems/6` on Linux, and :file:`/usr/local/rtems/6` on FreeBSD and
 macOS. Placing the RTEMS version number in the path lets you manage and
 migrate RTEMS versions as they are released.
 
@@ -50,10 +50,10 @@ make sure that your normal user has sufficient privileges 
to create files and
 directories under the prefix.  For example, you can create a directory
 :file:`/opt/rtems` and give it to a developer group with read, write, and
 execute permissions.  Alternatively, you can choose a prefix in your home
-directory, e.g. :file:`$HOME/rtems/5` or with a project-specific component
-:file:`$HOME/project-x/rtems/5`.  For more ideas, see the :ref:`project
+directory, e.g. :file:`$HOME/rtems/6` or with a project-specific component
+:file:`$HOME/project-x/rtems/6`.  For more ideas, see the :ref:`project
 sandboxing ` section.  In this quick start chapter, we will
-choose :file:`$HOME/quick-start/rtems/5` for the RTEMS tool suite prefix.
+choose :file:`$HOME/quick-start/rtems/6` for the RTEMS tool suite prefix.
 
 .. warning::
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 2/6] rtems-docs: Update command for offline download

[Ida Delphine]

Changed command from ../source-builder/sb-set-builder --source-only-download 
5/rtems-sparc to ../source-builder/sb-set-builder --source-only-download 
6/rtems-sparc.
Updated sample output as well
---
 user/start/sources.rst | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/user/start/sources.rst b/user/start/sources.rst
index 8c40aa0..f4cb8ae 100644
--- a/user/start/sources.rst
+++ b/user/start/sources.rst
@@ -10,7 +10,7 @@ Obtain the Sources
 ==
 
 You have considered and chosen a suitable installation prefix in the previous
-section.  We have chosen :file:`$HOME/quick-start/rtems/5` as the installation
+section.  We have chosen :file:`$HOME/quick-start/rtems/6` as the installation
 prefix. We will show how to use a released version of RTEMS and then as an
 alternative we will show you using the :ref:`RSB Git repository
 `. Consider using a Git clone if you wish to make
@@ -114,17 +114,17 @@ the sources to build the ERC 32 BSP before building run 
the following commands:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --source-only-download 5/rtems-sparc
+../source-builder/sb-set-builder --source-only-download 6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ``...``):
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-sparc
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-sparc
 ...
-download: 
https://ftp.rtems.org/pub/rtems/releases/5/5.1.0/5.1.0/sources/gcc-7.5.0.tar.xz 
-> sources/gcc-7.5.0.tar.xz
+download: https://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2 -> 
sources/gmp-6.1.0.tar.bz2
 ...
 Build Sizes: usage: 0.000B total: 143.814MB (sources: 143.793MB, patches: 
21.348KB, installed 0.000B)
 Build Set: Time 0:05:52.617958
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 3/6] rtems-docs: Edit command to install tool suite

[Ida Delphine]

Edit edit sample output of tool suite installation.
Edit command to check if C cross compiler works and sample output of this 
command.
---
 user/start/tools.rst | 26 +-
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/user/start/tools.rst b/user/start/tools.rst
index baa2387..9a915ab 100644
--- a/user/start/tools.rst
+++ b/user/start/tools.rst
@@ -12,7 +12,7 @@ Install the Tool Suite
 
 You have chosen an installation prefix, the BSP to build, the tool's
 architecure and prepared the source for the RSB in the previous sections.  We
-have chosen :file:`$HOME/quick-start/rtems/5` as the installation prefix, the
+have chosen :file:`$HOME/quick-start/rtems/6` as the installation prefix, the
 ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``, and unpacked
 the RSB source in :file:`$HOME/quick-start/src`.
 
@@ -25,7 +25,7 @@ Build and install the tool suite:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 
5/rtems-sparc
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 
6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ...). The build host appears as part of the name of the package being
@@ -33,19 +33,19 @@ built. The name you see may vary depending on the host you 
are using:
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-sparc
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-sparc
 ...
 config: tools/rtems-binutils-2.34.cfg
-package: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
-building: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
-sizes: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB 
(installed: 29.966MB)
-cleaning: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
+package: sparc-rtems6=-binutils-2.34-x86_64-freebsd12.1-1
+building: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
+sizes: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB 
(installed: 29.966MB)
+cleaning: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
 reporting: tools/rtems-binutils-2.34.cfg -> 
sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.txt
 reporting: tools/rtems-binutils-2.34.cfg -> 
sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.xml
 config: tools/rtems-gcc-7.5.0-newlib-fbaa096.cfg
-package: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
-building: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
+package: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
+building: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
 
 Build Sizes: usage: 5.684GB total: 1.112GB (sources: 143.803MB, patches: 
21.348KB, installed 995.188MB)
 Build Set: Time 0:21:35.626294
@@ -55,7 +55,7 @@ works with the following command:
 
 .. code-block:: none
 
-$HOME/quick-start/rtems/5/bin/sparc-rtems5-gcc --version
+$HOME/quick-start/rtems/6/bin/sparc-rtems6-gcc --version
 
 This command should output something like below.  The version informtion helps
 you to identify the exact sources used to build the cross compiler of your
@@ -69,8 +69,8 @@ source code used.
 
 .. code-block:: none
 
-sparc-rtems5-gcc (GCC) 7.5.0 20191114 (RTEMS 5, RSB 5.1.0, Newlib fbaa096)
-Copyright (C) 2017 Free Software Foundation, Inc.
+sparc-rtems6-gcc (GCC) 10.2.1 20210309 (RTEMS 6, RSB 
5e449fb5c2cb6812a238f9f9764fd339cbbf05c2, Newlib d10d0d9)
+Copyright (C) 2020 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 3/6] rtems-docs: Edit command to install tool suite

[Ida Delphine]

Edit edit sample output of tool suite installation.
Edit command to check if C cross compiler works and sample output of this 
command.
---
 user/start/tools.rst | 26 +-
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/user/start/tools.rst b/user/start/tools.rst
index baa2387..9a915ab 100644
--- a/user/start/tools.rst
+++ b/user/start/tools.rst
@@ -12,7 +12,7 @@ Install the Tool Suite
 
 You have chosen an installation prefix, the BSP to build, the tool's
 architecure and prepared the source for the RSB in the previous sections.  We
-have chosen :file:`$HOME/quick-start/rtems/5` as the installation prefix, the
+have chosen :file:`$HOME/quick-start/rtems/6` as the installation prefix, the
 ``erc32`` BSP and the SPARC architecture name of ``sparc-rtems5``, and unpacked
 the RSB source in :file:`$HOME/quick-start/src`.
 
@@ -25,7 +25,7 @@ Build and install the tool suite:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 
5/rtems-sparc
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 
6/rtems-sparc
 
 This command should output something like this (omitted lines are denoted by
 ...). The build host appears as part of the name of the package being
@@ -33,19 +33,19 @@ built. The name you see may vary depending on the host you 
are using:
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-sparc
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-sparc
 ...
 config: tools/rtems-binutils-2.34.cfg
-package: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
-building: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
-sizes: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB 
(installed: 29.966MB)
-cleaning: sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1
+package: sparc-rtems6=-binutils-2.34-x86_64-freebsd12.1-1
+building: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
+sizes: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1: 305.866MB 
(installed: 29.966MB)
+cleaning: sparc-rtems6-binutils-2.34-x86_64-freebsd12.1-1
 reporting: tools/rtems-binutils-2.34.cfg -> 
sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.txt
 reporting: tools/rtems-binutils-2.34.cfg -> 
sparc-rtems5-binutils-2.34-x86_64-freebsd12.1-1.xml
 config: tools/rtems-gcc-7.5.0-newlib-fbaa096.cfg
-package: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
-building: sparc-rtems5-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
+package: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
+building: sparc-rtems6-gcc-7.5.0-newlib-fbaa096-x86_64-freebsd12.1-1
 
 Build Sizes: usage: 5.684GB total: 1.112GB (sources: 143.803MB, patches: 
21.348KB, installed 995.188MB)
 Build Set: Time 0:21:35.626294
@@ -55,7 +55,7 @@ works with the following command:
 
 .. code-block:: none
 
-$HOME/quick-start/rtems/5/bin/sparc-rtems5-gcc --version
+$HOME/quick-start/rtems/6/bin/sparc-rtems6-gcc --version
 
 This command should output something like below.  The version informtion helps
 you to identify the exact sources used to build the cross compiler of your
@@ -69,8 +69,8 @@ source code used.
 
 .. code-block:: none
 
-sparc-rtems5-gcc (GCC) 7.5.0 20191114 (RTEMS 5, RSB 5.1.0, Newlib fbaa096)
-Copyright (C) 2017 Free Software Foundation, Inc.
+sparc-rtems6-gcc (GCC) 10.2.1 20210309 (RTEMS 6, RSB 
5e449fb5c2cb6812a238f9f9764fd339cbbf05c2, Newlib d10d0d9)
+Copyright (C) 2020 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 5/6] rtems-docs: Edit command to test BSP and sample output

[Ida Delphine]

---
 user/start/bsp-test.rst | 49 +++--
 1 file changed, 27 insertions(+), 22 deletions(-)

diff --git a/user/start/bsp-test.rst b/user/start/bsp-test.rst
index 9243f5d..cad6f23 100644
--- a/user/start/bsp-test.rst
+++ b/user/start/bsp-test.rst
@@ -30,37 +30,42 @@ by ``$BASE``.
 .. code-block:: none
 
 RTEMS Testing - Tester, 5.1.0
- Command Line: $BASE/rtems/5/bin/rtems-test --rtems-bsp=erc32-sis 
build/sparc/erc32
- Python: 2.7.15 (default, Jan 10 2019, 01:14:47) [GCC 4.2.1 Compatible 
FreeBSD Clang 6.0.1 (tags/RELEASE_601/final 335540)]
+ Command Line: $BASE/rtems/6/bin/rtems-test --rtems-bsp=erc32-sis 
build/sparc/erc32
+ Python: 3.8.5 (default, Jan 27 2021, 15:41:15) [GCC 9.3.0]
 Host: FreeBSD-12.0-RELEASE-p2-amd64-64bit-ELF (FreeBSD Build_FreeBSD12 
12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC amd64 amd64)
-[  1/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | 
sparc/erc32: dhrystone.exe
+[  1/570] p:0   f:0   u:0   e:0   I:0   B:0   t:0   L:0   i:0   W:0   | 
sparc/erc32: dhrystone.exe
 ...
-[589/589] p:574 f:0   u:5   e:0   I:0   B:3   t:0   i:0   W:0   | 
sparc/erc32: tmtimer01.exe
+[570/570] p:554 f:2   u:6   e:1   I:0   B:3   t:0   L:0   i:0   W:0   | 
sparc/erc32: ts-validation-1.exe
 
-Passed:580
-Failed:  0
-User Input:  5
-Expected Fail:   0
+Passed:558
+Failed:  2
+User Input:  6
+Expected Fail:   1
 Indeterminate:   0
 Benchmark:   3
-Timeout: 1
+Timeout: 0
+Test too long:   0
 Invalid: 0
 Wrong Version:   0
 Wrong Build: 0
 Wrong Tools: 0
 --
-Total: 589
+Total: 570
+Failures:
+dl06.exe
+minimum.exe
 User Input:
- monitor.exe
- termios.exe
- top.exe
- fileio.exe
- capture.exe
+dl10.exe
+monitor.exe
+termios.exe
+top.exe
+capture.exe
+fileio.exe
+Expected Fail:
+psxfenv01.exe
 Benchmark:
- whetstone.exe
- linpack.exe
- dhrystone.exe
-Timeouts:
- pppd.exe
-Average test time: 0:00:00.437773
-Testing time : 0:04:17.848557
+dhrystone.exe
+linpack.exe
+whetstone.exe
+Average test time: 0:00:00.371256
+Testing time : 0:03:31.616055
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 6/6] rtems-docs: Edit commands to build first app

[Ida Delphine]

---
 user/start/app.rst | 104 ++---
 1 file changed, 52 insertions(+), 52 deletions(-)

diff --git a/user/start/app.rst b/user/start/app.rst
index 8900f78..c343551 100644
--- a/user/start/app.rst
+++ b/user/start/app.rst
@@ -8,7 +8,7 @@ Build Your Application
 ==
 
 You tested a BSP in the previous section.  We built the ``erc32`` BSP
-and it is installed under :file:`$HOME/quick-start/rtems/5`.
+and it is installed under :file:`$HOME/quick-start/rtems/6`.
 
 We will now create a simple Hello World application with a Git
 repository and using the `Waf `_ build system.
@@ -107,7 +107,7 @@ and copy the Waf script:
 #
 from __future__ import print_function
 
-rtems_version = "5"
+rtems_version = "6"
 
 try:
 import rtems_waf.rtems as rtems
@@ -142,52 +142,52 @@ Configure the application using Waf's ``configure`` 
command:
 
 .. code-block:: none
 
-./waf configure --rtems=$HOME/quick-start/rtems/5 --rtems-bsp=sparc/erc32
+./waf configure --rtems=$HOME/quick-start/rtems/6 --rtems-bsp=sparc/erc32 
--rtems-version=6
 
 The output will be something close to:
 
 .. code-block:: none
 
- Setting top to   : $BASE/app/hello
- Setting out to   : $BASE/app/hello/build
- RTEMS Version: 5
- Architectures: sparc-rtems5
- Board Support Package (BSP)  : sparc-rtems5-erc32
- Show commands: no
- Long commands: no
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
- Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'sparc-rtems5-nm'   : 
$BASE/rtems/5/bin/sparc-rtems5-nm
- Checking for program 'sparc-rtems5-objdump' : 
$BASE/rtems/5/bin/sparc-rtems5-objdump
- Checking for program 'sparc-rtems5-objcopy' : 
$BASE/rtems/5/bin/sparc-rtems5-objcopy
- Checking for program 'sparc-rtems5-readelf' : 
$BASE/rtems/5/bin/sparc-rtems5-readelf
- Checking for program 'sparc-rtems5-strip'   : 
$BASE/rtems/5/bin/sparc-rtems5-strip
- Checking for program 'sparc-rtems5-ranlib'  : 
$BASE/rtems/5/bin/sparc-rtems5-ranlib
- Checking for program 'rtems-ld' : $BASE/rtems/5/bin/rtems-ld
- Checking for program 'rtems-tld': $BASE/rtems/5/bin/rtems-tld
- Checking for program 'rtems-syms'   : $BASE/rtems/5/bin/rtems-syms
- Checking for program 'rtems-bin2c'  : 
$BASE/rtems/5/bin/rtems-bin2c
- Checking for program 'tar'  : /usr/bin/tar
- Checking for program 'gcc, cc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'g++, c++' : 
$BASE/rtems/5/bin/sparc-rtems5-g++
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for program 'gas, gcc' : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
- Checking for program 'ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
- Checking for c flags '-MMD' : yes
- Checking for cxx flags '-MMD'   : yes
- Compiler version (sparc-rtems5-gcc) : 7.5.0 20191114 (RTEMS 5, 
RSB 5.1.0, Newlib fbaa096)
- Checking for a valid RTEMS BSP installation : yes
- Checking for RTEMS_DEBUG: no
- Checking for RTEMS_MULTIPROCESSING  : no
- Checking for RTEMS_NEWLIB   : yes
- Checking for RTEMS_POSIX_API: yes
- Checking for RTEMS_SMP  : no
- Checking for RTEMS_NETWORKING   : no
- 'configure' finished successfully (0.686s)
+Setting top to   : $BASE/app/hello 
+Setting out to   : $BASE/app/hello/build 
+RTEMS Version: 6 
+Architectures: sparc-rtems6 
+Board Support Package (BSP)  : sparc-rtems6-erc32 
+Show commands: no 
+Long commands: no 
+Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+Checking for program 'sparc-rtems6-g++'  : 
$BASE/rtems/6/bin/sparc-rtems6-g++ 
+Checking for program 'sparc-rtems6-gcc'  : 
$BASE/rtems/6/bin/sparc-rtems6-gcc 
+Checking for program 'sparc-rtems6-ld'   : 
$BASE/rtems/6/bin/sparc-rtems6-ld 
+Checking for program 'sparc-rtems6-ar'   : 

[PATCH 4/6] rtems-docs: Edit command to build BSP and sample output

[Ida Delphine]

---
 user/start/bsp-build.rst | 74 
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/user/start/bsp-build.rst b/user/start/bsp-build.rst
index 137b3ab..c4d6db6 100644
--- a/user/start/bsp-build.rst
+++ b/user/start/bsp-build.rst
@@ -11,7 +11,7 @@ Build a Board Support Package (BSP)
 You installed the tool suite in your installation prefix, made ready the source
 for two RTEMS source packages and if you are using a Git clone bootstrapped the
 RTEMS sources in the previous sections.  We installed the tool suite in
-:file:`$HOME/quick-start/rtems/5` and unpacked the source in
+:file:`$HOME/quick-start/rtems/6` and unpacked the source in
 :file:`$HOME/quick-start/src`.
 
 You are now able to build :ref:`Board Support Packages (BSPs) ` for all
@@ -44,24 +44,24 @@ To build the BSP with all the tests run this command:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 \
---target=sparc-rtems5 --with-rtems-bsp=erc32 --with-rtems-tests=yes 
5/rtems-kernel
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 \
+--target=sparc-rtems6 --with-rtems-bsp=erc32 --with-rtems-tests=yes 
6/rtems-kernel
 
 This command should output something like this:
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-kernel
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-kernel
 config: tools/rtems-kernel-5.cfg
-package: sparc-rtems5-kernel-erc32-1
-building: sparc-rtems5-kernel-erc32-1
-sizes: sparc-rtems5-kernel-erc32-1: 2.279GB (installed: 44.612MB)
-cleaning: sparc-rtems5-kernel-erc32-1
-reporting: tools/rtems-kernel-5.cfg -> sparc-rtems5-kernel-erc32-1.txt
-reporting: tools/rtems-kernel-5.cfg -> sparc-rtems5-kernel-erc32-1.xml
-installing: sparc-rtems5-kernel-erc32-1 -> $BASE/
-cleaning: sparc-rtems5-kernel-erc32-1
+package: sparc-rtems6-kernel-erc32-1
+building: sparc-rtems6-kernel-erc32-1
+sizes: sparc-rtems6-kernel-erc32-1: 2.279GB (installed: 44.612MB)
+cleaning: sparc-rtems6-kernel-erc32-1
+reporting: tools/rtems-kernel-5.cfg -> sparc-rtems6-kernel-erc32-1.txt
+reporting: tools/rtems-kernel-5.cfg -> sparc-rtems6-kernel-erc32-1.xml
+installing: sparc-rtems6-kernel-erc32-1 -> $BASE/
+cleaning: sparc-rtems6-kernel-erc32-1
 Build Set: Time 0:03:09.896961
 
 The RSB BSP build can be customised with following RSB command line options:
@@ -112,13 +112,13 @@ directory to your ``$PATH`` throughout the remaining 
steps. Run the command:
 
 .. code-block:: none
 
-export PATH=$HOME/quick-start/rtems/5/bin:"$PATH"
+export PATH=$HOME/quick-start/rtems/6/bin:"$PATH"
 
 Check your installed tools can be found by running:
 
 .. code-block:: none
 
-command -v sparc-rtems5-gcc && echo "found" || echo "not found"
+command -v sparc-rtems6-gcc && echo "found" || echo "not found"
 
 The output should be:
 
@@ -128,7 +128,7 @@ The output should be:
 
 If ``not found`` is printed the tools are not correctly installed or the path
 has not been correctly set. Check the contents of the path
-:file:`$HOME/quick-start/rtems/5/bin` manually and if :file:`sparc-rtems5-gcc`
+:file:`$HOME/quick-start/rtems/6/bin` manually and if :file:`sparc-rtems6-gcc`
 is present the path is wrong. If the file cannot be found return to
 :ref:`QuickStartTools` and install the tools again.
 
@@ -145,7 +145,7 @@ everything else.  For detailed information about the BSP 
build system, see
 cd $HOME/quick-start/src/rtems
 echo "[sparc/erc32]" > config.ini
 echo "BUILD_TESTS = True" >> config.ini
-./waf configure --prefix=$HOME/quick-start/rtems/5
+./waf configure --prefix=$HOME/quick-start/rtems/6
 
 The first invocation of ``./waf`` needs a bit of time (e.g. 10 seconds) since 
an
 internal cache file is populated.  This command should output something like
@@ -158,24 +158,24 @@ by ``$BASE``.
 Setting out to   : $BASE/src/rtems/build
 Regenerate build specification cache (needs a couple of seconds)...
 Configure board support package (BSP): sparc/erc32
-Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
-Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
-Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'g++, c++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'gas, gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-

[PATCH 4/6] rtems-docs: Edit command to build BSP and sample output

[Ida Delphine]

---
 user/start/bsp-build.rst | 74 
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/user/start/bsp-build.rst b/user/start/bsp-build.rst
index 137b3ab..c4d6db6 100644
--- a/user/start/bsp-build.rst
+++ b/user/start/bsp-build.rst
@@ -11,7 +11,7 @@ Build a Board Support Package (BSP)
 You installed the tool suite in your installation prefix, made ready the source
 for two RTEMS source packages and if you are using a Git clone bootstrapped the
 RTEMS sources in the previous sections.  We installed the tool suite in
-:file:`$HOME/quick-start/rtems/5` and unpacked the source in
+:file:`$HOME/quick-start/rtems/6` and unpacked the source in
 :file:`$HOME/quick-start/src`.
 
 You are now able to build :ref:`Board Support Packages (BSPs) ` for all
@@ -44,24 +44,24 @@ To build the BSP with all the tests run this command:
 .. code-block:: none
 
 cd $HOME/quick-start/src/rsb/rtems
-../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/5 \
---target=sparc-rtems5 --with-rtems-bsp=erc32 --with-rtems-tests=yes 
5/rtems-kernel
+../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 \
+--target=sparc-rtems6 --with-rtems-bsp=erc32 --with-rtems-tests=yes 
6/rtems-kernel
 
 This command should output something like this:
 
 .. code-block:: none
 
-RTEMS Source Builder - Set Builder, 5.1.0
-Build Set: 5/rtems-kernel
+RTEMS Source Builder - Set Builder, 6
+Build Set: 6/rtems-kernel
 config: tools/rtems-kernel-5.cfg
-package: sparc-rtems5-kernel-erc32-1
-building: sparc-rtems5-kernel-erc32-1
-sizes: sparc-rtems5-kernel-erc32-1: 2.279GB (installed: 44.612MB)
-cleaning: sparc-rtems5-kernel-erc32-1
-reporting: tools/rtems-kernel-5.cfg -> sparc-rtems5-kernel-erc32-1.txt
-reporting: tools/rtems-kernel-5.cfg -> sparc-rtems5-kernel-erc32-1.xml
-installing: sparc-rtems5-kernel-erc32-1 -> $BASE/
-cleaning: sparc-rtems5-kernel-erc32-1
+package: sparc-rtems6-kernel-erc32-1
+building: sparc-rtems6-kernel-erc32-1
+sizes: sparc-rtems6-kernel-erc32-1: 2.279GB (installed: 44.612MB)
+cleaning: sparc-rtems6-kernel-erc32-1
+reporting: tools/rtems-kernel-5.cfg -> sparc-rtems6-kernel-erc32-1.txt
+reporting: tools/rtems-kernel-5.cfg -> sparc-rtems6-kernel-erc32-1.xml
+installing: sparc-rtems6-kernel-erc32-1 -> $BASE/
+cleaning: sparc-rtems6-kernel-erc32-1
 Build Set: Time 0:03:09.896961
 
 The RSB BSP build can be customised with following RSB command line options:
@@ -112,13 +112,13 @@ directory to your ``$PATH`` throughout the remaining 
steps. Run the command:
 
 .. code-block:: none
 
-export PATH=$HOME/quick-start/rtems/5/bin:"$PATH"
+export PATH=$HOME/quick-start/rtems/6/bin:"$PATH"
 
 Check your installed tools can be found by running:
 
 .. code-block:: none
 
-command -v sparc-rtems5-gcc && echo "found" || echo "not found"
+command -v sparc-rtems6-gcc && echo "found" || echo "not found"
 
 The output should be:
 
@@ -128,7 +128,7 @@ The output should be:
 
 If ``not found`` is printed the tools are not correctly installed or the path
 has not been correctly set. Check the contents of the path
-:file:`$HOME/quick-start/rtems/5/bin` manually and if :file:`sparc-rtems5-gcc`
+:file:`$HOME/quick-start/rtems/6/bin` manually and if :file:`sparc-rtems6-gcc`
 is present the path is wrong. If the file cannot be found return to
 :ref:`QuickStartTools` and install the tools again.
 
@@ -145,7 +145,7 @@ everything else.  For detailed information about the BSP 
build system, see
 cd $HOME/quick-start/src/rtems
 echo "[sparc/erc32]" > config.ini
 echo "BUILD_TESTS = True" >> config.ini
-./waf configure --prefix=$HOME/quick-start/rtems/5
+./waf configure --prefix=$HOME/quick-start/rtems/6
 
 The first invocation of ``./waf`` needs a bit of time (e.g. 10 seconds) since 
an
 internal cache file is populated.  This command should output something like
@@ -158,24 +158,24 @@ by ``$BASE``.
 Setting out to   : $BASE/src/rtems/build
 Regenerate build specification cache (needs a couple of seconds)...
 Configure board support package (BSP): sparc/erc32
-Checking for program 'sparc-rtems5-gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
-Checking for program 'sparc-rtems5-g++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
-Checking for program 'sparc-rtems5-ar'   : 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'sparc-rtems5-ld'   : 
$BASE/rtems/5/bin/sparc-rtems5-ld
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'g++, c++'  : 
$BASE/rtems/5/bin/sparc-rtems5-g++
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-Checking for program 'gas, gcc'  : 
$BASE/rtems/5/bin/sparc-rtems5-gcc
-Checking for program 'ar': 
$BASE/rtems/5/bin/sparc-rtems5-ar
-

[PATCH 5/6] rtems-docs: Edit command to test BSP and sample output

[Ida Delphine]

---
 user/start/bsp-test.rst | 49 +++--
 1 file changed, 27 insertions(+), 22 deletions(-)

diff --git a/user/start/bsp-test.rst b/user/start/bsp-test.rst
index 9243f5d..cad6f23 100644
--- a/user/start/bsp-test.rst
+++ b/user/start/bsp-test.rst
@@ -30,37 +30,42 @@ by ``$BASE``.
 .. code-block:: none
 
 RTEMS Testing - Tester, 5.1.0
- Command Line: $BASE/rtems/5/bin/rtems-test --rtems-bsp=erc32-sis 
build/sparc/erc32
- Python: 2.7.15 (default, Jan 10 2019, 01:14:47) [GCC 4.2.1 Compatible 
FreeBSD Clang 6.0.1 (tags/RELEASE_601/final 335540)]
+ Command Line: $BASE/rtems/6/bin/rtems-test --rtems-bsp=erc32-sis 
build/sparc/erc32
+ Python: 3.8.5 (default, Jan 27 2021, 15:41:15) [GCC 9.3.0]
 Host: FreeBSD-12.0-RELEASE-p2-amd64-64bit-ELF (FreeBSD Build_FreeBSD12 
12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC amd64 amd64)
-[  1/589] p:0   f:0   u:0   e:0   I:0   B:0   t:0   i:0   W:0   | 
sparc/erc32: dhrystone.exe
+[  1/570] p:0   f:0   u:0   e:0   I:0   B:0   t:0   L:0   i:0   W:0   | 
sparc/erc32: dhrystone.exe
 ...
-[589/589] p:574 f:0   u:5   e:0   I:0   B:3   t:0   i:0   W:0   | 
sparc/erc32: tmtimer01.exe
+[570/570] p:554 f:2   u:6   e:1   I:0   B:3   t:0   L:0   i:0   W:0   | 
sparc/erc32: ts-validation-1.exe
 
-Passed:580
-Failed:  0
-User Input:  5
-Expected Fail:   0
+Passed:558
+Failed:  2
+User Input:  6
+Expected Fail:   1
 Indeterminate:   0
 Benchmark:   3
-Timeout: 1
+Timeout: 0
+Test too long:   0
 Invalid: 0
 Wrong Version:   0
 Wrong Build: 0
 Wrong Tools: 0
 --
-Total: 589
+Total: 570
+Failures:
+dl06.exe
+minimum.exe
 User Input:
- monitor.exe
- termios.exe
- top.exe
- fileio.exe
- capture.exe
+dl10.exe
+monitor.exe
+termios.exe
+top.exe
+capture.exe
+fileio.exe
+Expected Fail:
+psxfenv01.exe
 Benchmark:
- whetstone.exe
- linpack.exe
- dhrystone.exe
-Timeouts:
- pppd.exe
-Average test time: 0:00:00.437773
-Testing time : 0:04:17.848557
+dhrystone.exe
+linpack.exe
+whetstone.exe
+Average test time: 0:00:00.371256
+Testing time : 0:03:31.616055
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 1/1] Hello World - Ida's proof to work on rtems

[Ida Delphine]

Here's a screenshot as requested on the guide.

Thanks,
Ida.

On Sat, Mar 13, 2021 at 5:13 AM Ida Delphine  wrote:

> From: Meh Mbeh Ida Delphine 
>
> Modified rtems/testsuites/samples/hello/init.c to prove I can work on the
> RTEMS project for GSoC.
> ---
>  testsuites/samples/hello/init.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testsuites/samples/hello/init.c
> b/testsuites/samples/hello/init.c
> index 34ded37c55..fa581fd447 100644
> --- a/testsuites/samples/hello/init.c
> +++ b/testsuites/samples/hello/init.c
> @@ -22,7 +22,7 @@ static rtems_task Init(
>  {
>rtems_print_printer_fprintf_putc(_test_printer);
>TEST_BEGIN();
> -  printf( "Hello World\n" );
> +  printf( "Hello World, I'm Ida Deslphine and this is th main proof I can
> officially work on the RTEMS Project for GSoC. I'm so excited. Thank you
> all for the help you rendered when I ran into several errors!\n" );
>TEST_END();
>rtems_test_exit( 0 );
>  }
> --
> 2.25.1
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 1/1] Hello World - Ida's proof to work on rtems

[Ida Delphine]

From: Meh Mbeh Ida Delphine 

Modified rtems/testsuites/samples/hello/init.c to prove I can work on the RTEMS 
project for GSoC.
---
 testsuites/samples/hello/init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c
index 34ded37c55..fa581fd447 100644
--- a/testsuites/samples/hello/init.c
+++ b/testsuites/samples/hello/init.c
@@ -22,7 +22,7 @@ static rtems_task Init(
 {
   rtems_print_printer_fprintf_putc(_test_printer);
   TEST_BEGIN();
-  printf( "Hello World\n" );
+  printf( "Hello World, I'm Ida Deslphine and this is th main proof I can 
officially work on the RTEMS Project for GSoC. I'm so excited. Thank you all 
for the help you rendered when I ran into several errors!\n" );
   TEST_END();
   rtems_test_exit( 0 );
 }
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 0/1] My First Contribution

[Ida Delphine]

I modified init.c and tested it successfully as proof I can work on the RTEMS 
Project for GSoC.

Meh Mbeh Ida Delphine (1):
  Hello World - Ida's proof to work on rtems

 testsuites/samples/hello/init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC Introduction

[Ida Delphine]

Is it okay I assign a task to myself?

On Wed, 10 Mar 2021, 11:30 pm Gedare Bloom,  wrote:

> On Wed, Mar 10, 2021 at 3:44 AM Prateek Pardeshi 
> wrote:
> >
> > Hello and Welcome, Ida !
> >
> Indeed, welcome
>
> >  On Wed, 10 Mar 2021 12:30:51 +0530 Ida Delphine 
> wrote 
> >
> >  > Greetings everyone,
> >  >
> >  > I am Ida Delphine from the University of Bamenda, Cameroon. I came
> across RTEMS when lurking the GSoC organisations page. Considering my
> interest iand little experience in the embedded space, I'll love to get to
> know more about RTEMS. I'm very proficient in Python and will love to
> contribute to RTEMS for GSoC 2021.
> >  >
> >
> > You can go through this page for setting up RTEMS on your system.
> https://docs.rtems.org/branches/master/user/start/gsoc.html
> >
> > Also, you can explore the projects on (
> https://devel.rtems.org/wiki/Developer/OpenProjects) and choose what
> you're interested in.
> >
> Many of the Testing and the Development Environment tasks are
> Python-related. There is some C++ (coverage testing) and the rest is
> mostly in C/asm.
>
> > You can ask your doubts here, someone on this mailinglist would
> definitely help you out.
> >
> >
> > Regards,
> > Prateek
> >
> >  > ___
> >  > 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
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

GSoC Introduction

[Ida Delphine]

Greetings everyone,

I am Ida Delphine from the University of Bamenda, Cameroon. I came across
RTEMS when lurking the GSoC organisations page. Considering my interest
iand little experience in the embedded space, I'll love to get to know more
about RTEMS. I'm very proficient in Python and will love to contribute to
RTEMS for GSoC 2021.

Cheers,
Ida.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel