On Tue, 27 May 2014 16:49:35 +0200, Jens Thoms Toerring wrote:
> On Tue, May 27, 2014 at 03:01:18PM +0300, Damyan Ivanov wrote:
> > The hurd-i386 build fails with an undefined subroutine error:
> Looks like I got this fixed also (a missing '$self->' and a
> stray '=cut' - no idea why it wasn't als
Hi,
On Tue, May 27, 2014 at 03:01:18PM +0300, Damyan Ivanov wrote:
> The hurd-i386 build fails with an undefined subroutine error:
Looks like I got this fixed also (a missing '$self->' and a
stray '=cut' - no idea why it wasn't also flagged on other
systems...). Let's hope the new 0.20 version on
-=| Jens Thoms Toerring, 27.05.2014 09:21:42 +0200 |=-
>I realized that I can install a 32-bit version of Debian
> in a virtual box also on an 64-bit machine and that allowed
> me to find the reason for the failing tests. As you already
> may have suspected, it was a rather stupid mistake: I ha
Hi,
I realized that I can install a 32-bit version of Debian
in a virtual box also on an 64-bit machine and that allowed
me to find the reason for the failing tests. As you already
may have suspected, it was a rather stupid mistake: I had
forgotten to pass the CFLAGS Perl was build with to the
On 26/05/14 22:11, gregor herrmann wrote:
> On Mon, 26 May 2014 22:41:13 +0200, Jens Thoms Toerring wrote:
>
>> Is there any chance of someone temporarily giving me an account
>> on a type of machine where the tests fail or
>
> https://gcc.gnu.org/wiki/CompileFarm
If it's of any use I do have a
On Mon, 26 May 2014 22:41:13 +0200, Jens Thoms Toerring wrote:
> Is there any chance of someone temporarily giving me an account
> on a type of machine where the tests fail or
https://gcc.gnu.org/wiki/CompileFarm
https://dsa.debian.org/doc/guest-account/
might be possibilities.
> at least of ge
Hi,
On Mon, May 26, 2014 at 08:34:59PM +0200, gregor herrmann wrote:
> On Mon, 26 May 2014 17:57:34 +0200, Jens Thoms Toerring wrote:
> > Thank you very much. Unfortunately, CPAN testing has shown
> > that there are some systems where there are problems building
> > the complete module.
>
> The
On Mon, 26 May 2014 17:57:34 +0200, Jens Thoms Toerring wrote:
(trimming the CC list a bit)
> On Mon, May 26, 2014 at 12:39:51PM +0300, Damyan Ivanov wrote:
> > Package libfile-fcntllock-perl upgraded to 0.16 and uploaded to Debian
> > unstable.
> Thank you very much. Unfortunately, CPAN testing
Hi,
On Mon, May 26, 2014 at 12:39:51PM +0300, Damyan Ivanov wrote:
> Package libfile-fcntllock-perl upgraded to 0.16 and uploaded to Debian
> unstable.
Thank you very much. Unfortunately, CPAN testing has shown
that there are some systems where there are problems building
the complete module. Th
-=| Jens Thoms Toerring, 25.05.2014 23:01:34 +0200 |=-
>since I got no complaints about the new version of the
> File::FcntlLock module I just uploaded it to CPAN. I hope
> that it will help to avoid the problems you had with it.
Package libfile-fcntllock-perl upgraded to 0.16 and uploaded to
Hi,
since I got no complaints about the new version of the
File::FcntlLock module I just uploaded it to CPAN. I hope
that it will help to avoid the problems you had with it.
Best regards, Jens
--
\ Jens Thoms Toerring j...@toerring.de
\__
Hi,
thanks to your inputs I'm mostly through with a rework
of the File::FnctlLock module. It's now basically three
modules:
a) File::FcntlLock (or File::FcntlLock::XS as an alias) -
this is basically the old module, using XS,
b) File::FcntlLock::Pure - created during Perl "Makefile.PL"
Hi,
On Sun, May 18, 2014 at 07:24:25PM +0200, Guillem Jover wrote:
> Well, I think going for now with the pure perl version would solve
> our immediate problem, we could go over the rest separately. I just
> mentioned it now because it would avoid dropping an then having to
> reintroduce the XS co
On Sun, 2014-05-18 at 14:38:31 +0200, Jens Thoms Toerring wrote:
> On Sun, May 18, 2014 at 06:04:45AM +0200, Guillem Jover wrote:
> > What about, preserving the XS module, and make the code try to load it
> > and if not available, fall back to the new pure perl code? I think that
> > would palliate
Hi,
On Sun, May 18, 2014 at 06:04:45AM +0200, Guillem Jover wrote:
> What about, preserving the XS module, and make the code try to load it
> and if not available, fall back to the new pure perl code? I think that
> would palliate such concern.
That went over my head;-) Is that something I should
Hi!
On Sun, 2014-05-18 at 01:39:12 +0200, Jens Thoms Toerring wrote:
> On Fri, May 16, 2014 at 11:06:17PM +0300, Niko Tyni wrote:
> > Would it be possible to probe for the contents of the flock struct with C
> > code at build time, and then use that information to write out a pure perl
> > module
Hi,
On Fri, May 16, 2014 at 11:06:17PM +0300, Niko Tyni wrote:
> Would it be possible to probe for the contents of the flock struct with C
> code at build time, and then use that information to write out a pure perl
> module that regenerates the structs at run time (probably with pack())?
>
> It
Hi,
On Fri, May 16, 2014 at 11:06:17PM +0300, Niko Tyni wrote:
> > > Unfortunately, I also
> > > don't see any way to do things without XS since the flock
> > > structure that must be passed to fcntl(2) can be quite dif-
> > > ferent on different systems, both concerning the number and
> > > order
On Fri, May 16, 2014 at 05:54:26PM +0200, Guillem Jover wrote:
> On Fri, 2014-05-16 at 11:05:35 +0200, Jens Thoms Toerring wrote:
> > > Long term what I think would be best would be to get File::FcntlLock
> > > into the perl core distribution, preferably upstream, but I'm not sure
> > > how such pr
Hi,
On Fri, May 16, 2014 at 05:54:26PM +0200, Guillem Jover wrote:
> > ... But they might argue that you already can get
> > fcntl(2) used for locking instead of flock(2) by building Perl with
> > "-Ud_flock" (don't ask me why that's not the default anyway;-)
> > Perhaps building the Perl version
Hi!
On Fri, 2014-05-16 at 11:05:35 +0200, Jens Thoms Toerring wrote:
> > Long term what I think would be best would be to get File::FcntlLock
> > into the perl core distribution, preferably upstream, but I'm not sure
> > how such proposals are handled there and if something like that would
> > be
Hi,
> Long term what I think would be best would be to get File::FcntlLock
> into the perl core distribution, preferably upstream, but I'm not sure
> how such proposals are handled there and if something like that would
> be feasible, Jens what do you think? And/or would that be possible in
> Debi
22 matches
Mail list logo
