[#7978] Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...>

This patch adds support for getting the uid and gid of the peer

27 messages 2006/06/09
[#8004] Re: Patch for Unix socket peer credentials — Tanaka Akira <akr@...17n.org> 2006/06/16

In article <200606091528.30171.jfh@cise.ufl.edu>,

[#8005] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/06/16

On Friday 16 June 2006 11:51, Tanaka Akira wrote:

[#8010] Re: Patch for Unix socket peer credentials — Tanaka Akira <akr@...17n.org> 2006/06/17

In article <200606161327.35948.jfh@cise.ufl.edu>,

[#8191] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/07/10

On Saturday 17 June 2006 06:27, Tanaka Akira wrote:

[#8193] Re: Patch for Unix socket peer credentials — Tanaka Akira <akr@...> 2006/07/11

In article <200607101352.16804.jfh@cise.ufl.edu>,

[#8212] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/07/13

On Tuesday 11 July 2006 00:10, Tanaka Akira wrote:

[#8217] Re: Patch for Unix socket peer credentials — nobu@... 2006/07/14

Hi,

[#8257] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/07/18

On Thursday 13 July 2006 22:48, nobu@ruby-lang.org wrote:

[#8258] Re: Patch for Unix socket peer credentials — Eric Hodel <drbrain@...7.net> 2006/07/18

On Jul 18, 2006, at 12:27 PM, James F. Hranicky wrote:

[#8073] 1.8.5p1 build failure on Solaris 10 — "Daniel Berger" <Daniel.Berger@...>

Solaris 10

23 messages 2006/06/27
[#8074] Re: 1.8.5p1 build failure on Solaris 10 — Yukihiro Matsumoto <matz@...> 2006/06/28

Hi,

[#8078] Re: 1.8.5p1 build failure on Solaris 10 — "Daniel Berger" <Daniel.Berger@...> 2006/06/28

Yukihiro Matsumoto wrote:

[#8079] Re: 1.8.5p1 build failure on Solaris 10 — ts <decoux@...> 2006/06/28

>>>>> "D" == Daniel Berger <Daniel.Berger@qwest.com> writes:

[#8096] Re: 1.8.5p1 build failure on Solaris 10 — ville.mattila@... 2006/06/29

ts <decoux@moulon.inra.fr> wrote on 28.06.2006 17:37:00:

Re: 1.8.5p1 build failure on Solaris 10

From: "Daniel Berger" <Daniel.Berger@...>
Date: 2006-06-30 13:18:26 UTC
List: ruby-core #8106
ville.mattila@stonesoft.com wrote:
> "Daniel Berger" <Daniel.Berger@qwest.com> wrote on 29.06.2006 22:57:10:
> 
>> ville.mattila@stonesoft.com wrote:
>>> -solaris*2.10)  ac_cv_func_isinf=yes
>>> +solaris*2.10)  if test -z "$GCC"; then
>>> +                      ac_cv_func_isinf=yes
>>> +              fi
>>>                 LIBS="-lm $LIBS"
>>>                ;;
>>>  *) LIBS="-lm $LIBS";;
>>>
>>>
>> Actually, shouldn't we test for the feature instead of the platform? I 
> don't 
>> remember if older versions of Solaris have this.
>>
>> So, AC_CHECK_LIB(sunmath, isinf) && AC_CHECK_HEADER(sunmath.h, isinf), 
> with 
>> #ifdef's in the source?
>>
> 
>   I think this would add more code to source, now we only have to touch to 
> 
>   configure.in.
> 
>  - Ville
>  
> 

I don't totally understand how the build process works, which is part of my 
problem.  For example, I see a missing.h, and I can see AC_REPLACE_FUNCS in the 
configure.in file, but I'm not sure if/how they're tied together.  Within 
missing.h I see this:

#ifndef HAVE_ISINF
# if defined(HAVE_FINITE) && defined(HAVE_ISNAN)
# define isinf(x) (!finite(x) && !isnan(x))
# else
extern int isinf _((double));
# endif
#endif

So, in simple terms I think the logic should be:

a) On the Solaris platform...

b) If a) is true and the sunmath lib is present, and it contains the isinf 
function, then link against it.

c) If both a) and b) are true and the sunmath.h header file is present, and it 
contains the isinf function, then include it.

d) If a) or b) fail then resort to the implementation in missing.h.  This 
wouldn't require adding more source code from what I can gather, though I'm not 
positive.

Does that seem reasonable?  I would try to implement this myself, but I'm not 
sure how.

Regards,

Dan


This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.


In This Thread