On Wed, 27 Jul 2005 17:48:00 +0200, Campo Weijerman <[EMAIL PROTECTED]> wrote:

> On Wed, Jul 27, 2005 at 05:26:33PM +0200, H.Merijn Brand wrote:
> > I already change the skip for sigaction.t in case either SIGRTMIN or
> > SIGRTMAX returns -1, as HP-UX 10.20 does, but AIX 4.3.3 is even worse, it
> > returns 888 and 999 both bogus. The offending part in the system header
> > file is below the suggested patch, which cannot be applied yes, because
> > p4 is down.
> 
> On my AIX 5.1 smoke boxes I've been getting
> 
> No such signal: 888 at ../lib/POSIX.pm line 111.
> No such signal: 888 at ../lib/POSIX.pm line 117.
> #     Failed test (../ext/POSIX/t/sigaction.t at line 189)
> #          got: undef
> #     expected: 'CODE(0x30441a38)'
> Unrecognized signal name "RTMIN" at ../ext/POSIX/t/sigaction.t line 190.
> # Looks like you planned 30 tests but only ran 28.
> # Looks like your test died just after 28.
> ext/POSIX/t/sigaction.....................FAILED at test 28
> ext/POSIX/t/sigaction.....................FAILED at test 28
> 
> AIX 5.3 seems okay though...
>  
> > /* Values for sigev_notify */
> > #define SIGEV_NONE      999
> > #define SIGEV_SIGNAL    999
> > #define SIGEV_THREAD    999
> > 
> > #define SIGRTMIN        888
> > #define SIGRTMAX        999
> 
> On AIX 5.1, I'm seeing the same SIGRT* defines, but not the SIGEV_* ones.
> 
> On AIX 5.2 and 5.3:
> 
> /* Values for sigev_notify */
> #define SIGEV_NONE      1
> #define SIGEV_SIGNAL    2
> #define SIGEV_THREAD    3
> 
> /*
>  * Define range for POSIX real-time signals.
>  * There must be at least RTSIG_MAX == _POSIX_RTSIG_MAX of these,
>  * and they must not overlap POSIX required signals like SIGUSR1.
>  */
> #define SIGRTMIN        50
> #define SIGRTMAX        57

Thanks. Can you, just to be sure, send me the output of

# perl -V:sig_count

I want to see if that is >= SIGRTMAX

> By the way, gcc is complaining:
> 
> POSIX.xs: In function 'XS_POSIX_sigaction':
> POSIX.xs:1348: warning: comparison of distinct pointer types lacks a cast
> POSIX.xs:1357: warning: assignment from incompatible pointer type

That's a difficult one being discussed. It seems that it is not easy to solve
since a pointer to data is not the same as a pointer to a function on some
systems

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2  on HP-UX 10.20, 11.00 & 11.11,
 AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,    perl QA: http://qa.perl.org
 reports  to: [EMAIL PROTECTED],                perl-qa@perl.org

Reply via email to