On Tue, Nov 30, 2004 at 03:19:09PM +0100, Rafael Garcia-Suarez wrote:
Change 23183 by [EMAIL PROTECTED] on 2004/08/02 09:16:13
Remove empty rpath from .so files
Does it make sense to do the same with the other options there?
EXTRALIBS, LDLOADLIBS, etc...?
--
Michael G Schwern
Michael G Schwern wrote:
On Tue, Nov 30, 2004 at 03:19:09PM +0100, Rafael Garcia-Suarez wrote:
Change 23183 by [EMAIL PROTECTED] on 2004/08/02 09:16:13
Remove empty rpath from .so files
Does it make sense to do the same with the other options there?
EXTRALIBS, LDLOADLIBS,
On Tue, Nov 30, 2004 at 03:38:32PM -, Ingo Weinhold wrote:
lib/ExtUtils/t/MM_BeOS.t
* fixed number of tests and initialized a variable to some useful value
Thanks. Caught this for the CPAN version.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It's
On Wed, Dec 01, 2004 at 08:04:08AM +0200, Jarkko Hietaniemi wrote:
I re-setup Perl smokes in a Tru64 box after some bit rot had disabled
my old smoke setup. Otherwise smoking along nicely, but under a UTF-8
Thanks.
locale there is some test noise that doesn't seem to affect success.
I can't
This does for vms/descrip_mms.template what the Unix build does for the
scripts in utils and pod, which is run them with ../lib in @INC so they
can locate Config_heavy.pl when it gets loaded at run time.
--- vms/descrip_mms.template;-0 Tue Nov 30 09:59:22 2004
+++ vms/descrip_mms.templateTue
Automated smoke report for 5.9.2 patch 23577 on bsd/os - 4.1 (i386/1 cpu)
(fixit.xs4all.nl) using version
Report by Test::Smoke v1.18.09 (perl 5.00503) [3 hours 4 minutes]
O = OK F = Failure(s), extended report at the bottom
X = test(s) failed under TEST but not under harness
? = still running
On Wed 01 Dec 2004 14:24, Craig A. Berry [EMAIL PROTECTED] wrote:
This does for vms/descrip_mms.template what the Unix build does for the
scripts in utils and pod, which is run them with ../lib in @INC so they
can locate Config_heavy.pl when it gets loaded at run time.
Thanks, applied as
On Tue 30 Nov 2004 16:38, Ingo Weinhold (via RT) [EMAIL PROTECTED] wrote:
# New Ticket Created by Ingo Weinhold
# Please include the string: [perl #32717]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32717
On Wed, Dec 01, 2004 at 03:12:36PM +0100, H.Merijn Brand wrote:
4) I haven't updated the README.beos yet, since I'd rather wait for your
reply first. I'm also not quite sure how to do this best. Apparently
someone wrote it once and someone else added an `Update 2002-05-30'
section. So I
On Wed, Dec 01, 2004 at 07:24:45AM -0600, Craig A. Berry wrote:
This does for vms/descrip_mms.template what the Unix build does for the
scripts in utils and pod, which is run them with ../lib in @INC so they
can locate Config_heavy.pl when it gets loaded at run time.
With this does VMS now
At 2:25 PM + 12/1/04, Nicholas Clark wrote:
On Wed, Dec 01, 2004 at 07:24:45AM -0600, Craig A. Berry wrote:
This does for vms/descrip_mms.template what the Unix build does for the
scripts in utils and pod, which is run them with ../lib in @INC so they
can locate Config_heavy.pl when it gets
The patch against perl.h was wrong.
This is a patch that does the right thing but produces odd text for
MALLOC_TOO_LATE_FOR
Use the attachment (not the text below) to patch, as the white space is munged.
Is there anyway to test for broken macro definitions.
Robin
--- ./perl.h Thu Sep 9
perl #32446 describes a bug with perl5.8 on OpenBSD, where a STDOUT gets
duped to a socket and a close(STDOUT) later leaves the socket open.
Attached is a proposed and tested fix for the problem, which simply
duplicates the FreeBSD code for OpenBSD.
Details:
In perlio.c there is a function
This patch:
On Thu, Nov 04, 2004 at 02:59:25AM -0800, Rafael Garcia-Suarez wrote:
Change 23471 by [EMAIL PROTECTED] on 2004/11/04 09:26:56
Subject: [PATCH blead] [perl #3038] Re: $qr = qr/^a$/m; $x =~ $qr; fails
From: Rick Delaney [EMAIL PROTECTED]
Date: Sun, 31 Oct 2004
[EMAIL PROTECTED] - Tue Nov 13 00:33:50 2001]:
Now again: Can you produce a *working* *subset* of your current script
that reproduces the error you had been mentioning?
After a lot of fiddling, I have determined that the cause of the error was
something completely unrelated to what I
[sky - Sat Apr 26 03:02:29 2003]:
Hi,
Could you try the maint snapshot that is going to be 5.8.1 at
http://www.iki.fi/jhi/[EMAIL PROTECTED] or
http://www.iki.fi/jhi/[EMAIL PROTECTED]
Thanks Arthur
With Perl 5.8.6, I got none of the test failures mentioned in the
original
Craig A. Berry [EMAIL PROTECTED] wrote:
:In article [EMAIL PROTECTED], [EMAIL PROTECTED]
:wrote:
: I think it would set a bad precedent to have a core module ignoring
: changes affecting @INC.
:
:It would only ignore run-time changes to @INC or run-time changes to
:the current working directory
I seemed to be extremely lucky in getting gmake -j3 to stomp all
over the place when doing the mktables step: either two or three
mktables getting invoked and trying to run simultaneously, sometimes
miraculously not corrupting any files, but most of the time failing
in various mysterious ways.
On Wed 01 Dec 2004 18:21, Jarkko Hietaniemi [EMAIL PROTECTED] wrote:
I seemed to be extremely lucky in getting gmake -j3 to stomp all
over the place when doing the mktables step: either two or three
mktables getting invoked and trying to run simultaneously, sometimes
miraculously not
On Wed, Dec 01, 2004 at 06:28:11PM +0100, H.Merijn Brand wrote:
I can imagine the pain, but this patch comes nowhere near the state of the
bleading edge Makefile.SH
Which version did you patch against?
It's prior to my Config.pm changes. I can see how to hand apply it.
Nicholas Clark
Sorry, but Win32::Console is not part of the core Perl
distribution. It
is part of the core ActiveState distribution, so you can
report the bug
to them at http://bugs.activestate.com//ActivePerl/query.cgi.
Im just curious about this. Is there a good reason why the core Win32
modules are
Orton, Yves wrote:
Im just curious about this. Is there a good reason why the core Win32
modules are NOT considered to be Core perl in general? Are there any other
OS'es where core perl doesn't deploy with what most users of that os would
consider to be standard modules?
You should ask
locale there is some test noise that doesn't seem to affect success.
I can't recreate this. I've tried with both nl_NL.utf8 and fa_IR.utf8
with no joy
The curious part is that if the test is run manually, no noise:
.../t ; env PERL_CORE=1 LC_ALL=fi_FI.UTF-8 ./perl -I../lib ../ext/B/t/xref.t
Rafael Garcia-Suarez said on 01 December 2004 18:45
Orton, Yves wrote:
Im just curious about this. Is there a good reason why the core Win32
modules are NOT considered to be Core perl in general? Are there any
other
OS'es where core perl doesn't deploy with what most users of that os
Nicholas Clark wrote:
On Wed, Dec 01, 2004 at 06:28:11PM +0100, H.Merijn Brand wrote:
I can imagine the pain, but this patch comes nowhere near the state of the
bleading edge Makefile.SH
Last night? :-) (23565)
Which version did you patch against?
It's prior to my Config.pm changes. I
Orton, Yves wrote:
Consider that libwin32 hasn't been updated on CPAN since 08 Jul 2002
(libwin32-0.191).
I am sympathetic to the point about not wanting to add a whole host of
modules to the core, especially if they are specific to only one OS, but IMO
it seems that libwin32 should at
On Wed 01 Dec 2004 19:29, Jarkko Hietaniemi [EMAIL PROTECTED] wrote:
Nicholas Clark wrote:
On Wed, Dec 01, 2004 at 06:28:11PM +0100, H.Merijn Brand wrote:
I can imagine the pain, but this patch comes nowhere near the state of the
bleading edge Makefile.SH
Last night? :-) (23565)
Ahh.
On Wed, 01 Dec 2004, Orton, Yves wrote:
Consider that libwin32 hasn't been updated on CPAN since 08 Jul 2002
(libwin32-0.191).
I have a copy of most/all patches that have been submitted to Sarathy
over the time and I plan to integrate them sometime early next year and
upload a new version to
Jan Dubois wrote on 01 December 2004 19:52
On Wed, 01 Dec 2004, Orton, Yves wrote:
Consider that libwin32 hasn't been updated on CPAN since 08 Jul 2002
(libwin32-0.191).
I have a copy of most/all patches that have been submitted to Sarathy
over the time and I plan to integrate them
On Wed, Dec 01, 2004 at 07:21:25PM +0200, Jarkko Hietaniemi wrote:
I seemed to be extremely lucky in getting gmake -j3 to stomp all
over the place when doing the mktables step: either two or three
mktables getting invoked and trying to run simultaneously, sometimes
miraculously not corrupting
On Wed, Dec 01, 2004 at 10:52:19AM -0800, Jan Dubois [EMAIL PROTECTED] wrote:
On Wed, 01 Dec 2004, Orton, Yves wrote:
Consider that libwin32 hasn't been updated on CPAN since 08 Jul 2002
(libwin32-0.191).
I have a copy of most/all patches that have been submitted to Sarathy
over the time
On Wed, 01 Dec 2004, Yitzchak Scott-Thoennes wrote:
Perhaps a new mailing list is in order? If a perl.org [*]perl-libwin32
list were started and you post what you have, someone might take the
work off your shoulders, and a beta release go out. Who actually has
the PAUSE rights to upload the
On Wed, Dec 01, 2004 at 08:14:11PM +0200, Jarkko Hietaniemi wrote:
Sadly, no valgrind for Tru64. There's the third tool, but it
doesn't show any funny business going on with the xref.t.
I managed to cut down the xref.t (I lost one of the two warnings,
though, hopefully one is enough) to
On Tue, Nov 23, 2004 at 01:44:15AM -0800, Rafael Garcia-Suarez wrote:
Change 23525 by [EMAIL PROTECTED] on 2004/11/23 09:09:57
Subject: [PATCH] warnings.t portability tweaks
From: Craig A. Berry [EMAIL PROTECTED]
Date: Sat, 20 Nov 2004 10:29:47 -0600
Message-ID:
[EMAIL PROTECTED] - Sun May 25 14:27:36 2003]:
This is a build failure report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.34 running under perl v5.8.1.
-
[Please enter your report here]
Testing
[stmpeters - Tue Oct 19 07:13:13 2004]:
[EMAIL PROTECTED] - Fri Oct 15 08:32:53 2004]:
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.35 running under perl v5.8.5.
(but manually sent by email)
Ask, would you set up a [EMAIL PROTECTED] list?
On Wed, Dec 01, 2004 at 11:56:11AM -0800, Jan Dubois [EMAIL PROTECTED] wrote:
On Wed, 01 Dec 2004, Yitzchak Scott-Thoennes wrote:
Perhaps a new mailing list is in order? If a perl.org [*]perl-libwin32
list were started and you post what you
Sadly, no valgrind for Tru64. There's the third tool, but it
doesn't show any funny business going on with the xref.t.
I managed to cut down the xref.t (I lost one of the two warnings,
though, hopefully one is enough) to the minimal version that still
gives the \xB8 warning (with env
Argh, duh. Please ignore my earlier analysis, mostly.
I need to go back to the beginning and redo the cutting
down exercise.
Nicholas Clark
--
Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this
special
biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
Jarkko Hietaniemi wrote:
Argh, duh. Please ignore my earlier analysis, mostly.
I need to go back to the beginning and redo the cutting
down exercise.
Now I know more - useithreads matters. The breakage happens
with the combination of -Duseithreads and the UTF-8 locales.
Fun. Could we get
Jarkko Hietaniemi wrote:
Jarkko Hietaniemi wrote:
Argh, duh. Please ignore my earlier analysis, mostly.
I need to go back to the beginning and redo the cutting
down exercise.
Now I know more - useithreads matters. The breakage happens
with the combination of -Duseithreads and the UTF-8
Has anyone put online a call-tree for perl? (I don't mean for Perl
scripts, but for the program perl.)
Thanks!
kj
On Wed, Dec 01, 2004 at 11:59:13PM +0200, Jarkko Hietaniemi wrote:
Jarkko Hietaniemi wrote:
Jarkko Hietaniemi wrote:
Argh, duh. Please ignore my earlier analysis, mostly.
I need to go back to the beginning and redo the cutting
down exercise.
Now I know more - useithreads matters.
[EMAIL PROTECTED] - Sat Jul 29 16:25:22 2000]:
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.28 running under perl v5.6.0.
-
[Please enter your report here]
I kept getting
On Wed, Dec 01, 2004 at 10:20:07PM -, Steve Peters via RT wrote:
The line to change in the proposed patch no longer exists in
ExtUtil::MM_Win32 version 1.10. Please upgrade to a more recent version
if you are still having this problem.
I don't think you should be setting old, valid bugs
On Wed, Dec 01, 2004 at 10:15:55PM +, Nicholas Clark wrote:
On Wed, Dec 01, 2004 at 11:59:13PM +0200, Jarkko Hietaniemi wrote:
Jarkko Hietaniemi wrote:
Now I know more - useithreads matters. The breakage happens
with the combination of -Duseithreads and the UTF-8 locales.
Fun.
On Wed, Dec 01, 2004 at 05:13:47PM -0500, [EMAIL PROTECTED] wrote:
Has anyone put online a call-tree for perl? (I don't mean for Perl
scripts, but for the program perl.)
There used to be pxr.perl.org that Arthur Bergman put together about
three years ago, but that seems to have disappeared.
[EMAIL PROTECTED] - Mon Jul 30 16:58:10 2001]:
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.33 running under perl v5.7.2.
-
[Please enter your report here]
I built perl 5.7.2
On Wed, 01 Dec 2004 18:24:28 GMT, Orton, Yves wrote:
Rafael Garcia-Suarez said on 01 December 2004 18:45
Orton, Yves wrote:
Im just curious about this. Is there a good reason why the core Win32
modules are NOT considered to be Core perl in general? Are there any
other
OS'es where core perl
Hello,
I am studying perl internals and I am trying to write my own B compiler
backend. Unfortunately I have just managed to crash perl.
B::SegFault is attached and it seems to be rather simple.
Here is how to reproduce:
$ ls lib/B/SegFault.pm
lib/B/SegFault.pm
$ perl -Ilib -MO=SegFault
At 8:07 PM + 12/1/04, Nicholas Clark wrote:
On Tue, Nov 23, 2004 at 01:44:15AM -0800, Rafael Garcia-Suarez wrote:
Change 23525 by [EMAIL PROTECTED] on 2004/11/23 09:09:57
Subject: [PATCH] warnings.t portability tweaks
From: Craig A. Berry [EMAIL PROTECTED]
Date: Sat, 20 Nov
The attached patch makes the changes necessary to doio.c to use
strlcat() and strlcpy() instead of strcat() and strcpy() on environments
where these functions are available.
Comments or questions are welcome.
Steve Peters
[EMAIL PROTECTED]
--- perl-current/doio.c Sat Jul 31 11:44:58 2004
I had a peek last night at the change log of Debian's perl. Saw some
security fixes I don't remember having seen come back to p5p.
http://packages.debian.org/changelogs/pool/main/p/perl/perl_5.8.4-4/changelog
http://ftp.debian.org/debian/pool/main/p/perl/perl_5.8.4-4.diff.gz
perl (5.8.4-4)
On Wed, Dec 01, 2004 at 09:05:36PM -0500, Michael G Schwern wrote:
I had a peek last night at the change log of Debian's perl. Saw some
security fixes I don't remember having seen come back to p5p.
Yes, a bunch of patches for insecure tempfile use which trustix has
applied.
The patch against
On Thu, Dec 02, 2004 at 01:42:17PM +1100, Brendan O'Dea wrote:
--- perl-5.8.4.orig/ext/DB_File/t/db-recno.t 2003-12-28 07:37:53.0
+1100
+++ perl-5.8.4/ext/DB_File/t/db-recno.t 2004-11-07 02:07:29.0
+1100
@@ -1198,7 +1198,7 @@
my $testnum = 181;
my $failed = 0;
[stmpeters - Wed Dec 01 12:13:03 2004]:
[EMAIL PROTECTED] - Sun May 25 14:27:36 2003]:
This is a build failure report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.34 running under perl v5.8.1.
On 2004-12-02, at 04:29:47 -, Steve Peters via RT wrote:
[stmpeters - Wed Dec 01 12:13:03 2004]:
[EMAIL PROTECTED] - Sun May 25 14:27:36 2003]:
This is a build failure report for perl from [EMAIL PROTECTED],
generated with the help of perlbug 1.34 running under perl v5.8.1.
Not actually a UTF8 bug. valgrind still screams without any UTF8.
It's something ithreads.
Yeah, it's more like an ithreads bug that gets exposed because
the resulting garbage doesn't pass up as valid UTF-8.
Does this give anyone a hunch as to the cause?
Double free? Something not
[EMAIL PROTECTED] - Thu Jun 21 03:08:05 2001]:
-
[Please enter your report here]
$ perl -we 'open(X, /etc/motd);X'
$ perl -Mstrict -e 'open(X, /etc/motd);X'
$ perl -we 'open(X, /etc/motd);readline(X)'
Name main::X
Steve Peters via RT wrote:
[EMAIL PROTECTED] - Thu Jun 21 03:08:05 2001]:
-
[Please enter your report here]
$ perl -we 'open(X, /etc/motd);X'
$ perl -Mstrict -e 'open(X, /etc/motd);X'
$ perl -we 'open(X, /etc/motd);readline(X)'
On Thu, Dec 02, 2004 at 06:14:20AM +0100, Marcus Holland-Moritz wrote:
On 2004-12-02, at 04:29:47 -, Steve Peters via RT wrote:
[stmpeters - Wed Dec 01 12:13:03 2004]:
[EMAIL PROTECTED] - Sun May 25 14:27:36 2003]:
This is a build failure report for perl from [EMAIL
On Wed, Dec 01, 2004 at 08:31:55AM -0600, Craig A. Berry wrote:
At 2:25 PM + 12/1/04, Nicholas Clark wrote:
On Wed, Dec 01, 2004 at 07:24:45AM -0600, Craig A. Berry wrote:
This does for vms/descrip_mms.template what the Unix build does for the
scripts in utils and pod, which is run them
62 matches
Mail list logo
