Re: lpc40xx BSPs do not build on master

[Sebastian Huber]

On 15/01/18 18:53, Joel Sherrill wrote:

Hi

I'm not sure what broke but neither lpc40xx_ea_ram nor lpc40xx_ea_rom 
build.


I cannot reproduce this problem. Which error do you get?

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

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

Re: lpc40xx BSPs do not build on master

[Joel Sherrill]

On Tue, Jan 16, 2018 at 3:29 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 15/01/18 18:53, Joel Sherrill wrote:
>
>> Hi
>>
>> I'm not sure what broke but neither lpc40xx_ea_ram nor lpc40xx_ea_rom
>> build.
>>
>
> I cannot reproduce this problem. Which error do you get?


Hmmm... I neglected to mention that I am using gcc master also. Sorry.

One of the configure conftest.c probes is failing with an object
architecture
variant mismatch.

configure:3595: arm-rtems5-gcc -mthumb -march=armv7-m -mfpu=fpv4-sp-d16
-mfloat-abi=hard -mtune=cortex-m4 -O2 -g -ffunction-sections
-fdata-sections   conftest.c  >&5
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld:
error: /tmp/cckWAYRI.o uses VFP register arguments, a.out does not
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld:
failed to merge target specific data of file /tmp/cckWAYRI.o
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld:
warning: cannot find entry symbol _start; defaulting to 8018
collect2: error: ld returned 1 exit status

With gcc 8.0 trying to head to a freeze, I wonder if you could take a look
at it Sebastian.

--joel


>
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, G
> 
> ermany
> Phone   : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail  : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

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

[Chris Johns]

Close #3272
---
 source-builder/config/gcc-4.3-1.cfg | 6 +++---
 source-builder/config/gcc-4.4-1.cfg | 6 +++---
 source-builder/config/gcc-4.5-1.cfg | 6 +++---
 source-builder/config/gcc-4.6-1.cfg | 6 +++---
 source-builder/config/gcc-4.7-1.cfg | 6 +++---
 source-builder/config/gcc-4.8-1.cfg | 6 +++---
 source-builder/config/gcc-4.9-1.cfg | 6 +++---
 source-builder/config/gcc-6-1.cfg   | 6 +++---
 8 files changed, 24 insertions(+), 24 deletions(-)

diff --git a/source-builder/config/gcc-4.3-1.cfg 
b/source-builder/config/gcc-4.3-1.cfg
index a7b825b..bf78822 100644
--- a/source-builder/config/gcc-4.3-1.cfg
+++ b/source-builder/config/gcc-4.3-1.cfg
@@ -26,9 +26,9 @@
 #
 # Packages GCC requires
 #
-%source set mpfr 
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc 
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
+%source set mpfr https://ftp.gnu.org/gnu/mpfr/mpfr-%{mpfr_version}.tar.bz2
+%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
+%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
 
 #
 # GCC Common build script.
diff --git a/source-builder/config/gcc-4.4-1.cfg 
b/source-builder/config/gcc-4.4-1.cfg
index 077792a..ecfa651 100644
--- a/source-builder/config/gcc-4.4-1.cfg
+++ b/source-builder/config/gcc-4.4-1.cfg
@@ -25,9 +25,9 @@
 #
 # Packages GCC requires
 #
-%source set mpfr 
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc 
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
+%source set mpfr https://ftp.gnu.org/gnu/mpfr/mpfr-%{mpfr_version}.tar.bz2
+%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
+%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
 
 #
 # GCC Common build script.
diff --git a/source-builder/config/gcc-4.5-1.cfg 
b/source-builder/config/gcc-4.5-1.cfg
index 0039f68..acca717 100644
--- a/source-builder/config/gcc-4.5-1.cfg
+++ b/source-builder/config/gcc-4.5-1.cfg
@@ -21,9 +21,9 @@
 #
 # Packages GCC requires
 #
-%source set mpfr 
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc 
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
+%source set mpfr https://ftp.gnu.org/gnu/mpfr/mpfr-%{mpfr_version}.tar.bz2
+%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
+%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
 
 #
 # GCC Common build script.
diff --git a/source-builder/config/gcc-4.6-1.cfg 
b/source-builder/config/gcc-4.6-1.cfg
index da5c0ab..4eff844 100644
--- a/source-builder/config/gcc-4.6-1.cfg
+++ b/source-builder/config/gcc-4.6-1.cfg
@@ -25,9 +25,9 @@
 #
 # Packages GCC requires
 #
-%source set mpfr 
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc 
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
+%source set mpfr https://ftp.gnu.org/gnu/mpfr/mpfr-%{mpfr_version}.tar.bz2
+%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
+%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
 
 #
 # GCC Common build script.
diff --git a/source-builder/config/gcc-4.7-1.cfg 
b/source-builder/config/gcc-4.7-1.cfg
index 923ef12..25ac233 100644
--- a/source-builder/config/gcc-4.7-1.cfg
+++ b/source-builder/config/gcc-4.7-1.cfg
@@ -30,9 +30,9 @@
 #
 # Packages GCC requires
 #
-%source set mpfr 
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc 
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
+%source set mpfr https://ftp.gnu.org/gnu/mpfr/mpfr-%{mpfr_version}.tar.bz2
+%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
+%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
 
 #
 # GCC Common build script.
diff --git a/source-builder/config/gcc-4.8-1.cfg 
b/source-builder/config/gcc-4.8-1.cfg
index 56074b0..a090717 100644
--- a/source-builder/config/gcc-4.8-1.cfg
+++ b/source-builder/config/gcc-4.8-1.cfg
@@ -21,9 +21,9 @@
 #
 # Packages GCC requires
 #
-%source set mpfr 
http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_version}.tar.bz2
-%source set mpc 
http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
-%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
+%source set mpfr https://ftp.gnu.org/gnu/mpfr/mpfr-%{mpfr_version}.tar.bz2
+%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
+%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
 
 #
 # GCC Common build script.
diff --git a/source-builder/config/gcc-4.9-1.cfg 
b/

RSB release's default mode for building kernels

[Chris Johns]

Hi,

The current mode on all release branches is to build the RTEMS kernel. The
purpose was to have a single command that builds the tools and RTEMS. However
this means all BSPs for an architecture are built and this is not practical
because it slows a build and uses a larger amount of disk space when an
architecture has a larger number of BSPs so I am wondering if the default is
reversed.

Comments?

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

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

[Joel Sherrill]

Looks good to me.



On Tue, Jan 16, 2018 at 4:19 PM, Chris Johns  wrote:

> Close #3272
> ---
>  source-builder/config/gcc-4.3-1.cfg | 6 +++---
>  source-builder/config/gcc-4.4-1.cfg | 6 +++---
>  source-builder/config/gcc-4.5-1.cfg | 6 +++---
>  source-builder/config/gcc-4.6-1.cfg | 6 +++---
>  source-builder/config/gcc-4.7-1.cfg | 6 +++---
>  source-builder/config/gcc-4.8-1.cfg | 6 +++---
>  source-builder/config/gcc-4.9-1.cfg | 6 +++---
>  source-builder/config/gcc-6-1.cfg   | 6 +++---
>  8 files changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/source-builder/config/gcc-4.3-1.cfg
> b/source-builder/config/gcc-4.3-1.cfg
> index a7b825b..bf78822 100644
> --- a/source-builder/config/gcc-4.3-1.cfg
> +++ b/source-builder/config/gcc-4.3-1.cfg
> @@ -26,9 +26,9 @@
>  #
>  # Packages GCC requires
>  #
> -%source set mpfr http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_
> version}.tar.bz2
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz
> -%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
> +%source set mpfr https://ftp.gnu.org/gnu/mpfr/
> mpfr-%{mpfr_version}.tar.bz2
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
> +%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
>
>  #
>  # GCC Common build script.
> diff --git a/source-builder/config/gcc-4.4-1.cfg
> b/source-builder/config/gcc-4.4-1.cfg
> index 077792a..ecfa651 100644
> --- a/source-builder/config/gcc-4.4-1.cfg
> +++ b/source-builder/config/gcc-4.4-1.cfg
> @@ -25,9 +25,9 @@
>  #
>  # Packages GCC requires
>  #
> -%source set mpfr http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_
> version}.tar.bz2
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz
> -%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
> +%source set mpfr https://ftp.gnu.org/gnu/mpfr/
> mpfr-%{mpfr_version}.tar.bz2
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
> +%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
>
>  #
>  # GCC Common build script.
> diff --git a/source-builder/config/gcc-4.5-1.cfg
> b/source-builder/config/gcc-4.5-1.cfg
> index 0039f68..acca717 100644
> --- a/source-builder/config/gcc-4.5-1.cfg
> +++ b/source-builder/config/gcc-4.5-1.cfg
> @@ -21,9 +21,9 @@
>  #
>  # Packages GCC requires
>  #
> -%source set mpfr http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_
> version}.tar.bz2
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz
> -%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
> +%source set mpfr https://ftp.gnu.org/gnu/mpfr/
> mpfr-%{mpfr_version}.tar.bz2
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
> +%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
>
>  #
>  # GCC Common build script.
> diff --git a/source-builder/config/gcc-4.6-1.cfg
> b/source-builder/config/gcc-4.6-1.cfg
> index da5c0ab..4eff844 100644
> --- a/source-builder/config/gcc-4.6-1.cfg
> +++ b/source-builder/config/gcc-4.6-1.cfg
> @@ -25,9 +25,9 @@
>  #
>  # Packages GCC requires
>  #
> -%source set mpfr http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_
> version}.tar.bz2
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz
> -%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
> +%source set mpfr https://ftp.gnu.org/gnu/mpfr/
> mpfr-%{mpfr_version}.tar.bz2
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
> +%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
>
>  #
>  # GCC Common build script.
> diff --git a/source-builder/config/gcc-4.7-1.cfg
> b/source-builder/config/gcc-4.7-1.cfg
> index 923ef12..25ac233 100644
> --- a/source-builder/config/gcc-4.7-1.cfg
> +++ b/source-builder/config/gcc-4.7-1.cfg
> @@ -30,9 +30,9 @@
>  #
>  # Packages GCC requires
>  #
> -%source set mpfr http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_
> version}.tar.bz2
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz
> -%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
> +%source set mpfr https://ftp.gnu.org/gnu/mpfr/
> mpfr-%{mpfr_version}.tar.bz2
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
> +%source set gmp https://ftp.gnu.org/gnu/gmp/gmp-%{gmp_version}.tar.bz2
>
>  #
>  # GCC Common build script.
> diff --git a/source-builder/config/gcc-4.8-1.cfg
> b/source-builder/config/gcc-4.8-1.cfg
> index 56074b0..a090717 100644
> --- a/source-builder/config/gcc-4.8-1.cfg
> +++ b/source-builder/config/gcc-4.8-1.cfg
> @@ -21,9 +21,9 @@
>  #
>  # Packages GCC requires
>  #
> -%source set mpfr http://www.mpfr.org/mpfr-%{mpfr_version}/mpfr-%{mpfr_
> version}.tar.bz2
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
> version}.tar.gz
> -%source set gmp ftp://ftp.gnu.org/gnu/gmp/gmp-%{

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

[Chris Johns]

On 17/1/18 9:32 am, Joel Sherrill wrote:
> Looks good to me.

FYI this is for 4.10. We need this to make a release.

Chris

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

Re: RSB release's default mode for building kernels

[Joel Sherrill]

On Tue, Jan 16, 2018 at 4:27 PM, Chris Johns  wrote:

> Hi,
>
> The current mode on all release branches is to build the RTEMS kernel. The
> purpose was to have a single command that builds the tools and RTEMS.
> However
> this means all BSPs for an architecture are built and this is not practical
> because it slows a build and uses a larger amount of disk space when an
> architecture has a larger number of BSPs so I am wondering if the default
> is
> reversed.
>

I think RTEMS itself should not be built as part of the tools.

You can't win. You are building BSPs that are not wanted, likely in a
configuration that isn't the users, and not being able to test on end user
hardware while doing it.  Best not to build them. Users expect to build
their own RTEMS and we need to encourage them to test and report.

--joel

>
> Comments?
>
> Chris
> ___
> 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/2] arm: ARM on a recent FreeBSD fails to build.

[Chris Johns]

- See #2439 for details.

Update #3262
---
 rtems/config/4.10/rtems-arm.bset | 11 ++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/rtems/config/4.10/rtems-arm.bset b/rtems/config/4.10/rtems-arm.bset
index 35874db..3da910b 100644
--- a/rtems/config/4.10/rtems-arm.bset
+++ b/rtems/config/4.10/rtems-arm.bset
@@ -4,4 +4,13 @@
 
 %define release 1
 %define rtems_arch arm
-%include 4.10/rtems-defaults.bset
+
+%include rtems-base.bset
+
+4.10/rtems-autotools
+
+devel/expat-2.1.0-1
+tools/rtems-binutils-2.26-1
+tools/rtems-gcc-4.4.7-newlib-1.18.0-1
+tools/rtems-gdb-7.11-1
+tools/rtems-kernel-4.10
-- 
2.14.1

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

[PATCH 1/2] gcc: Add GCC option to build on Linux and do not build the texinfo.

[Chris Johns]

- GCC on recent Linux systems needs `-fgnu89-inline` to build.
- Disable building texinfo. Makeinfo on some hosts breaks the build.

Update #3262
---
 source-builder/config/gcc-common-1.cfg | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/source-builder/config/gcc-common-1.cfg 
b/source-builder/config/gcc-common-1.cfg
index 941e15c..0bf59b6 100644
--- a/source-builder/config/gcc-common-1.cfg
+++ b/source-builder/config/gcc-common-1.cfg
@@ -31,6 +31,16 @@ BuildRoot: %{_tmppath}/%{name}-root-%(%{__id_u} -n)
 #
 %global _gcclibdir %{_prefix}/lib
 
+#
+# Update the build flags need to build the older gcc with newer compilers.
+#
+%define build_cflags %{build_cflags} -fgnu89-inline
+
+#
+# Do not build GCC doco, it seems to break with age.
+#
+%define disable_MAKEINFO 1
+
 #
 # Prepare the source code.
 #
@@ -151,6 +161,7 @@ BuildRoot: %{_tmppath}/%{name}-root-%(%{__id_u} -n)
 --enable-version-specific-runtime-libs \
 --disable-lto \
 --enable-newlib-io-c99-formats \
+%{?disable_MAKEINFO:MAKEINFO=missing} \
 %{?with_iconv:--enable-newlib-iconv} \
 %{?with_iconv:--enable-newlib-iconv-encodings=%{_newlib_iconv_encodings}} \
 %{?with_threads:--enable-threads}%{!?with_threads:--disable-threads} \
-- 
2.14.1

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

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

[Joel Sherrill]

On Tue, Jan 16, 2018 at 4:34 PM, Chris Johns  wrote:

> On 17/1/18 9:32 am, Joel Sherrill wrote:
> > Looks good to me.
>
> FYI this is for 4.10. We need this to make a release.
>

Shouldn't we also be doing this for 4.11 and 5.0 or have those already
switched to gcc?


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

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

[Chris Johns]

On 17/1/18 9:35 am, Joel Sherrill wrote:
> Shouldn't we also be doing this for 4.11 and 5.0 or have those already 
> switched to gcc?

5 is already ok and the 4.11 patch is:

https://lists.rtems.org/pipermail/devel/2018-January/019911.html

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

Re: lpc40xx BSPs do not build on master

[Chris Johns]

On 16/1/18 11:17 am, Joel Sherrill wrote:
> I have most of the architectures and targets building with empty bsp_spec 
> files.

It is not clear to me how this change and the no-preinstall changes will
interact, that is which is pushed to master first.

The BSP spec files themselves are not touched in the no-preinstall branch, in
fact the only place they are referenced is linking the samples and tests and
installing.

Chris

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

Re: lpc40xx BSPs do not build on master

[Joel Sherrill]

FWIW arm gcc 8 is the culprit. I have confirmed it with an unmodified RTEMS
master.

lpc40xx_ea_r* do not build with gcc 8/master and RTEMS master.

configure:3595: arm-rtems5-gcc -mthumb -march=armv7-m -mfpu=fpv4-sp-d16
-mfloat-abi=hard -mtune=cortex-m4 -O2 -g -ffunction-sections
-fdata-sections   conftest.c  >&5
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld:
error: /tmp/ccZTj7BL.o uses VFP register arguments, a.out does not
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld:
failed to merge target specific data of file /tmp/ccZTj7BL.o
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld:
warning: cannot find entry symbol _start; defaulting to 8018
collect2: error: ld returned 1 exit status


On Tue, Jan 16, 2018 at 5:15 PM, Chris Johns  wrote:

> On 16/1/18 11:17 am, Joel Sherrill wrote:
> > I have most of the architectures and targets building with empty
> bsp_spec files.
>
> It is not clear to me how this change and the no-preinstall changes will
> interact, that is which is pushed to master first.
>
> The BSP spec files themselves are not touched in the no-preinstall branch,
> in
> fact the only place they are referenced is linking the samples and tests
> and
> installing.
>

I think they are orthogonal changes. Unfortunately, emptying the bsp_specs
files requires modifying the built in info in gcc. Some of which was just
right
enough to configure anyway. That's why we had to have bsp_specs to build
real applications.

My plan is that once they are all empty, I can then add the patches to not
use
them and them remove them.

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

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

[Chris Johns]

On 17/1/18 9:19 am, Chris Johns wrote:
> -%source set mpc 
> http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz

This does not work for 4.10 as GNU only hosts mpc-1.0.1 and later and 4.10 uses
0.8.1.

Do we update MPC etc to use GNU hosted version?

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

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

[Joel Sherrill]

On Jan 16, 2018 6:50 PM, "Chris Johns"  wrote:

On 17/1/18 9:19 am, Chris Johns wrote:
> -%source set mpc http://www.multiprecision.org/mpc/download/mpc-%{mpc_
version}.tar.gz
> +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz

This does not work for 4.10 as GNU only hosts mpc-1.0.1 and later and 4.10
uses
0.8.1.

Do we update MPC etc to use GNU hosted version?


That seems potentially dangerous. It could unintentionally change the
toolset behavior.

What was the recommended version with that GCC version? Any idea?

Can we host the required version? Isn't it already on our ftp site since
you unrolled all the source RPMs?


Chris
___
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] gcc: Update the MPC part of gcc to 1.0.3 as it is available on GNU's FTP.

[Chris Johns]

Update #3262
---
 rtems/config/tools/rtems-gcc-4.4.7-newlib-1.18.0-1.cfg | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rtems/config/tools/rtems-gcc-4.4.7-newlib-1.18.0-1.cfg 
b/rtems/config/tools/rtems-gcc-4.4.7-newlib-1.18.0-1.cfg
index 4a852a5..3958e04 100644
--- a/rtems/config/tools/rtems-gcc-4.4.7-newlib-1.18.0-1.cfg
+++ b/rtems/config/tools/rtems-gcc-4.4.7-newlib-1.18.0-1.cfg
@@ -16,7 +16,7 @@
 %define gcc_version4.4.7
 %define newlib_version 1.18.0
 %define mpfr_version   2.4.2
-%define mpc_version0.8.1
+%define mpc_version1.0.3
 %define gmp_version5.0.5
 
 %define with_threads 1
@@ -33,7 +33,7 @@
 # Hash checksums of the libraries used in GCC.
 #
 %hash md5 mpfr-%{mpfr_version}.tar.bz2 89e59fe665e2b3ad44a6789f40b059a0
-%hash md5 mpc-%{mpc_version}.tar.gz5b34aa804d514cc295414a963aedb6bf
+%hash md5 mpc-%{mpc_version}.tar.gzd6a1d5f8ddea3abd2cc3e98f58352d26
 %hash md5 gmp-%{gmp_version}.tar.bz2   041487d25e9c230b0c42b106361055fe
 
 #
-- 
2.14.1

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

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

[Chris Johns]

On 17/1/18 1:04 pm, Joel Sherrill wrote:
> On Jan 16, 2018 6:50 PM, "Chris Johns"  > wrote:
> 
> On 17/1/18 9:19 am, Chris Johns wrote:
> > -%source set mpc
> http://www.multiprecision.org/mpc/download/mpc-%{mpc_version}.tar.gz
> 
> > +%source set mpc https://ftp.gnu.org/gnu/mpc/mpc-%{mpc_version}.tar.gz
> 
> 
> This does not work for 4.10 as GNU only hosts mpc-1.0.1 and later and 
> 4.10 uses
> 0.8.1.
> 
> Do we update MPC etc to use GNU hosted version?
> 
> 
> That seems potentially dangerous. It could unintentionally change the toolset
> behavior. 

I do not know. It would depend on how this package is used in gcc-4.4.7.

> 
> What was the recommended version with that GCC version? Any idea?
> 

I do not know.

> Can we host the required version? Isn't it already on our ftp site since you
> unrolled all the source RPMs?

We host all source in a release on the RTEMS FTP site as part of the release and
RSB releases know to use the RTEMS FTP site by default. The issue is creating a
releases requires the source be present on the project's specified home site.
This means we cannot make a release if the source cannot be found.

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

Re: Hello World patch

[Vidushi Vashishth]

Hello!

I sent the patch to Gedare Bloom. The student tracking table is not
editable yet I think. Thanks for the list of projects. I will shortly get
back to you on which project I would contribute to.

Best,
Vidushi

On Tue, Jan 16, 2018 at 3:05 AM, Joel Sherrill  wrote:

>
>
> On Mon, Jan 15, 2018 at 2:20 PM, Christian Mauderer <
> christian.maude...@embedded-brains.de> wrote:
>
>> - Ursprüngliche Mail -
>> > Von: "Vidushi Vashishth" 
>> > An: "RTEMS Devel" 
>> > Gesendet: Montag, 15. Januar 2018 06:17:53
>> > Betreff: Hello World patch
>>
>> > Hi!
>> >
>> > I have the hello world patch and screenshot. Whom should I send it to?
>> >
>> > Best,
>> > Vidushi
>> >
>> > ___
>> > devel mailing list
>> > devel@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>>
>> Hello Vidushi,
>>
>> I assume that you think of the patch and screenshot from the GSoC Getting
>> Started guide (https://devel.rtems.org/wiki/GSoC/GettingStarted)? In
>> that case: Quite a number of last years student's have sent that to the
>> mailing list. But I think you can also send it to Gedare Bloom directly. If
>> you send it to the list, please make sure that your screenshot isn't too
>> big. There is a size limit on the mailing list (I think around 100 or 200k)
>> and it will be delivered to a lot of people.
>>
>
> Sending it to Gedare or myself is fine.
>
> Also there is a student tracking page at https://devel.rtems.org/wik
> i/GSoC/2018 with a table you should add yourself to. You can leave the
> project TBD for now. But we can discuss project ideas
>
>
>>
>> It's really great that you are interested in working with us but please
>> note that you are quite early. Not everything is set up yet for GSoC2018.
>> For example a lot of wiki pages are still only updated partially. Beneath
>> that Google didn't even publish it's list of accepted organizations but we
>> had no problems in the last years so I would be quite optimistic.
>>
>> Of course you can already start to bond with the community. If you
>> already have project ideas you should discuss them with potential mentors
>> or - if you have no idea who might could be a mentor - discuss them on the
>> mailing list. If you don't have ideas, you can take a look over
>> https://devel.rtems.org/wiki/Developer/OpenProjects.
>>
>
> Christian is correct. It is quite early. We have applied and I have made a
> suggestion on what I personally think are the highest priority projects
> from an RTEMS project perspective. But that doesn't mean all have mentors
> or that someone in the community or a student doesn't have other ideas.
>
> My personal starting list for high priority projects was:
>
> + Wifi integration improvements (assuming Christian mentors)
> + aarch64 port
> + non-legacy PC support
> + coverage reporting changes and gcov support improvements
> + Eclipse target support for tracing and gdb (TCF?)
>
> I am sure there are other projects of merit. Those were just the ones off
> the top of my head.
>
> The Open Project page is a good place to start looking but some projects
> have had progress on them and others are possibly no longer relevant.
>
> --joel
>
>
>>
>> Best regards
>>
>> Christian Mauderer
>> --
>> 
>> embedded brains GmbH
>> Christian Mauderer
>> Dornierstr. 4
>> 
>> D-82178 Puchheim
>> Germany
>> email: christian.maude...@embedded-brains.de
>> Phone: +49-89-18 94 741 - 18
>> Fax:   +49-89-18 94 741 - 08
>> PGP: Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>> ___
>> 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: lpc40xx BSPs do not build on master

[Sebastian Huber]

On 16/01/18 16:38, Joel Sherrill wrote:



On Tue, Jan 16, 2018 at 3:29 AM, Sebastian Huber 
> wrote:


On 15/01/18 18:53, Joel Sherrill wrote:

Hi

I'm not sure what broke but neither lpc40xx_ea_ram
nor lpc40xx_ea_rom build.


I cannot reproduce this problem. Which error do you get?


Hmmm... I neglected to mention that I am using gcc master also. Sorry.

One of the configure conftest.c probes is failing with an object 
architecture

variant mismatch.

configure:3595: arm-rtems5-gcc -mthumb -march=armv7-m 
-mfpu=fpv4-sp-d16 -mfloat-abi=hard -mtune=cortex-m4 -O2 -g 
-ffunction-sections -fdata-sections   conftest.c >&5
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld: 
error: /tmp/cckWAYRI.o uses VFP register arguments, a.out does not
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld: 
failed to merge target specific data of file /tmp/cckWAYRI.o
/data/home/joel/test-gcc/install-master/bin/../lib/gcc/arm-rtems5/8.0.0/../../../../arm-rtems5/bin/ld: 
warning: cannot find entry symbol _start; defaulting to 8018

collect2: error: ld returned 1 exit status

With gcc 8.0 trying to head to a freeze, I wonder if you could take a 
look at it Sebastian.


ARM changed the floating point machine options in GCC 8. I guess we have 
to change all machine flags once we start to use GCC 8.


https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/arm/t-rtems;h=026a58956623ca8f74980f1a69b241b88e4988e7;hb=refs/heads/gcc-7-branch

vs.

https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/arm/t-rtems;h=c07378657c8289014fc875a426e48b48b7c1f690;hb=HEAD

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

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

Re: RSB release's default mode for building kernels

[Sebastian Huber]

On 16/01/18 23:35, Joel Sherrill wrote:



On Tue, Jan 16, 2018 at 4:27 PM, Chris Johns > wrote:


Hi,

The current mode on all release branches is to build the RTEMS
kernel. The
purpose was to have a single command that builds the tools and
RTEMS. However
this means all BSPs for an architecture are built and this is not
practical
because it slows a build and uses a larger amount of disk space
when an
architecture has a larger number of BSPs so I am wondering if the
default is
reversed.


I think RTEMS itself should not be built as part of the tools.


Yes, only the tools should be built by default.

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

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

no-preinstall: Ready for final review

[Sebastian Huber]

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 message and push it to the master.


--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

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