On Mon, 2 Nov 1998, Aaron M. Renn wrote:
> >I also noticed a strange warning message when I tried to compile
> >classpath on a linux box. Here is the warning I got from the
> >java.net classes.
> >
> >/bin/sh ../../libtool --mode=compile
> gcc -DPACKAGE=\"classpath\" -DVERSION=\"0.0\" -DSTDC_HEADERS=1 -DHAVE_UNISTD
> _H=1 -DHAVE_GETHOSTNAME=1 -DHAVE_STRERROR=1 -DHAVE_LIBPTHREAD=1 -DUSE_PTHREA
> DS= -I. -I. -I/tmp/mo/install_japhar/include/japhar -I/tmp/mo/install_japh
> ar/include/japhar/private -g -O2 -c javanet.c
> >gcc -DPACKAGE=\"classpath\" -DVERSION=\"0.0\" -DSTDC_HEADERS=1 -DHAVE_UNIST
> D_H=1 -DHAVE_GETHOSTNAME=1 -DHAVE_STRERROR=1 -DHAVE_LIBPTHREAD=1 -DUSE_PTHRE
> ADS= -I. -I. -I/tmp/mo/install_japhar/include/japhar -I/tmp/mo/install_japha
> r/include/japhar/private -g -O2 -c javanet.c
> >javanet.c:37: warning: #warning Neither SO_TIMEOUT or SO_RCVTIMEO are
> defined!
> >javanet.c:38: warning: #warning This will cause all get/setOption calls
> with that value to throw an exception
> >echo timestamp > javanet.lo
> >/bin/sh: .deps/javanet.p: No such file or directory
> >make: [javanet.lo] Error 1 (ignored)
>
> I don't know where the "Error 1" out of make is coming from, but the
> javanet.c warnings should be generated only if your machine doesn't support
> SO_TIMEOUT. Linux doesn't seem to have that value (or SO_RCVTIMEO) defined
> anywhere. (If it does, let me know). On a non-Linux system that has one of
> these, you should not get the error. What platform are you on? Where is
> SO_TIMEOUT defined?
I was running on a linux 2.0.32 box.
>
> I'll look at the patch later tonight.
Cool. Note that patch was for systems other then linux (mine was solaris).
It compiled the way it was under linux.
> --
> Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
>
>
Mo DeJong
dejong at cs.umn.edu
