hi,
I've got this "not enough memory" twice today while trying to upgrade
some packages using zef.
Once when I ran 'zef upgrade zef' and then again when I ran
'zef --debug upgrade Bailador'.
In both cases the error was shown during the running of the tests.
After running the first command again
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131673]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131673 >
Works as expected:
23:03 m: sub ($x is rw) {}(42)
camelia rakudo
this was caused by instructions coming back from the dead, haunting usage
counts by mysteriously dropping them by 1 or more, and then both the dead
instruction and the lawful citizens of other blocks of code being executed by
the local authorities.
fixed with https://github.com/MoarVM/MoarVM/co
this was caused by instructions coming back from the dead, haunting usage
counts by mysteriously dropping them by 1 or more, and then both the dead
instruction and the lawful citizens of other blocks of code being executed by
the local authorities.
fixed with https://github.com/MoarVM/MoarVM/co
the problem here is that we have a flag to ensure gcc explodes at us
when we write code on linux that'd immediately explode on windows due to
MSVC being somewhat archaic, but that flag is also set for third-party
code, and since the arm dyncall stuff only gets tested once every few
months at best,
the problem here is that we have a flag to ensure gcc explodes at us
when we write code on linux that'd immediately explode on windows due to
MSVC being somewhat archaic, but that flag is also set for third-party
code, and since the arm dyncall stuff only gets tested once every few
months at best,
On Mon, 26 Jun 2017 04:45:38 -0700, frank576frank...@gmail.com wrote:
> rakudobrew build perl6 fail
>
> platform :
> Orange Pi PC (H3 Quad-core Cortex-A7 H.265/HEVC 4K)
> DISTRIB_ID=Ubuntu 15.04 vivid
>
> https://gist.github.com/freakcoco/7d4b7f634288b9534fd926d9f0316e9c
Hi,
Did you ever succes
On Mon, 26 Jun 2017 04:45:38 -0700, frank576frank...@gmail.com wrote:
> rakudobrew build perl6 fail
>
> platform :
> Orange Pi PC (H3 Quad-core Cortex-A7 H.265/HEVC 4K)
> DISTRIB_ID=Ubuntu 15.04 vivid
>
> https://gist.github.com/freakcoco/7d4b7f634288b9534fd926d9f0316e9c
Hi,
Did you ever succes
# New Ticket Created by Will Coleda
# Please include the string: [perl #131670]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131670 >
There are a class of warnings that do not emit their warnings on
$*ERR, but always on the
> On 28 Jun 2017, at 14:01, Martin Barth wrote:
> but your approach means you have to state the version in the META6.json AND
> in the Module.pm6 file again. This would be the similar to having $VERSION in
> perl5. Shouldnt there be a simpler way?
Isn’t that info available in %?RESOURCES somewh
See I'm using mi6 to generate my META6.json file from the report and it
picks the version up from the module file. Other options like that seem
sensible to me.
Simon
On Wed, 28 Jun 2017, 13:01 Martin Barth, wrote:
> Hello,
>
> but your approach means you have to state the version in the META6.j
Hello,
but your approach means you have to state the version in the META6.json
AND in the Module.pm6 file again. This would be the similar to having
$VERSION in perl5. Shouldnt there be a simpler way?
Am 28.06.2017 um 08:45 schrieb Fernando Santagata:
Hi Martin,
This works for me:
File m
12 matches
Mail list logo
