[#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:

Solaris patches for configure.in work!

From: "Daniel Berger" <Daniel.Berger@...>
Date: 2006-06-30 14:49:05 UTC
List: ruby-core #8110
I applied both Ville's isinf patch and Andrew's patch for -shared (ruby-core: 
7791) and both worked fine against the nightly snapshot (I messed up Andrew's 
patch earlier, btw).

Here's the total diff (based on the 30-Jun-2006 stable snapshot):


 >diff -u configure.in.orig configure.in
--- configure.in.orig   Fri Jun 30 08:38:58 2006
+++ configure.in        Fri Jun 30 08:23:52 2006
@@ -417,8 +417,10 @@
                 ;;
  superux*)     ac_cv_func_setitimer=no
                ;;
-solaris*2.10)  ac_cv_func_isinf=yes
-               LIBS="-lm $LIBS"
+solaris*2.10) if test -z "$GCC"; then
+                 ac_cv_func_isinf=yes
+              fi
+              LIBS="-lm $LIBS"
                ;;
  *) LIBS="-lm $LIBS";;
  esac
@@ -910,10 +912,9 @@
                         : ${LIBPATHENV=SHLIB_PATH}
                         rb_cv_dlopen=yes;;
         solaris*)       if test "$GCC" = yes; then
-                          : ${LDSHARED='$(CC) -Wl,-G'}
+                          : ${LDSHARED='$(CC) -shared'}
                            if test "$rb_cv_prog_gnu_ld" = yes; then
                                LDFLAGS="$LDFLAGS -Wl,-E"
-                              LDSHARED="$LDSHARED -shared"
                            fi
                         else
                            : ${LDSHARED='ld -G'}

I applied both patches individually, re-ran autoconf, configure and make with 
both gcc 3.4.5 and the Sun compiler that ships with Sun Studio 11 (cc: Sun C 
5.8 2005/10/13).  I didn't pass any special options to either compiler.

Both worked fine.

Regards,

Dan

PS - I'm running into issues with Sun's cc and OpenSSL.  More later...


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

Prev Next