lpc40xx BSPs do not build on master
Hi I'm not sure what broke but neither lpc40xx_ea_ram nor lpc40xx_ea_rom build. Does anyone else see this? If so, any idea what's up? It is failing quite early in the build process. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Hello World patch
- 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. 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. 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
Re: Hello World patch
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/wiki/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
ARM FVP, GDB, RTEMS, etc
Hi Has anyone got any experience with the ARM Fixed Virtual Platforms with GDB and/or RTEMS on any of the architectural variants? https://developer.arm.com/products/system-design/fixed-virtual-platforms In looking at it, I am not sure what the preferred debug setup is and was hoping someone in the community had experience to offer. Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] gcc: Use GNU's FTP rather than the package's home sites that change.
Close #3271
---
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 +++---
7 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/source-builder/config/gcc-4.3-1.cfg
b/source-builder/config/gcc-4.3-1.cfg
index d499a15..4c7a335 100644
--- a/source-builder/config/gcc-4.3-1.cfg
+++ b/source-builder/config/gcc-4.3-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.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/source-builder/config/gcc-4.9-1.cfg
index 7d6a44
Re: lpc40xx BSPs do not build on master
On 16/1/18 4:53 am, Joel Sherrill wrote: > > Does anyone else see this? If so, any idea what's up? It is failing quite > early > in the build process. > I did not see this building Sebastian's no-preinstall branch for just 'tests': https://lists.rtems.org/pipermail/build/2018-January/000330.html Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: lpc40xx BSPs do not build on master
On Jan 15, 2018 5:59 PM, "Chris Johns" wrote: On 16/1/18 4:53 am, Joel Sherrill wrote: > > Does anyone else see this? If so, any idea what's up? It is failing quite early > in the build process. > I did not see this building Sebastian's no-preinstall branch for just 'tests': https://lists.rtems.org/pipermail/build/2018-January/000330.html Thanks. I have most of the architectures and targets building with empty bsp_spec files. I will try it with an unmodified tree. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
