[PATCH] wscript: fix default version from 4.12 to 5

--- wscript | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wscript b/wscript index f3c8304..f32fb8d 100644 --- a/wscript +++ b/wscript @@ -17,7 +17,7 @@ # to build for more than BSP at a time. # -rtems_version = "4.12" +rtems_version = "5" try: import rtems_waf.rtems

Re: no-preinstall: Ready for final review

On Wed, Jan 17, 2018 at 2:24 AM, Sebastian Huber wrote: > Hello, > > the no-preinstall branch is now in a good shape. > > https://git.rtems.org/sebh/rtems.git/log/?h=no-preinstall > > Please review this work. The next step would be to squash all commits on > this branch, write a proper commit mess

Re: no-preinstall: Ready for final review

I fixed the cpuopts.h problem two minutes ago. - Gedare Bloom schrieb: > On Wed, Jan 17, 2018 at 2:24 AM, Sebastian Huber > wrote: > > Hello, > > > > the no-preinstall branch is now in a good shape. > > > > https://git.rtems.org/sebh/rtems.git/log/?h=no-preinstall > > > > Please review this

Re: no-preinstall: Ready for final review

On Thu, Jan 18, 2018 at 10:20 AM, Sebastian Huber wrote: > I fixed the cpuopts.h problem two minutes ago. > Thanks. I just noticed that actually when I run tester on the installed tree I get a lot of timeouts. I'm not sure if this is my host problem. > - Gedare Bloom schrieb: >> On Wed, Jan

Re: no-preinstall: Ready for final review

On Thu, Jan 18, 2018 at 10:34 AM, Gedare Bloom wrote: > On Thu, Jan 18, 2018 at 10:20 AM, Sebastian Huber > wrote: >> I fixed the cpuopts.h problem two minutes ago. >> > Thanks. > > I just noticed that actually when I run tester on the installed tree I > get a lot of timeouts. I'm not sure if thi

Re: no-preinstall: Ready for final review

Is this after installation or during the BSP build? - Am 18. Jan 2018 um 17:19 schrieb Gedare Bloom ged...@rtems.org: > On Thu, Jan 18, 2018 at 10:34 AM, Gedare Bloom wrote: >> On Thu, Jan 18, 2018 at 10:20 AM, Sebastian Huber >> wrote: >>> I fixed the cpuopts.h problem two minutes ago. >>>

Re: no-preinstall: Ready for final review

v1 of the commit message: Remove make preinstall A speciality of the RTEMS build system was the make preinstall step. It copied header files from arbitrary locations into the build tree. The header files were included via the -Bsome/build/tree/path GCC command line option. This has at least fi

Re: no-preinstall: Ready for final review

After installation. The BSP builds fine On Thu, Jan 18, 2018 at 11:33 AM, Sebastian Huber wrote: > Is this after installation or during the BSP build? > > - Am 18. Jan 2018 um 17:19 schrieb Gedare Bloom ged...@rtems.org: > >> On Thu, Jan 18, 2018 at 10:34 AM, Gedare Bloom wrote: >>> On Thu,

Re: no-preinstall: Ready for final review

- Am 18. Jan 2018 um 16:06 schrieb Gedare Bloom ged...@rtems.org: [...] > I also took a quick look through the commits, and I have a small nit. > Might I suggest "headers.sh" and "headers.am" instead of "header.sh" > and "header.am"? I want to add this stuff to the bootstrap script as a -p

Re: no-preinstall: Ready for final review

On Thu, Jan 18, 2018 at 11:36 AM, Sebastian Huber wrote: > > > - Am 18. Jan 2018 um 16:06 schrieb Gedare Bloom ged...@rtems.org: > > [...] >> I also took a quick look through the commits, and I have a small nit. >> Might I suggest "headers.sh" and "headers.am" instead of "header.sh" >> and "he

Re: no-preinstall: Ready for final review

- Gedare Bloom schrieb: > On Thu, Jan 18, 2018 at 11:36 AM, Sebastian Huber > wrote: > > > > > > - Am 18. Jan 2018 um 16:06 schrieb Gedare Bloom ged...@rtems.org: > > > > [...] > >> I also took a quick look through the commits, and I have a small nit. > >> Might I suggest "headers.sh" an

Re: [PATCH] gcc: Reference GNU's FTP site for all GCC parts.

On Wed, Jan 17, 2018 at 6:39 PM, Chris Johns wrote: > On 18/1/18 11:01 am, Joel Sherrill wrote: > > On Wed, Jan 17, 2018 at 5:21 PM, Chris Johns > > wrote: > > > > On 18/1/18 9:30 am, Joel Sherrill wrote: > > > Why can't we change it to here for 4.10? > > > >

Re: no-preinstall: Ready for final review

On 19/1/18 3:35 am, Sebastian Huber wrote: > v1 of the commit message: Looks good. Best to limit the number of problems with preinstalling to just 5 :) Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: no-preinstall: Ready for final review

On 19/1/18 3:37 am, Gedare Bloom wrote: > On Thu, Jan 18, 2018 at 11:36 AM, Sebastian Huber > wrote: >> >> >> - Am 18. Jan 2018 um 16:06 schrieb Gedare Bloom ged...@rtems.org: >> >> [...] >>> I also took a quick look through the commits, and I have a small nit. >>> Might I suggest "headers.sh"

Re: no-preinstall: Ready for final review

On Thu, Jan 18, 2018 at 3:34 PM, Chris Johns wrote: > On 19/1/18 3:37 am, Gedare Bloom wrote: >> On Thu, Jan 18, 2018 at 11:36 AM, Sebastian Huber >> wrote: >>> >>> >>> - Am 18. Jan 2018 um 16:06 schrieb Gedare Bloom ged...@rtems.org: >>> >>> [...] I also took a quick look through the co

Re: [PATCH] gcc: Reference GNU's FTP site for all GCC parts.

On 19/1/18 4:48 am, Joel Sherrill wrote: > > > On Wed, Jan 17, 2018 at 6:39 PM, Chris Johns > wrote: > > On 18/1/18 11:01 am, Joel Sherrill wrote: > > On Wed, Jan 17, 2018 at 5:21 PM, Chris Johns > >

Re: [PATCH] rtems: Remove unused configuration files.

The RSB policy with respect to configuration files is not clear to me. I thought these are read-only files that will be never removed? If you want to keep only the files used by the build sets, then why do they have file names with a version included? Are branches in the RSB really practical?

Re: no-preinstall: Ready for final review

On 18/01/18 21:57, Gedare Bloom wrote: On Thu, Jan 18, 2018 at 3:34 PM, Chris Johns wrote: On 19/1/18 3:37 am, Gedare Bloom wrote: On Thu, Jan 18, 2018 at 11:36 AM, Sebastian Huber wrote: - Am 18. Jan 2018 um 16:06 schrieb Gedare bloomged...@rtems.org: [...] I also took a quick look t

RTEMS Tester and Log Files

Hello, the RTEMS Tester works quite well if it can run the tests step by step. I have a board were I can run reliably all tests at once with a custom script. I cannot run tests individually due to an instability in the debug support. This produces a large text file with the test output of all

no-preinstall: Architecture-specific header files

Hello, the architecture-specific header files are currently in: cpukit/score/cpu/@RTEMS_CPU@ For example: cpukit/score/cpu/sparc/rtems/score/cpu.h The new include directory for architecture-specific header files after the preinstall removal is: cpukit/score/cpu/@RTEMS_CPU@/include For exa