Tru64 is unhappy with [EMAIL PROTECTED]:
Failed Test Stat Wstat Total Fail Failed List of
Failed
---
../lib/ExtUtils/CBuilder/t/02-lin51 20.00% 5
run/exit.t
#define WNOHANG 0x1
#define WUNTRACED 0x2
#define _WSTOPPED 0177
#ifdef _BSD
#define _W_INT(w) (*(int *)(w)) /* convert union wait to int */
#else
#define _W_INT(i) (i)
#endif
#define _WSTATUS(x) (_W_INT(x) _WSTOPPED)
#if ( !defined(_OSF_SOURCE)
I'm pulling out HASATTRIBUTE in favor of the more specific
HASATTRIBUTE_xxx.
Also, I've added two more attributes that we check for that weren't in
the first patch.
Jarkko, you define HASATTRIBUTE in a SYMBIAN block in perl.h, but undef
__attribute__. Why? What does HASATTRIBUTE give
Automated smoke report for 5.9.3 patch 24501
TANGAROA.uk.radan.com: Intel(R) Pentium(R) 4 CPU 2.00GHz(~1992 MHz) (x86/1 cpu)
onMSWin32 - WinXP/.Net SP1
using cl version 12.00.8804
smoketime 10 hours 50 minutes (average 27 minutes 7 seconds)
Summary: FAIL(F)
O = OK F =
Jarkko Hietaniemi [EMAIL PROTECTED] writes:
Tru64 is unhappy with [EMAIL PROTECTED]:
Failed Test Stat Wstat Total Fail Failed List of
Failed
---
../lib/ExtUtils/CBuilder/t/02-lin
On 2005-05-18, at 14:00:23 +0100, Dave Mitchell wrote:
Based an a suggestion from Jarkko, I've tried building bleed with
-Dregister=
and timed 'make test' a few times.
This is Linux FC3, GCC 3.4.3, Athlon 750Mhz, in single-user mode.
There seems to be a slight advantage having the
On Fri, May 13, 2005 at 09:40:33PM -0400, John Peacock wrote:
calculations (which means occasionally updating the database)? Most
especially, do we break ranks with POSIX (which apparently demands that
2100 be a leap year, even though it isn't).
I would assume here that if POSIX turns out
Nicholas Clark [EMAIL PROTECTED] writes:
On Fri, May 13, 2005 at 09:40:33PM -0400, John Peacock wrote:
calculations (which means occasionally updating the database)? Most
especially, do we break ranks with POSIX (which apparently demands that
2100 be a leap year, even though it
Gisle Aas wrote:
This bug in the specs was fixed in POSIX:2001. See
http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_14
for the current definition of POSIX time.
Excellent! Based on the history (IEEE Std 1003.1 was originally published in
1988 and became ISO/IEC
Nicholas Clark wrote:
I would assume here that if POSIX turns out currently to be stating this and
doesn't change, then Linux (or glibc, whichever is important here) will treat
2100 as not-a-leap-year, POSIX-be-damned, and POSIX will end up following.
Well, the reality of the thing is that current
Automated smoke report for 5.9.3 patch 24503
fixit.xs4all.nl: Pentium II (i386/1 cpu)
onbsd/os - 4.1
using cc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
smoketime 4 hours 10 minutes (average 2 hours 5 minutes)
Summary: FAIL(F)
O = OK F = Failure(s), extended
# New Ticket Created by Steve Hay
# Please include the string: [perl #35877]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35877
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of
# New Ticket Created by Salvador Fandio
# Please include the string: [perl #35878]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35878
To: [EMAIL PROTECTED]
Subject: goto xsub that croaks corrupts memory
Cc: [EMAIL
On Thu, May 19, 2005 at 12:22:07PM -, Salvador Fandiño wrote:
Run tryme.pl from the module attached to see it happening:
The file you attached, goto_and_croak-0.01.tar.gz, does not appear to
be in gz (nor bz2, tar, or zip) format.
--
My Dad used to say 'always fight fire with fire', which
Steve Hay (via RT) wrote:
I believe that the following program should print OK 5 times over, but
it prints NOT OK from the first line.
print qq[10\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
print qq[1\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
print qq[10\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
I believe that the following program should print OK 5
times over, but it prints NOT OK from the first line.
Do you mean the first test fails only (which is what I see) or that all of
them fail?
print qq[10\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
print qq[1\n] =~ /\d+$ \n/ix ? OK\n : NOT
Rafael Garcia-Suarez wrote:
Steve Hay (via RT) wrote:
I believe that the following program should print OK 5 times over, but
it prints NOT OK from the first line.
print qq[10\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
print qq[1\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
print qq[10\n] =~ /\d+$ \n/ix
On Thu, May 19, 2005 at 01:53:16PM +0100, Dave Mitchell wrote:
On Thu, May 19, 2005 at 12:22:07PM -, Salvador Fandiño wrote:
Run tryme.pl from the module attached to see it happening:
The file you attached, goto_and_croak-0.01.tar.gz, does not appear to
be in gz (nor bz2, tar, or zip)
On Thu, May 19, 2005 at 02:15:11PM +0100, Nicholas Clark wrote:
It's become UTF-8 encoded. Using my handy de-utf-8 tool:
$ perl -C1 -pe0 goto_and_croak-0.01.tar.gz | tar tfz -
Oooh, shiney :-)
I can reproduce the goto bug in bleed. I'm a bit busy at the moment,
so I'll try to look at it in
I'm not sure if this a bug in RT, or in the mail system at bugs.perl.org,
but for the mail that creates the initial tickets, it seems that all
attachments are converted bytes-UTF-8.
All attachments or all text/* attachments?
Nicholas Clark
--
Automated smoke report for 5.9.3 patch 24503
mccoy.peters.homeunix.org: Intel Pentium III (GenuineIntel 686-class, 512KB
L2 cache) (i386/1 cpu)
onopenbsd - 3.7
using cc version 3.3.5 (propolice)
smoketime 9 hours 22 minutes (average 1 hour 10 minutes)
Summary: FAIL(F)
O
Here it is, the all-singing, all-dancing, Jarrko-pleasing (I hope) patch
for configuring attributes. Many many files changed, mostly hints and
headers. I understand that Merijn will have to modify stuff behind the
scenes to do Configure.
* The d_attribut parm no longer exists. It's replaced
attached patch teaches B::Concise to see XS code,
so now it reports 'foo is XS code' when thats appropriate,
rather than 'foo has no START'.
concise-xs.t tests it against B, Digest::MD5, and Data::Dumper,
each in core, and with a known list of XS funcs.
These 3 pkgs yield 276 tests in threaded,
Andy
What is the recommended way to test -Wformat on the extensions:
make all OPTIMIZE=-Wall
?
Robin
---
This e-mail and any attachments may contain confidential and/or
privileged material; it is for the intended
On 18 May 2005 08:30:44 -, via RT yves orton
[EMAIL PROTECTED] wrote:
# New Ticket Created by yves orton
# Please include the string: [perl #35857]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35857
This
# New Ticket Created by Salvador Fandio
# Please include the string: [perl #35884]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35884
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help
# New Ticket Created by Salvador Fandio
# Please include the string: [perl #35885]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=35885
To: [EMAIL PROTECTED]
Subject: qw and x operators doesn't mix
Cc: [EMAIL
Gisle Aas wrote:
Jarkko Hietaniemi [EMAIL PROTECTED] writes:
Tru64 is unhappy with [EMAIL PROTECTED]:
Failed Test Stat Wstat Total Fail Failed List of
Failed
---
At 2005-05-18 08:30:44 -, [EMAIL PROTECTED] wrote:
The following program demonstrates that with one module using
warnings::register the output is as expected, with two modules
using it the output changes to be an ugly assignment statement.
The attached patch fixes the problem.
Thanks,
Jim Cromie wrote:
attached patch teaches B::Concise to see XS code,
so now it reports 'foo is XS code' when thats appropriate,
rather than 'foo has no START'.
Jim, is that related to:
https://rt.perl.org/rt3/Ticket/Display.html?id=35849
--
Stas Bekman wrote:
Jim Cromie wrote:
attached patch teaches B::Concise to see XS code,
so now it reports 'foo is XS code' when thats appropriate,
rather than 'foo has no START'.
Jim, is that related to:
https://rt.perl.org/rt3/Ticket/Display.html?id=35849
only insofar as it (yout ticket) prompted
Stas Bekman wrote:
Jim Cromie wrote:
attached patch teaches B::Concise to see XS code,
so now it reports 'foo is XS code' when thats appropriate,
rather than 'foo has no START'.
Jim, is that related to:
https://rt.perl.org/rt3/Ticket/Display.html?id=35849
um, I should hedge a bit here.
Jim Cromie wrote:
Stas Bekman wrote:
Jim Cromie wrote:
attached patch teaches B::Concise to see XS code,
so now it reports 'foo is XS code' when thats appropriate,
rather than 'foo has no START'.
Jim, is that related to:
https://rt.perl.org/rt3/Ticket/Display.html?id=35849
um, I should hedge a
On Thu, 19 May 2005 08:37 +0200, H.Merijn Brand [EMAIL PROTECTED] wrote:
Automated smoke report for 5.9.3 patch 24501
d3: PA8000 (PA-2.0/32/1 cpu)
onhp-ux - 10.20
using cc version A.10.32.30
smoketime 9 hours 16 minutes (average 2 hours 19 minutes)
:
Failures:
On Thu, May 19, 2005 at 04:12:45PM -, Salvador Fandiño wrote:
for instance:
$ perl -e '@foo = qw(foo bar) x 3'
Number found where operator expected at -e line 1, near x 3
(Do you need to predeclare x?)
syntax error at -e line 1, near qw(foo bar) x
Execution of -e
On Thu, May 19, 2005 at 07:46:20PM +0300, Jarkko Hietaniemi wrote:
Looks like perl -e 'kill 15, $$; sleep(1)' will not be killed by the
signal but exits normally instead. Is that the case? What is $? from
It is killed immediately.
OpenBSD sees the same test failures.
the shell
H.Merijn Brand [EMAIL PROTECTED] writes:
ok 9 - WEXITSTATUS
sh: 9508 Terminated
not ok 10 - Term by signal
What happens is that the shell interferes on some platforms and change
the status returned back to perl. This patch made this test failure
go away on HP-UX. Hopefully this fixes the
http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.29.tar.gz
or
http://svn.schwern.org/svn/CPAN/ExtUtils-MakeMaker/trunk
or
a CPAN near you.
This release fixes a problem with PL_FILES where the functionality was
changed in 6.25. I put it back the way it was because several CPAN modules
On 19 May 2005 14:26:46 -0700, Gisle Aas [EMAIL PROTECTED] wrote:
What happens is that the shell interferes on some platforms and change
the status returned back to perl. This patch made this test failure
go away on HP-UX. Hopefully this fixes the failure seen on some other
platforms as
Because the intention of the patch was exactly that you should be able
to assume the traditional UNIX/POSIX semantics for $?.
That's a bold claim given that e.g. signals, or a process being stopped,
or the concept of core dump, may or may not be supported in non-UNIX
(*) operating
On Thu, May 19, 2005 at 11:49:02PM +0100, Nicholas Clark wrote:
Is this a direction we want to go? Should I tidy up the portability nits
and commit these to blead?
Sounds good to me. A most excellent piece of displacement activity ;-)
--
You live and learn (although usually you just live).
Orton, Yves [EMAIL PROTECTED] wrote:
[Steve Hay wrote:]
: I believe that the following program should print OK 5
: times over, but it prints NOT OK from the first line.
:
:Do you mean the first test fails only (which is what I see) or that all of
:them fail?
I also see just the first fail - I
On Thu, May 19, 2005 at 02:03:45PM +0100, Steve Hay wrote:
Rafael Garcia-Suarez wrote:
Steve Hay (via RT) wrote:
I believe that the following program should print OK 5 times over, but
it prints NOT OK from the first line.
print qq[10\n] =~ /\d+$ \n/ix ? OK\n : NOT OK\n;
print
On Thu, May 19, 2005 at 09:37:39AM +0300, Jarkko Hietaniemi wrote:
Tru64 is unhappy with [EMAIL PROTECTED]:
Failed Test Stat Wstat Total Fail Failed List of
Failed
---
On Thu, May 19, 2005 at 02:11:00PM +0200, [EMAIL PROTECTED] wrote:
Inconsistent test results (between TEST and harness):
../lib/ExtUtils/CBuilder/t/02-link.tFAILED at test 5
Can I see verbose test output (both stderr and stdout) for that?
A compiler or linker that clutters up stdout
On Thu, May 19, 2005 at 10:18:43PM +0200, H.Merijn Brand wrote:
Inconsistent test results (between TEST and harness):
../lib/ExtUtils/CBuilder/t/02-link.tFAILED--expected 5 tests, saw 3
1..5
# Running under perl version 5.009003 for hpux
# Current time local: Thu May 19 22:12:20
46 matches
Mail list logo
