public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Rutger Hofman <rutger@cs.vu.nl>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Build fails after CVS update
Date: Sat, 30 Jun 2007 17:14:00 -0000	[thread overview]
Message-ID: <46852512.3030401@mlbassoc.com> (raw)
In-Reply-To: <46851F7A.8010709@mlbassoc.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gary Thomas wrote:
> Rutger Hofman wrote:
>> Hi list,
> 
>> I updated to the most recent version of the CVS list; the previous
>> checkout was from last february, not too long ago; but I ran into some
>> problems:
> 
>> = the Legacy Flash stuff has disappeared, but I use it (I think I might
>> be the only user, but still!). I can add it back of course.
>> = more seriously: after some conflict resolution, I can instruct
>> ecosconfig to create a tree, which it does without reporting any errors.
>> But it doesn't create a pkgconf/hal.h. It does create/copy a number of
>> include files from my ARM configuration, like hal_arm.h
> 
>> I thought many this was to do with an incompatible version of
>> ecosconfig, so I rebuilt that from today's checkout. It made no difference.
> 
>> Any clue how I can get a working build again?
> 
> What command did you use to checkout/update?
> Did you do this in a clean directory (checkout)?
> 

Also, what's the target?  How did you configure eCos?

I just tried this with a fresh checkout, using an ARM target (aaed)
and had no troubles building either RedBoot or an eCos kernel.

- --
- ------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGhSUOmaKbSsQGV8ARAoDkAKCDSAT+szCKvf6dFqbh/D9SjPlgngCeNP8X
zi06wlvqppRe10Sq+sYlLS4=
=Huzv
-----END PGP SIGNATURE-----

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

      parent reply	other threads:[~2007-06-29 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30  8:04 Rutger Hofman
2007-06-30 15:00 ` Gary Thomas
2007-06-30 16:12   ` Rutger Hofman
2007-07-06 10:37     ` [ECOS] Legacy Flash implementation (was: Re: [ECOS] Build fails after CVS update) Rutger Hofman
2007-07-08 18:57       ` Andrew Lunn
2007-07-08 20:15         ` [ECOS] Legacy Flash implementation Rutger Hofman
2007-07-09 11:08           ` Rutger Hofman
2007-07-09 13:48             ` Andrew Lunn
2007-06-30 17:14   ` Gary Thomas [this message]

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=46852512.3030401@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=rutger@cs.vu.nl \
    /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).