From: Gary Thomas <gary@mlbassoc.com>
To: Greg Lindberg <gl4jalopi@earthlink.net>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] 1st build of redboot
Date: Thu, 02 Jun 2005 00:32:00 -0000 [thread overview]
Message-ID: <1117672317.19118.87.camel@hermes> (raw)
In-Reply-To: <MPEAJFOFNNOAIMOHBACIMEGGDPAA.gl4jalopi@earthlink.net>
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
next prev parent reply other threads:[~2005-06-02 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 23:06 Greg Lindberg
2005-06-02 0:32 ` Gary Thomas [this message]
[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
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=1117672317.19118.87.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gl4jalopi@earthlink.net \
/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).