From: Nickolay <nickolay@protei.ru>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] RedBoot and semaphore
Date: Fri, 01 Apr 2005 11:34:00 -0000 [thread overview]
Message-ID: <424D31D6.5020401@protei.ru> (raw)
Hallo!
What last ecos version, that successfuly builded with IXP425 NPE support
from Intel?
I did try build last ecos version from CVS with Intel's
CYGPKG_DEVS_ETH_INTEL_NPE and
CYGPKG_DEVS_ETH_ARM_IXDP425_NPE. But when compile, has some error:
In file included from
/home/nickolay/ecos/build1/install/include/os_datatypes.h:168,
from
/home/nickolay/ecos/build1/install/include/ix_ossl.h:170,
from
/home/nickolay/ecos/packages/devs/eth/intel/npe/v1_4/src/if_npe.c:72:
/opt/montavista/previewkit/arm/xscale_le/target/usr/include/asm/semaphore.h:20:
error: parse error before "wait_queue_head_t"
But wait_queue_head_t really defined only with -D__KERNEL__, but ecos
compile without this flag.
--
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:[~2005-04-01 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 11:34 Nickolay [this message]
2005-04-01 13:47 ` Mark Salter
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=424D31D6.5020401@protei.ru \
--to=nickolay@protei.ru \
--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).