Re: [PATCH v2] Rework RTEMS licensing discussions.

On Thu, Apr 30, 2020 at 3:57 PM Joel Sherrill wrote: > > This now captures historical rationale alone with cross-linking > code templates with license guidelines. > > Closes #3962. > --- > eng/coding-conventions.rst | 19 ++- > eng/license-requirements.rst | 81 > ++

Re: [PATCH v2] Rework RTEMS licensing discussions.

Thanks this looks good. Slap my copyright on it too though, I think half the text was lifted from my blog :) On Thu, Apr 30, 2020 at 6:53 PM Chris Johns wrote: > > On 1/5/20 10:11 am, Joel Sherrill wrote: > > On Thu, Apr 30, 2020, 6:18 PM Chris Johns > > wrote: > > > >

Re: RTEMS 5 Release status

On Tue, Apr 28, 2020, 7:28 PM Chris Johns wrote: > Hello, > > We are down to 4 remaining tickets. Many thanks to everyone for all the > hard work getting to this point. It is appreciated. > > The remaining tickets need to be closed or moved before I can branch the > repos. The milestone page is .

Re: RTEMS 5 Release status

On 29/4/20 6:00 pm, Chris Johns wrote: Also I have currently backed away from a full markdown for the generated README.txt. It was creating some issues that require more work than is needed and it is not critical. It can be revisited as part of the on going support work. After saying I would

Re: [PATCH v2] Rework RTEMS licensing discussions.

On 1/5/20 10:11 am, Joel Sherrill wrote: On Thu, Apr 30, 2020, 6:18 PM Chris Johns > wrote: Hi Joel, This looks good, thanks. I am wondering about references to the wiki and to a "To Be Reviewed" (TBR) page being placed in the documentation. I copied

Re: [PATCH v2] Rework RTEMS licensing discussions.

On Thu, Apr 30, 2020, 6:18 PM Chris Johns wrote: > Hi Joel, > > This looks good, thanks. > > I am wondering about references to the wiki and to a "To Be Reviewed" > (TBR) page being placed in the documentation. I copied that and didn't notice that. There should be a permanent link. And the TBD

Re: [PATCH v2] Rework RTEMS licensing discussions.

Hi Joel, This looks good, thanks. I am wondering about references to the wiki and to a "To Be Reviewed" (TBR) page being placed in the documentation. A released PDF may not have access to the web. For license links should a copy be added to the document therefore held and maintained across re

[PATCH v2] Licensing Information Rework (#3962)

I figured out why the cross-references did not work. I simplified the text in Coding Conventions and put more meat in Licensing Requirements including rationale. Please review and comment. Joel Sherrill (1): Rework RTEMS licensing discussions. eng/coding-conventions.rst | 19 ++-

[PATCH v2] Rework RTEMS licensing discussions.

This now captures historical rationale alone with cross-linking code templates with license guidelines. Closes #3962. --- eng/coding-conventions.rst | 19 ++- eng/license-requirements.rst | 81 +--- 2 files changed, 86 insertions(+), 14 deletions(

Licensing Requirements Rework (#3962)

Hi Attached is a patch which reworks the license text. I think it is an improvement overall but I can't get the cross-references to work. Please proofread the attached patch and give me some help on the cross-references. Thanks. --joel 0001-Rework-RTEMS-licensing-discussions.patch Description

Re: source builder, bsp arch settings

Hello everyone! Apologies for breaking the chain of this conversation. I have also been working (read struggling) on adding libbsd and ntp support for RTEMS+EPICS on xilinx_zynq_a9_qemu and trying to figure out what files in /rtems/rtems-libbsd and /rtems/rsb/source-builder/, I have to begin with.

Re: rtems assembler

On Thu, 30 Apr 2020 at 15:56, suyash singh wrote: > after adding -v > https://hastebin.com/epijunegix.coffeescript > > with sparc-unknown-elf > https://hastebin.com/ijohidofus.coffeescript > > (target getting an extra unknown for some reason) > > riscv64-unknown-elf > https://hastebin.com/jirusid

Re: rtems assembler

after adding -v https://hastebin.com/epijunegix.coffeescript with sparc-unknown-elf https://hastebin.com/ijohidofus.coffeescript (target getting an extra unknown for some reason) riscv64-unknown-elf https://hastebin.com/jirusidoti.sql different error: unknown register name (maybe because erc32

Re: rtems assembler

On Thu, 30 Apr 2020 at 15:21, suyash singh wrote: > I think it doesn't support sparc backend although it does not give unknown > target error. > > I compiled this c program with > export PATH=$HOME/quick-start/rtems/5/bin:"$PATH" > clang -target sparc-unknown-rtems5 test1.c > Can you add -v to t

Re: rtems assembler

oh I mean for target which does not exist like "hello" it says "unknown target" I wrote that as example to say that sparc-unknown-rtems5 is detected as valid target but not used On Thu, Apr 30, 2020 at 7:52 PM Joel Sherrill wrote: > > > On Thu, Apr 30, 2020 at 9:21 AM suyash singh > wrote: > >

Re: rtems assembler

On Thu, Apr 30, 2020 at 9:21 AM suyash singh wrote: > I think it doesn't support sparc backend although it does not give unknown > target error. > > I compiled this c program with > export PATH=$HOME/quick-start/rtems/5/bin:"$PATH" > clang -target sparc-unknown-rtems5 test1.c > > *test1.c* > int

Re: rtems assembler

I think it doesn't support sparc backend although it does not give unknown target error. I compiled this c program with export PATH=$HOME/quick-start/rtems/5/bin:"$PATH" clang -target sparc-unknown-rtems5 test1.c *test1.c* int main(int argc, char **argv) { int k = 0x7fff; k += argc; re

Re: rtems assembler

On Thu, 30 Apr 2020 at 14:18, suyash singh wrote: > > I am using ubuntu 18.04 terminal > > Here's the python script I wrote to find all include files and run clang > -fsanitize > > # run with python3 in terminal > > import subprocess > import os > > relativedir="../bsps/sparc/erc32/btimer" > dire

Re: rtems assembler

I am using ubuntu 18.04 terminal Here's the python script I wrote to find all include files and run clang -fsanitize # run with python3 in terminal import subprocess import os relativedir="../bsps/sparc/erc32/btimer" directory=os.path.join(os.getcwd(),"../") file="btimer.c" root_dir="ubsan" ar

Re: rtems assembler

On Thu, 30 Apr 2020 at 13:51, Joel Sherrill wrote: > > > On Thu, Apr 30, 2020 at 7:34 AM suyash singh > wrote: > >> Hello, >> I was running clang UBSan on >> bsps/sparc/erc32/btimer/btimer.c >> >> and got error >> >> /usr/bin/as: unrecognized option '-Av8' >> clang-11: error: assembler command f

Re: rtems assembler

On Thu, 30 Apr 2020 at 13:34, suyash singh wrote: > Hello, > I was running clang UBSan on > bsps/sparc/erc32/btimer/btimer.c > What’s the command line you're using? > and got error > > /usr/bin/as: unrecognized option '-Av8' > clang-11: error: assembler command failed with exit code 1 > > I am

Re: rtems assembler

On Thu, Apr 30, 2020 at 7:34 AM suyash singh wrote: > Hello, > I was running clang UBSan on > bsps/sparc/erc32/btimer/btimer.c > > and got error > > /usr/bin/as: unrecognized option '-Av8' > clang-11: error: assembler command failed with exit code 1 > > I am not sure but is it because clang is us

rtems assembler

Hello, I was running clang UBSan on bsps/sparc/erc32/btimer/btimer.c and got error /usr/bin/as: unrecognized option '-Av8' clang-11: error: assembler command failed with exit code 1 I am not sure but is it because clang is using wrong assembler? ___ de