From: "David Brennan" <ecos@brennanhome.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Compile error in if_i82559.c
Date: Thu, 13 Sep 2007 05:30:00 -0000 [thread overview]
Message-ID: <888069a80709122230s7248dadbhbc0019543915482e@mail.gmail.com> (raw)
I am just returning to eCos after a prolonged absence. I got the
latest CVS version and tried to compile for a basic pc with network
functions. However the if_i82559.c module will not compile with
default template.
ubuntu@ubuntu:/opt/ecos/pc-base$ rm -rf *
ubuntu@ubuntu:/opt/ecos/pc-base$ ecosconfig new pc net
U CYGBLD_ISO_STRUCTTIMEVAL_HEADER, new inferred value <cyg/posix/sys/time.h>
U CYGBLD_ISO_FNMATCH_HEADER, new inferred value <cyg/fileio/fnmatch.h>
ubuntu@ubuntu:/opt/ecos/pc-base$ ecosconfig tree
ubuntu@ubuntu:/opt/ecos/pc-base$ make -s
headers finished
/opt/ecos/ecos/packages/devs/eth/intel/i82559/current/src/if_i82559.c:
In function `pci_init_find_82559s':
/opt/ecos/ecos/packages/devs/eth/intel/i82559/current/src/if_i82559.c:2992:
`eth_dsr' undeclared (first use in this function)
/opt/ecos/ecos/packages/devs/eth/intel/i82559/current/src/if_i82559.c:2992:
(Each undeclared identifier is reported only once
/opt/ecos/ecos/packages/devs/eth/intel/i82559/current/src/if_i82559.c:2992:
for each function it appears in.)
make[1]: *** [src/if_i82559.o.d] Error 1
make: *** [build] Error 2
The root of this problem seems to be the new conditional compile added
by this change.
(http://sourceware.org/ml/ecos-patches/2006-11/msg00037.html) However,
I don't know if the conditions are wrong in the #if or in the default
template.
Thanks in advance for any pointers.
David
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2007-09-13 5:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=888069a80709122230s7248dadbhbc0019543915482e@mail.gmail.com \
--to=ecos@brennanhome.com \
--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).