From: Andrew Lunn <andrew@lunn.ch>
To: Jeff Cooper <jeffc@logicpd.com>
Cc: ECOS Discussion Mailing List <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Error in CVS version of memalloc.cdl
Date: Fri, 09 Jul 2004 18:35:00 -0000 [thread overview]
Message-ID: <20040709183535.GC15979@lunn.ch> (raw)
In-Reply-To: <1089395521.20180.25.camel@nostromo>
On Fri, Jul 09, 2004 at 12:52:01PM -0500, Jeff Cooper wrote:
> I just noticed an error in memalloc.cdl in the anonymous CVS version of
> eCos that will cause my library not to build. The compile halts when it
> can't find the file 'debug.c'.
> It basically looks like someone was debugging and left an extra file in
> the compile line. Either that or they forgot to check in the file
> debug.c.
I forgot the check the file in :-(
Do a cvs up and it should work again.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2004-07-09 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 17:52 Jeff Cooper
2004-07-09 18:35 ` Andrew Lunn [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=20040709183535.GC15979@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=jeffc@logicpd.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).