From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Which packages are needed for networking?
Date: Fri, 16 Feb 2001 09:09:00 -0000 [thread overview]
Message-ID: <3A8D5E6B.D8D32DB5@larwe.com> (raw)
I'm a bit confused; somehow I've managed to break something that was
previously working. I am trying to compile a simple network test app
(with code borrowed from ftp_test.c) for the EDB7xxx platform. I
previously managed to build OK, but something - NO idea what! - has
broken; I haven't changed my build process that I can remember.
Could someone read over the below and tell me what I'm doing wrong?
Looks like a package needs to be added (probably something to do with
filesystems?), but it _used_ to work and I didn't add any other
packages.
Using CVS sources a week old,
ecosconfig new edb7xxx
ecosconfig add eth_drivers net
ecosconfig tree
make
then into my app's directory and make 2>&1 | tee make.out
arm-elf-gcc -c -o main.o -g -I. -I../ecos/install/include
-ffunction-sections -fdata-sections -mcpu=arm7tdmi -DDF57 main.c
In file included from ../ecos/install/include/network.h:63,
from main.c:14:
../ecos/install/include/sys/param.h:120:28: sys/simplelock.h: No such
file or directory
../ecos/install/include/sys/param.h:132:27: sys/syslimits.h: No such
file or directory
../ecos/install/include/sys/param.h:162:24: sys/signal.h: No such file
or directory
In file included from ../ecos/install/include/network.h:65,
from main.c:14:
../ecos/install/include/sys/ioctl.h:103:24: sys/ttycom.h: No such file
or directory
In file included from ../ecos/install/include/network.h:65,
from main.c:14:
../ecos/install/include/sys/ioctl.h:123:22: sys/dkio.h: No such file or
directory
../ecos/install/include/sys/ioctl.h:124:23: sys/filio.h: No such file or
directory
In file included from ../ecos/install/include/network.h:78,
from main.c:14:
../ecos/install/include/bootp.h:95:49: bptypes.h: No such file or
directory
In file included from ../ecos/install/include/network.h:78,
from main.c:14:
../ecos/install/include/bootp.h:316: warning: no semicolon at end of
struct or union
../ecos/install/include/bootp.h:316: parse error before "v_flags"
../ecos/install/include/bootp.h:326: parse error before "v_unused"
../ecos/install/include/bootp.h:326: warning: data definition has no
type or storage class
../ecos/install/include/bootp.h:328: parse error before '}' token
make: *** [main.o] Error 1
On a related note, is there a concise list of packages somewhere, other
than browsing through the cdl files? (That's why I love the graphical
config tool; it shows me everything :)
-- Lewin A.R.W. Edwards (Embedded Engineer) * Linux system
Work: http://www.digi-frame.com/
Personal: http://www.larwe.com/ and http://www.zws.com/
next reply other threads:[~2001-02-16 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 9:09 Lewin A.R.W. Edwards [this message]
2001-02-16 10:01 ` Bart Veer
2001-02-16 11:19 ` Lewin A.R.W. Edwards
2001-02-16 11:55 ` [ECOS] Still having problems getting networking up Lewin A.R.W. Edwards
2001-02-16 12:30 ` 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=3A8D5E6B.D8D32DB5@larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sources.redhat.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).