Re: Error when trying to build llvm

2021-07-30 Thread Joel Sherrill 
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

Re: [PATCH] rtems: Generate

2021-07-30 Thread Joel Sherrill 
On Fri, Jul 30, 2021 at 1:52 AM Sebastian Huber
 wrote:
>
> On 30/07/2021 00:54, Chris Johns wrote:
> > On 29/7/21 10:59 pm, Sebastian Huber wrote:
> >> On 29/07/2021 14:51, Sebastian Huber wrote:
> >>> Change license to BSD-2-Clause according to file histories and
> >>> documentation re-licensing agreement.
> >>>
> >>> Place the group into the I/O Manager group.  Add all source files to the
> >>> group.
> >>>
> >>> Update #3899.
> >>> Update #3993.
> >>

Should the specification include what format specifiers are supported? Those
would seem to be API contracts/requirements.

> >> It would be easy to add a chapter for this to the Classic API Guide (for 
> >> example
> >> "Kernel Character I/O Support"):
> >>
> >> https://ftp.rtems.org/pub/rtems/people/sebh/c-user.pdf
> >>
> >
> > Looks good.
> >
> > I think something should be said about the relationship of this interface 
> > to the
> > standard console and termios streams. Specifically they can use the same BSP
> > device and the output can become mixed if both are being used at the same 
> > time.
> >
> > Should something be said about which calls can be used during interrupts? 
> > Also
> > concurrent calls on SMP system are not serialised.
> >
> I updated the proposal:
>
> https://lists.rtems.org/pipermail/devel/2021-July/068657.html
>
> --
> 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: [PATCH] rtems: Generate

2021-07-30 Thread Sebastian Huber 

On 30/07/2021 15:25, Joel Sherrill wrote:

On Fri, Jul 30, 2021 at 1:52 AM Sebastian Huber
  wrote:

On 30/07/2021 00:54, Chris Johns wrote:

On 29/7/21 10:59 pm, Sebastian Huber wrote:

On 29/07/2021 14:51, Sebastian Huber wrote:

Change license to BSD-2-Clause according to file histories and
documentation re-licensing agreement.

Place the group into the I/O Manager group.  Add all source files to the
group.

Update #3899.
Update #3993.

Should the specification include what format specifiers are supported? Those
would seem to be API contracts/requirements.


What we have currently is this:

.. rubric:: PARAMETERS:

``fmt``
This parameter is a printf()-style format string.

.. rubric:: CONSTRAINTS:

The following constraints apply to this directive:

* The directive may be called from within any runtime context.

* The directive will not cause the calling task to be preempted.

* Formatting of floating point numbers is not supported.

Doing a detailed documentation of the supported format specifiers would 
be a bit of work.


--
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: [PATCH] rtems: Generate

2021-07-30 Thread Joel Sherrill 
On Fri, Jul 30, 2021, 8:33 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 30/07/2021 15:25, Joel Sherrill wrote:
> > On Fri, Jul 30, 2021 at 1:52 AM Sebastian Huber
> >   wrote:
> >> On 30/07/2021 00:54, Chris Johns wrote:
> >>> On 29/7/21 10:59 pm, Sebastian Huber wrote:
>  On 29/07/2021 14:51, Sebastian Huber wrote:
> > Change license to BSD-2-Clause according to file histories and
> > documentation re-licensing agreement.
> >
> > Place the group into the I/O Manager group.  Add all source files to
> the
> > group.
> >
> > Update #3899.
> > Update #3993.
> > Should the specification include what format specifiers are supported?
> Those
> > would seem to be API contracts/requirements.
>
> What we have currently is this:
>
> .. rubric:: PARAMETERS:
>
> ``fmt``
>  This parameter is a printf()-style format string.
>
> .. rubric:: CONSTRAINTS:
>
> The following constraints apply to this directive:
>
> * The directive may be called from within any runtime context.
>
> * The directive will not cause the calling task to be preempted.
>
> * Formatting of floating point numbers is not supported.
>
> Doing a detailed documentation of the supported format specifiers would
> be a bit of work.
>

I wasn't thinking of heavy detail. Just a list of which specifiers are
supported and maybe some general missing format options. Beyond that see
printf for details.

I was thinking you would need a requirement for a specifier that is
supported. Otherwise you don't have traceability to the entire source code.

Trying to focus on general description of what was present for the missing
the requirements are positive, not negative.

--joel

>
> --
> 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: [PATCH] rtems: Generate

2021-07-30 Thread Sebastian Huber 

On 30/07/2021 15:55, Joel Sherrill wrote:


On Fri, Jul 30, 2021, 8:33 AM Sebastian Huber 
> wrote:


On 30/07/2021 15:25, Joel Sherrill wrote:
 > On Fri, Jul 30, 2021 at 1:52 AM Sebastian Huber
 > mailto:sebastian.hu...@embedded-brains.de>>  wrote:
 >> On 30/07/2021 00:54, Chris Johns wrote:
 >>> On 29/7/21 10:59 pm, Sebastian Huber wrote:
  On 29/07/2021 14:51, Sebastian Huber wrote:
 > Change license to BSD-2-Clause according to file histories and
 > documentation re-licensing agreement.
 >
 > Place the group into the I/O Manager group.  Add all source
files to the
 > group.
 >
 > Update #3899.
 > Update #3993.
 > Should the specification include what format specifiers are
supported? Those
 > would seem to be API contracts/requirements.

What we have currently is this:

.. rubric:: PARAMETERS:

``fmt``
      This parameter is a printf()-style format string.

.. rubric:: CONSTRAINTS:

The following constraints apply to this directive:

* The directive may be called from within any runtime context.

* The directive will not cause the calling task to be preempted.

* Formatting of floating point numbers is not supported.

Doing a detailed documentation of the supported format specifiers would
be a bit of work.


I wasn't thinking of heavy detail. Just a list of which specifiers are 
supported and maybe some general missing format options. Beyond that see 
printf for details.


I was thinking you would need a requirement for a specifier that is 
supported. Otherwise you don't have traceability to the entire source code.


Trying to focus on general description of what was present for the 
missing the requirements are positive, not negative.


For the space profile I only need rtems_putc(), rtems_put_char(), and 
getchark(). The _IO_Vprintf() belongs to the test code.


--
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: [PATCH] rtems: Generate

2021-07-30 Thread Joel Sherrill 
On Fri, Jul 30, 2021, 9:24 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 30/07/2021 15:55, Joel Sherrill wrote:
> >
> > On Fri, Jul 30, 2021, 8:33 AM Sebastian Huber
> >  > > wrote:
> >
> > On 30/07/2021 15:25, Joel Sherrill wrote:
> >  > On Fri, Jul 30, 2021 at 1:52 AM Sebastian Huber
> >  >  > >  wrote:
> >  >> On 30/07/2021 00:54, Chris Johns wrote:
> >  >>> On 29/7/21 10:59 pm, Sebastian Huber wrote:
> >   On 29/07/2021 14:51, Sebastian Huber wrote:
> >  > Change license to BSD-2-Clause according to file histories and
> >  > documentation re-licensing agreement.
> >  >
> >  > Place the group into the I/O Manager group.  Add all source
> > files to the
> >  > group.
> >  >
> >  > Update #3899.
> >  > Update #3993.
> >  > Should the specification include what format specifiers are
> > supported? Those
> >  > would seem to be API contracts/requirements.
> >
> > What we have currently is this:
> >
> > .. rubric:: PARAMETERS:
> >
> > ``fmt``
> >   This parameter is a printf()-style format string.
> >
> > .. rubric:: CONSTRAINTS:
> >
> > The following constraints apply to this directive:
> >
> > * The directive may be called from within any runtime context.
> >
> > * The directive will not cause the calling task to be preempted.
> >
> > * Formatting of floating point numbers is not supported.
> >
> > Doing a detailed documentation of the supported format specifiers
> would
> > be a bit of work.
> >
> >
> > I wasn't thinking of heavy detail. Just a list of which specifiers are
> > supported and maybe some general missing format options. Beyond that see
> > printf for details.
> >
> > I was thinking you would need a requirement for a specifier that is
> > supported. Otherwise you don't have traceability to the entire source
> code.
> >
> > Trying to focus on general description of what was present for the
> > missing the requirements are positive, not negative.
>
> For the space profile I only need rtems_putc(), rtems_put_char(), and
> getchark(). The _IO_Vprintf() belongs to the test code.
>

Ok.  Feel free.to.movr forward.

And fwiw that method is the most uncovered code in the score. It doesn't
have good test coverage.

--joel

>
> --
> 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: Error when trying to build llvm

2021-07-30 Thread 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

Re: Error when trying to build llvm

2021-07-30 Thread Joel Sherrill 
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 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