On Sat, Sep 17, 2005 at 05:20:30PM +0100, Jochen Voss wrote:
> Hello,
>
> recompiling eperl fixed the segfault for me.
> The file from my original email processes fine, now.
> Maybe the problem is related to one of the many
> transitions in unstable?
Hi Jochen,
as eperl has not been uploaded recently, it looks like this breakage
came from Perl upgrade; unfortunately it does not happen on i386,
as you noticed. I could make a new upload to fix this bug, but
I prefer to find the reason of this breakage. For this, I need
an eperl binary not stripped (and with debugging symbols) compiled
on a sarge box. I will then run it on unstable dchroots of a
powerpc Debian machine.
I could not find a suitable machine with libperl-dev from stable,
can you please provide such an eperl binary?
FYI, here is a simpler test case:
<:
use POSIX qw(strftime);
print strftime "%d.%m.%Y", localtime;
:>
On Sat, Sep 17, 2005 at 05:20:30PM +0100, Jochen Voss wrote:
> Hello,
>
> recompiling eperl fixed the segfault for me.
> The file from my original email processes fine, now.
> Maybe the problem is related to one of the many
> transitions in unstable?
Hi Jochen,
as eperl has not been uploaded recently, it looks like this breakage
came from Perl upgrade; unfortunately it does not happen on i386,
as you noticed. I could make a new upload to fix this bug, but
I prefer to find the reason of this breakage. For this, I need
an eperl binary not stripped (and with debugging symbols) compiled
on a sarge box. I will then run it on unstable dchroots of a
powerpc Debian machine.
I could not find a suitable machine with libperl-dev from stable,
can you please provide such an eperl binary?
FYI, here is a simpler test case:
<:
use POSIX qw(strftime);
print strftime "%d.%m.%Y", localtime;
:>
Thanks
Denis