Best way to update RTEMS?

Wu, Mark H. Mark.H.Wu at disney.com
Tue Jun 9 16:55:40 UTC 2015


Interesting. I'll try those next time. But I did follow the steps below (bootstrap, configure, make), and it didn't resolve the problem. I had to start with a clean directory to get it to work again.

-----Original Message-----
From: Sebastian Huber [mailto:sebastian.huber at embedded-brains.de] 
Sent: Monday, June 08, 2015 22:11
To: Gedare Bloom
Cc: Wu, Mark H.; users at rtems.org
Subject: Re: Best way to update RTEMS?

Hello,

in most cases it is enough to run configure with the --enable-mainainer-mode option and then do a "make preinstall" in an existing build tree.  If you get strange errors, then do the below steps.

----- Gedare Bloom <gedare at rtems.org> schrieb:
> After pulling, it is a good idea to:
> 1. re-run bootstrap, in case any of the autoconf input files have
> changed (Makefile.am, preinstall.am, configure.ac).
> 2. re-run configure, in case bootstrap changed any of the autoconf
> output files (configure, Makefile.in)
> 3. re-run make, in case configure changed any of its outputs (Makefile)
> 
> The cleanest thing to do is to delete your build directory--where you
> previously have run configure and make, which should not be the same
> as your source (rtems.git) directory.
> 
> Gedare
> 
> 
> On Mon, Jun 8, 2015 at 3:25 PM, Wu, Mark H. <Mark.H.Wu at disney.com> wrote:
> > I started with a fresh directory, ran configure and make, and it built fine. Is configure supposed to update the directory when a new pull is done, or is it make that's supposed to update things?
> >
> > -----Original Message-----
> > From: Chris Johns [mailto:chrisj at rtems.org]
> > Sent: Friday, June 05, 2015 18:48
> > To: Wu, Mark H.; users at rtems.org
> > Subject: Re: Best way to update RTEMS?
> >
> > On 6/06/2015 11:11 am, Wu, Mark H. wrote:
> >> I downloaded RTEMS from the git repo a few weeks ago, and have things at a stable point (still working on getting a few things to work, like networking). I decided to update from the git repo, and can't seem to get it rebuilt correctly. What are the correct steps to update my libraries after pulling down from the repo?
> >>
> >
> > How did you update RTEMS ? I normally do a 'git pull'.
> >
> >> What I have done so far:
> >>
> >> 1. Run ./bootstrap within the RTEMS directory
> >> 2. Re-run configure from within my installation directory
> >> 3. Re-run make from within my installation directory
> >>
> >
> > Just to clear up any misunderstanding, we use the term 'source'
> > directory for the location of the RTEMS source code we are building. We
> > term the 'installation' directory the locate the files the 'make
> > install' process installs RTEMS to, ie the configure's -prefix path.
> >
> >> This is where it fails - I have a compilation error. The files within my installation directory don't quite match the ones in the RTEMS directory.
> >> I believe that these are the same steps I performed upon initial installation (the same steps in the quick start). Do they not work for updating? Is there another (better) procedure for updating RTEMS?
> >
> > What is your configure command line ?
> >
> > What is the error ?
> >
> > The error all depends on the point you took your initial build from.
> > There was a change in newlib that effected the RTEMS kernel source and
> > that requires an RSB update and a rebuild of your tools.
> >
> > Please note, this type of change does not happen on releases and once
> > 4.11 is released you will experience a stable environment.
> >
> > Chris
> > _______________________________________________
> > users mailing list
> > users at rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users

-- 
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.huber at embedded-brains.de
PGP     : Public key available on request.

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


More information about the users mailing list