You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Steven Filling <st...@panoptic.csustan.edu> on 1998/03/16 03:50:00 UTC
Re: os-linux/1612: compile warnings, compiled object will not ex
The following reply was made to PR os-linux/1612; it has been noted by GNATS.
From: Steven Filling <st...@panoptic.csustan.edu>
To: Dean Gaudet <dg...@arctic.org>
Cc: apbugs@apache.org
Subject: Re: os-linux/1612: compile warnings, compiled object will not ex
Date: Sun, 15 Mar 1998 18:44:15 -0800 (PST)
On 02-Jan-98 Dean Gaudet extemporized:
>=20
>> [crit] (45)Operation not supported: setsockopt: (SO_REUSEADDR)
>=20
> Er wait no, I'm wrong in what I just said. This looks like a kernel or
> libc problem. It shouldn't refuse this, it does implement SO_REUSEADDR.
>=20
> Oh hmm! I wonder if it's got a problem with the sizeof(int) parameter.
> But the Single Unix spec says it's supposed to take an int there, so it
> should be ok. =20
Dean -
Just an update on 1.3b5 : this version compiles with no perceptible
errors, but when I attempt to run it error_log gets the following:
[crit] (45)Operation not supported: setsockopt: (SO_REUSEADDR)
Guess there continues to be a disparity on alpha, as this compiles and
runs fine on intel [Red Hat 4.2 and 5.0] and Sparc [Red Hat 4.2]. If you
think it is a kernel problem, I'll see if I can find someone running one
of the 2.1.x kernels on alpha and have them give it a shot.
cheers
S.
----------------------------------
Steven Filling
E-Mail: steven@panopticon.csustan.edu
Date: 15-Mar-98 Time: 18:38:04
----------------------------------