From: Bart Veer <bartv@redhat.com>
To: larwe@larwe.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Which packages are needed for networking?
Date: Fri, 16 Feb 2001 10:01:00 -0000 [thread overview]
Message-ID: <200102161801.f1GI1do07795@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <3A8D5E6B.D8D32DB5@larwe.com>
>>>>> "Lewin" == Lewin A R W Edwards <larwe@larwe.com> writes:
Lewin> I'm a bit confused; somehow I've managed to break something
Lewin> that was previously working. I am trying to compile a
Lewin> simple network test app (with code borrowed from
Lewin> ftp_test.c) for the EDB7xxx platform. I previously managed
Lewin> to build OK, but something - NO idea what! - has broken; I
Lewin> haven't changed my build process that I can remember.
Lewin> Could someone read over the below and tell me what I'm
Lewin> doing wrong? Looks like a package needs to be added
Lewin> (probably something to do with filesystems?), but it _used_
Lewin> to work and I didn't add any other packages.
Lewin> Using CVS sources a week old,
Lewin> ecosconfig new edb7xxx
Lewin> ecosconfig add eth_drivers net
You should be able to just do "ecosconfig new edb7xxx net" to combine
the above two steps, but that is not the problem here.
Lewin> ecosconfig tree
Lewin> make
Lewin> then into my app's directory and make 2>&1 | tee make.out
Lewin> arm-elf-gcc -c -o main.o -g -I. -I../ecos/install/include
Lewin> -ffunction-sections -fdata-sections -mcpu=arm7tdmi -DDF57 main.c
Lewin> In file included from ../ecos/install/include/network.h:63,
Lewin> from main.c:14:
Lewin> ../ecos/install/include/sys/param.h:120:28: sys/simplelock.h: No such
Lewin> file or directory
OK, let's take a look at sys/param.h at ~line 120 to see what the
problem might be:
#ifndef __ECOS
#include <sys/simplelock.h>
#endif
And quoting from the TCP/IP documentation at
http://sources.redhat.com/ecos/docs-latest/tcpip/tcpip.3.html#pgfId=1133601
"In general, using the networking code may require definition of two
symbols: _KERNEL and __ECOS. _KERNEL is not normally required; __ECOS
is normally required. So add this to your compile lines for files
which use the network stack:
-D__ECOS"
so that should solve the problem.
<snip>
Lewin> On a related note, is there a concise list of packages
Lewin> somewhere, other than browsing through the cdl files?
Lewin> (That's why I love the graphical config tool; it shows me
Lewin> everything :)
$ ecosconfig --help
Usage: ecosconfig [ qualifier ... ] [ command ]
commands are:
list : list repository contents
<snip>
That is as concise as it is going to get for now, given the number of
packages and targets in the current system. Alternatively you can look
at the ecos.db file in any text editor, since that is where the
information comes from.
Bart
next prev parent reply other threads:[~2001-02-16 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 9:09 Lewin A.R.W. Edwards
2001-02-16 10:01 ` Bart Veer [this message]
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=200102161801.f1GI1do07795@sheesh.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=larwe@larwe.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).