public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Greg Lindberg" <gl4jalopi@earthlink.net>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] 1st build of redboot
Date: Thu, 02 Jun 2005 22:11:00 -0000	[thread overview]
Message-ID: <MPEAJFOFNNOAIMOHBACIEEHNDPAA.gl4jalopi@earthlink.net> (raw)
In-Reply-To: <1117748869.19118.146.camel@hermes>

Gary,

Thanks, now I understand what was happening.  The Redboot page says to get
'ecos' and then proceeds to tell you how to use the ecosconfig program,
which isn't pulled.  I'll go back and pull the full tree.

Greg

> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Gary Thomas
> Sent: Thursday, June 02, 2005 2:48 PM
> To: Greg Lindberg
> Cc: eCos Discussion
> Subject: RE: [ECOS] 1st build of redboot
>
>
> On Thu, 2005-06-02 at 11:41 -0700, Greg Lindberg wrote:
> > Sorry about the reply.
> >
> > I tried what you suggested and the ecosconfig program does not
> exist in the
> > resulting tree.  I had run configure, make and make install on
> the cvs tree
> > initially and had not found the ecosconfig program which is why
> I had gone
> > to the ecos installer.
> >
> > As far as trying to improve the documentation, I am new to the
> Redboot and
> > eCos environment.  If I can't figure out how to do the initial
> install of
> > the tools because the documentation leaves out important pieces, I'm not
> > going to be able to get to the point where I can contribute any useful
> > suggestions.  It appears to me, from my experience, that the
> documentation
> > should say that you have to go through the ecos install to get the tools
> > before trying to install the redboot cvs code.  If there is a
> way to pull
> > from cvs and generate the tools, I haven't been able to figure
> out how to do
> > it.  I've run configure and make & make install in several ways on a cvs
> > tree and have not been able to find the ecosconfig program that is then
> > necessary to configure the code to produce a version of the
> Redboot loader.
> > It's possible that I've missed something, so any help is still
> appreciated.
> >
>
> When you did the checkout, what module did you use?  To get the tools,
> I always checkout 'ecos-full', e.g.
>   % cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos co ecos-full
>
> If you just checkout 'ecos' you get a rather minimal tree.  If you
> want to add the tools to an already checked out tree, just use:
>   % cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos co ecos-host
>
> > Greg
> >
> > > -----Original Message-----
> > > From: ecos-discuss-owner@ecos.sourceware.org
> > > [mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of
> Gary Thomas
> > > Sent: Thursday, June 02, 2005 9:18 AM
> > > To: Greg Lindberg
> > > Cc: eCos Discussion
> > > Subject: RE: [ECOS] 1st build of redboot
> > >
> > >
> > > Please copy relies to the list so that all may benefit.
> > >
> > > On Thu, 2005-06-02 at 09:06 -0700, Greg Lindberg wrote:
> > > > Ok, using a code tree just from cvs cured the build problems
> > > with the eU250
> > > > branch, thanks.
> > > >
> > > > Seems that the Redboot page that describes how to get the code
> > > should talk
> > > > about getting the tools, specifically ecosconfig, because they
> > > are not in
> > > > the cvs repository.
> > > >
> > >
> > > Sure it is - you just have to build it.
> > >   % mkdir tools
> > >   % cd tools
> > >   % <ECOS>/configure
> > >   % make
> > > Where <ECOS> is the top-level directory (contains 'host' and
> 'packages'
> > > directories, amongst others)
> > >
> > > If you think the documentation can be improved (either the manuals or
> > > the web pages), feel free to suggest changes (patches!).  This is a
> > > community project after all :-)
> > >
> > > > Greg
> > > > > -----Original Message-----
> > > > > From: ecos-discuss-owner@ecos.sourceware.org
> > > > > [mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of
> > > Gary Thomas
> > > > > Sent: Wednesday, June 01, 2005 5:32 PM
> > > > > To: Greg Lindberg
> > > > > Cc: eCos Discussion
> > > > > Subject: Re: [ECOS] 1st build of redboot
> > > > >
> > > > >
> > > > > On Wed, 2005-06-01 at 16:10 -0700, Greg Lindberg wrote:
> > > > > > Hello all,
> > > > > >
> > > > > > I'm just getting started with Redboot and ecos.  I trying
> > > to build an
> > > > > > existing version of redboot before starting on porting it
> > > to the custom
> > > > > > hardware that we're using for our product.  I downloaded the
> > > > > > ecos-installer.sh script and ran that and after trying to
> > > > > configure for an
> > > > > > intel xscale pxa processor, I pulled the latest code from cvs
> > > > > and copied it
> > > > > > on top of the tree that the installer created.  I then was able
> > > > > to configure
> > > > > > for the uE250 board.  I got some warnings and then a
> > > failure during the
> > > > > > compile as follows:
> > > > >
> > > > > Use the anonymous CVS tree (instead of the hodge-podge you
> > > have).  These
> > > > > problems will vanish.
> > >
> > > --
> > > ------------------------------------------------------------
> > > Gary Thomas                 |  Consulting for the
> > > MLB Associates              |    Embedded world
> > > ------------------------------------------------------------
> > >
> > >
> > > --
> > > Before posting, please read the FAQ:
http://ecos.sourceware.org/fom/ecos
> > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> >
>

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-06-02 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MPEAJFOFNNOAIMOHBACIIEHDDPAA.gl4jalopi@earthlink.net>
2005-06-02 16:18 ` Gary Thomas
2005-06-02 18:37   ` Greg Lindberg
2005-06-02 21:48     ` Gary Thomas
2005-06-02 22:11       ` Greg Lindberg [this message]
2005-06-01 23:06 Greg Lindberg
2005-06-02  0:32 ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MPEAJFOFNNOAIMOHBACIEEHNDPAA.gl4jalopi@earthlink.net \
    --to=gl4jalopi@earthlink.net \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).