Call for testing: OpenSSH-6.2

[Iain Morgan]

On Fri, Mar 15, 2013 at 11:58:19 -0500, Tom Christensen wrote:
> On 03/15/2013 01:24 AM, Damien Miller wrote:
> > On Tue, 12 Mar 2013, Tom Christensen wrote:
> >
> >>> replaced with kill(0, SIGTERM) to achieve the same thing.
> >>>
> >> Any opinion on this one?
> >>
> >> Building openssh with -D_BSD_SIGNALS forced on causes numerous warnings like
> >> the below to appear:
> >
> > How did you enable this? Was it CFLAGS="-D_BSD_SIGNALS" ./configure ... or
> > by editing the Makefile after configure ran?
> >
> I did CC="gcc -D_BSD_SIGNALS" ./configure ...
> 
> > If you haven't, I'd recommend you try the CFLAGS/configure way so all the
> > configure tests have a chance to find and react to the exposed symbols.
> >
> I just double checked with CFLAGS="-D_BSD_SIGNALS" ./configure ...
> As expected it did not make a difference.
> 
> I did a build on IRIX 6.2 with SGI MIPSpro 7.3 and it had this to report:
> cc -D_BSD_SIGNALS  -I. -I.. -I. -I./.. -I/usr/tgcware/include/openssl 
> -I/usr/tgcware/include -DHAVE_CONFIG_H -c bsd-arc4random.c
> c-1047 cc: WARNING File = ../openbsd-compat/bsd-misc.h, Line = 103
>    Macro "signal" (declared at line 376 of "/usr/include/sys/signal.h") 
> has an
>            incompatible redefinition.
> 
>    #define signal(a,b) mysignal(a,b)
>            ^
> 
> 

I haven't had an IRIX system to play with for several years, but looking
back on my notes I see that it used to be necessary to set CC=c99 when
using the MIPSpro.

-- 
Iain Morgan