This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: {Patch] java.net network functions
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Michael Koch <konqueror at gmx dot de>
- Cc: Richard dot Earnshaw at arm dot com, Richard Earnshaw <rearnsha at arm dot com>, java-patches at gcc dot gnu dot org
- Date: Thu, 21 Nov 2002 14:26:23 +0000
- Subject: Re: {Patch] java.net network functions
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> Am Donnerstag, 21. November 2002 14:55 schrieb Richard Earnshaw:
>
> > The difference is that previously we didn't depend on sys/socket.h
> > existing (which is why it's wrapped in autoconf include guards).
> > But with your change we now assume it does exist (we use a function
> > from it even if we didn't include it). A newlib libc does not
> > provide this header so we then get the error.
>
> The question is what header to include to get socket on a newlib
> system ? And I wonder how that worked before as there where an
> unconditional inclusion of socket.h and nothing special to get
> socket() on a newlib system. I just moved code to a different
> location. I really wonder how that can break this way.
No. There is no socket on a newlib system. End of story. The libjava
code is supposed to work without the networking parts if sockets aren't
available.
R.