From: Rutger Hofman <rutger@cs.vu.nl>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Build fails after CVS update
Date: Sat, 30 Jun 2007 08:04:00 -0000 [thread overview]
Message-ID: <46851C3D.5000400@cs.vu.nl> (raw)
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?
Rutger
--
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 reply other threads:[~2007-06-29 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 8:04 Rutger Hofman [this message]
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 ` [ECOS] Build fails after CVS update 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=46851C3D.5000400@cs.vu.nl \
--to=rutger@cs.vu.nl \
--cc=ecos-discuss@ecos.sourceware.org \
/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).