* [ECOS] socket.cxx (recvmsg()) problem
@ 2007-10-31 9:30 Alperen Coskun
2007-10-31 9:37 ` [ECOS] build arm toolchain failed，why？ sean yang
2007-10-31 11:19 ` [ECOS] socket.cxx (recvmsg()) problem Gary Thomas
0 siblings, 2 replies; 3+ messages in thread
From: Alperen Coskun @ 2007-10-31 9:30 UTC (permalink / raw)
To: ecos discuss
Hi all,
I want to understand how athttp server receives data from the socket. I followed the related functions till;
error = ops->recvmsg(fp,&msg,fromlen,&ret);
which is in the function recvfrom() in socket.cxx. After that, I couldn't find where that function call is.
It doesn't go to the function recvmsg() which is in socket.cxx. I searched for every recvmsg() functions in the packages but I couldn't find an appropriate one.
Could anyone help me?
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ECOS] build arm toolchain failed，why？
2007-10-31 9:30 [ECOS] socket.cxx (recvmsg()) problem Alperen Coskun
@ 2007-10-31 9:37 ` sean yang
2007-10-31 11:19 ` [ECOS] socket.cxx (recvmsg()) problem Gary Thomas
1 sibling, 0 replies; 3+ messages in thread
From: sean yang @ 2007-10-31 9:37 UTC (permalink / raw)
To: 'ecos discuss'
I followed the http://ecos.sourceware.org/build-toolchain.html to build a
arm toolchain,but it cann't be finished successfully when I input the "make
-w all install 2>&1 | tee make.out" in cygwin,the log is :
make: Entering directory `/tmp/build/binutils'
Making info in doc
make[1]: Entering directory `/tmp/build/binutils/doc'
make[1]: Nothing to be done for `info'.
make[1]: Leaving directory `/tmp/build/binutils/doc'
Making info in po
make[1]: Entering directory `/tmp/build/binutils/po'
make[1]: Nothing to be done for `info'.
make[1]: Leaving directory `/tmp/build/binutils/po'
make[1]: Entering directory `/tmp/build/binutils'
make[1]: Nothing to be done for `info-am'.
make[1]: Leaving directory `/tmp/build/binutils'
make all-recursive
make[1]: Entering directory `/tmp/build/binutils'
Making all in doc
make[2]: Entering directory `/tmp/build/binutils/doc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/build/binutils/doc'
Making all in po
make[2]: Entering directory `/tmp/build/binutils/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/build/binutils/po'
make[2]: Entering directory `/tmp/build/binutils'
make[2]: *** No rule to make target `../bfd/bfdver.h', needed by `size.o'.
Stop.
make[2]: Leaving directory `/tmp/build/binutils'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/binutils'
make: *** [all] Error 2
make: Leaving directory `/tmp/build/binutils'
I don’t know why,could anyone help me out?thanks very much!
-----邮件原件-----
发件人: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] 代表 Alperen Coskun
发送时间: 2007年10月31日 17:30
收件人: ecos discuss
主题: [ECOS] socket.cxx (recvmsg()) problem
Hi all,
I want to understand how athttp server receives data from the socket. I
followed the related functions till;
error = ops->recvmsg(fp,&msg,fromlen,&ret);
which is in the function recvfrom() in socket.cxx. After that, I couldn't
find where that function call is.
It doesn't go to the function recvmsg() which is in socket.cxx. I searched
for every recvmsg() functions in the packages but I couldn't find an
appropriate one.
Could anyone help me?
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ECOS] socket.cxx (recvmsg()) problem
2007-10-31 9:30 [ECOS] socket.cxx (recvmsg()) problem Alperen Coskun
2007-10-31 9:37 ` [ECOS] build arm toolchain failed，why？ sean yang
@ 2007-10-31 11:19 ` Gary Thomas
1 sibling, 0 replies; 3+ messages in thread
From: Gary Thomas @ 2007-10-31 11:19 UTC (permalink / raw)
To: Alperen Coskun; +Cc: ecos discuss
Alperen Coskun wrote:
> Hi all,
>
> I want to understand how athttp server receives data from the socket. I followed the related functions till;
>
> error = ops->recvmsg(fp,&msg,fromlen,&ret);
>
> which is in the function recvfrom() in socket.cxx. After that, I couldn't find where that function call is.
>
> It doesn't go to the function recvmsg() which is in socket.cxx. I searched for every recvmsg() functions in the packages but I couldn't find an appropriate one.
>
> Could anyone help me?
Look at it carefully - the function being called is not 'recvmsg', but
rather the 'recvmsg' member of the structure pointed to by 'ops'.
To find the real function being called, you'd have to know what this
value/address is.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-10-31 11:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-10-31 9:30 [ECOS] socket.cxx (recvmsg()) problem Alperen Coskun
2007-10-31 9:37 ` [ECOS] build arm toolchain failed，why？ sean yang
2007-10-31 11:19 ` [ECOS] socket.cxx (recvmsg()) problem Gary Thomas
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).