* RE: [ECOS] TCP/IP as a program.
@ 2001-08-16 1:29 David.Karlberg
2001-08-16 1:37 ` Andrew Lunn
2001-08-16 7:47 ` [ECOS] " Grant Edwards
0 siblings, 2 replies; 6+ messages in thread
From: David.Karlberg @ 2001-08-16 1:29 UTC (permalink / raw)
To: andrew.lunn; +Cc: ecos-discuss
I want to use PPP with TCP/IP and I figured it would be a lot easier to work
with the Net pack
if I did not have to recompile the whole eCos everytime I want to see if my
changes work.
And that I would have more control of which files are used.
David
-----Original Message-----
From: Andrew Lunn [ mailto:andrew.lunn@ascom.ch ]
Sent: den 16 augusti 2001 10:20
To: Karlberg David
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] TCP/IP as a program.
> Hi,
> I am trying to run the TCP/IP stack as a "program". As opposed to haveing
it
> in the eCos lib.
Silly question: Why?
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ECOS] TCP/IP as a program.
2001-08-16 1:29 [ECOS] TCP/IP as a program David.Karlberg
@ 2001-08-16 1:37 ` Andrew Lunn
2001-08-16 7:47 ` [ECOS] " Grant Edwards
1 sibling, 0 replies; 6+ messages in thread
From: Andrew Lunn @ 2001-08-16 1:37 UTC (permalink / raw)
To: David.Karlberg; +Cc: ecos-discuss
On Thu, Aug 16, 2001 at 10:29:10AM +0200, David.Karlberg@combitechsystems.com wrote:
> I want to use PPP with TCP/IP and I figured it would be a lot easier
> to work with the Net pack if I did not have to recompile the whole
> eCos everytime I want to see if my changes work. And that I would
> have more control of which files are used.
OK. From experiance, i found its fine working on eCos sources
directly. Compiles are no slower working inside ecos to outside. You
may want to look at putting source files into the work tree, rather
than the repository. This is in the documentation somewhere. Just be
carefull of make clean, and ecosconfig tree!
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread* [ECOS] Re: TCP/IP as a program.
2001-08-16 1:29 [ECOS] TCP/IP as a program David.Karlberg
2001-08-16 1:37 ` Andrew Lunn
@ 2001-08-16 7:47 ` Grant Edwards
1 sibling, 0 replies; 6+ messages in thread
From: Grant Edwards @ 2001-08-16 7:47 UTC (permalink / raw)
To: David.Karlberg; +Cc: andrew.lunn, ecos-discuss
David.Karlberg@combitechsystems.com writes:
> I want to use PPP with TCP/IP and I figured it would be a lot easier to work
> with the Net pack
> if I did not have to recompile the whole eCos everytime I want to see if my
> changes work.
A make will only recompile files that have changed. The only time
everything gets recompiled is when you change the eCos configuration
file (ecos.ecc), and if you do that, you've got to re-compile everything
anyway (regardless of where the files are).
I regularly work by modifying files in the main eCos source tree, and
I don't think you're going to save much time by splitting out parts of
it.
When testing, you do have to remember to do two makes: one to recompile the
changed eCos source files, and a second to re-link your test app with
the new eCos libraries. I've created more confusion that I'd like to
admit by by forgetting that second make.
> And that I would have more control of which files are used.
I guess I never had any problems with that.
--
Grant Edwards
grante@visi.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] TCP/IP as a program.
@ 2001-08-16 1:16 David.Karlberg
2001-08-16 1:19 ` Andrew Lunn
2001-08-16 6:52 ` Jonathan Larmour
0 siblings, 2 replies; 6+ messages in thread
From: David.Karlberg @ 2001-08-16 1:16 UTC (permalink / raw)
To: ecos-discuss
Hi,
I am trying to run the TCP/IP stack as a "program". As opposed to haveing it
in the eCos lib.
I have all the files from the net directory and Im trying to compile it but
I get a lot of parse errors.
What do I have to do to make it work?
Daivd
bash.exe-2.05$ make
arm-elf-gcc -mcpu=strongarm -nostartfiles
-L//c/ecos-work/m
edia_install/lib -Wl,--gc-sections -Wl,-Map -Wl,tcpip_stack_mapfile.map -o
hell
o hello.o -Ttarget.ld -nostdlib
arm-elf-gcc -mcpu=strongarm -c -o src/ecos/timeout.o -g
-Wa
ll -I//c/ecos-work/media_install/include -I//c/Wosp_nexgen/include/
-ffunction
-sections -fdata-sections -Wpointer-arith -Wstrict-prototypes -Winline
-Wundef -
Woverloaded-virtual -ffunction-sections -fdata-sections -D_KERNEL -D_ECOS
-D__EC
OS -DCYGPKG_NET -D_PPP -DBTD_USERSTACK src/ecos/timeout.c
In file included from //c/Wosp_nexgen/include/machine/param.h:109,
from //c/Wosp_nexgen/include/sys/param.h:166,
from src/ecos/timeout.c:50:
//c/Wosp_nexgen/include/lib/libkern/libkern.h:122: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:128: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:134: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:140: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:145: parse error before `max'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:146: parse error before
`u_int'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:146: warning: type defaults to
`in
t' in declaration of `a'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:146: warning: type defaults to
`in
t' in declaration of `b'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:146: warning: data definition
has
no type or storage class
//c/Wosp_nexgen/include/lib/libkern/libkern.h:147: parse error before `{'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:151: parse error before `min'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:152: parse error before
`u_int'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:152: warning: type defaults to
`in
t' in declaration of `a'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:152: warning: type defaults to
`in
t' in declaration of `b'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:152: warning: data definition
has
no type or storage class
//c/Wosp_nexgen/include/lib/libkern/libkern.h:153: parse error before `{'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:157: parse error before
`ulmax'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:158: parse error before
`u_long'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:158: warning: type defaults to
`in
t' in declaration of `a'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:158: warning: type defaults to
`in
t' in declaration of `b'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:158: warning: data definition
has
no type or storage class
//c/Wosp_nexgen/include/lib/libkern/libkern.h:159: parse error before `{'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:163: parse error before
`ulmin'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:164: parse error before
`u_long'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:164: warning: type defaults to
`in
t' in declaration of `a'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:164: warning: type defaults to
`in
t' in declaration of `b'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:164: warning: data definition
has
no type or storage class
//c/Wosp_nexgen/include/lib/libkern/libkern.h:165: parse error before `{'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:222: parse error before
`u_int'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:222: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:224: parse error before
`const'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:224: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:225: parse error before
`u_char'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:225: warning: function
declaration
isn't a prototype
//c/Wosp_nexgen/include/lib/libkern/libkern.h:235: syntax error before
`const'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:235: warning: type defaults to
`in
t' in declaration of `__bcd2bin'
//c/Wosp_nexgen/include/lib/libkern/libkern.h:235: warning: type defaults to
`in
t' in declaration of `__bin2bcd'
In file included from //c/Wosp_nexgen/include/sys/param.h:166,
from src/ecos/timeout.c:50:
//c/Wosp_nexgen/include/machine/param.h:149: parse error before `cp'
//c/Wosp_nexgen/include/machine/param.h:149: warning: function declaration
isn't
a prototype
//c/Wosp_nexgen/include/machine/param.h:157: parse error before `u_long'
//c/Wosp_nexgen/include/machine/param.h:157: warning: function declaration
isn't
a prototype
src/ecos/timeout.c:74: `CYGNUM_HAL_STACK_SIZE_TYPICAL' undeclared here (not
in a
function)
src/ecos/timeout.c: In function `cyg_alarm_timeout_init':
src/ecos/timeout.c:197: `CYGPKG_NET_FAST_THREAD_PRIORITY' undeclared (first
use
in this function)
src/ecos/timeout.c:197: (Each undeclared identifier is reported only once
src/ecos/timeout.c:197: for each function it appears in.)
src/ecos/timeout.c:202: `CYGNUM_HAL_STACK_SIZE_TYPICAL' undeclared (first
use in
this function)
src/ecos/timeout.c: At top level:
//c/Wosp_nexgen/include/lib/libkern/libkern.h:235: warning: array
`__bcd2bin' as
sumed to have one element
//c/Wosp_nexgen/include/lib/libkern/libkern.h:235: warning: array
`__bin2bcd' as
sumed to have one element
src/ecos/timeout.c:74: warning: `alarm_stack' defined but not used
make: *** [src/ecos/timeout.o] Error 1
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ECOS] TCP/IP as a program.
2001-08-16 1:16 [ECOS] " David.Karlberg
@ 2001-08-16 1:19 ` Andrew Lunn
2001-08-16 6:52 ` Jonathan Larmour
1 sibling, 0 replies; 6+ messages in thread
From: Andrew Lunn @ 2001-08-16 1:19 UTC (permalink / raw)
To: David.Karlberg; +Cc: ecos-discuss
> Hi,
> I am trying to run the TCP/IP stack as a "program". As opposed to haveing it
> in the eCos lib.
Silly question: Why?
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ECOS] TCP/IP as a program.
2001-08-16 1:16 [ECOS] " David.Karlberg
2001-08-16 1:19 ` Andrew Lunn
@ 2001-08-16 6:52 ` Jonathan Larmour
1 sibling, 0 replies; 6+ messages in thread
From: Jonathan Larmour @ 2001-08-16 6:52 UTC (permalink / raw)
To: David.Karlberg; +Cc: ecos-discuss
David.Karlberg@combitechsystems.com wrote:
>
> Hi,
> I am trying to run the TCP/IP stack as a "program". As opposed to haveing it
> in the eCos lib.
> I have all the files from the net directory and Im trying to compile it but
> I get a lot of parse errors.
> What do I have to do to make it work?
The rest of the eCos configuration still has to match what happens when the
stack is included. For example various CDL requirements exist. Ensure those
are set in the eCos configuration you are building with.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-08-16 7:47 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-16 1:29 [ECOS] TCP/IP as a program David.Karlberg
2001-08-16 1:37 ` Andrew Lunn
2001-08-16 7:47 ` [ECOS] " Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 1:16 [ECOS] " David.Karlberg
2001-08-16 1:19 ` Andrew Lunn
2001-08-16 6:52 ` Jonathan Larmour
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).