Re: [perl #130339] make install failure on rakudo star 2016.11
On Wed, Dec 14, 2016 at 8:39 AM, mark carter wrote: > The perl 5 script "prove" was not found. Adding (for me, anyway) > > /usr/bin/core_perl > ...so Red Hat decided too many people had figured out how they broke Perl, and broke it even more to compensate? -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
[perl #130339] make install failure on rakudo star 2016.11
# New Ticket Created by mark carter # Please include the string: [perl #130339] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130339 > $perl6 --version This is Rakudo version 2016.11 built on MoarVM version 2016.11 implementing Perl 6.c. make install seems to have problems building panda. It is reliant on File::Find, which is failing a test: Unhandled exception: Failed to write to filehandle: NULL string given http://pastebin.com/7PzmcaTS
[perl #130339] make install failure on rakudo star 2016.11
I think I found the cause. The perl 5 script "prove" was not found. Adding (for me, anyway) /usr/bin/core_perl to PATH fixed the issue (as far as I can tell).
Re: [perl #130339] make install failure on rakudo star 2016.11
I think I found the cause. The perl 5 script "prove" was not found. Adding (for me, anyway) /usr/bin/core_perl to PATH fixed the issue (as far as I can tell).
Re: [perl #130339] AutoReply: make install failure on rakudo star 2016.11
I think I found the cause. The perl 5 script "prove" was not found. Adding (for me, anyway) /usr/bin/core_perl to PATH fixed the issue (as far as I can tell).
[perl #129838] [LTA] Too-short indent in HEREDOCs produces gut-referencing error
On Sun, 09 Oct 2016 19:14:30 -0700, biod...@gmail.com wrote: > Hi guys, > > Friends on IRC kindly asked me to submit this error report: > > Asked to remove 2 spaces, but the shortest indent is 0 spaces in any > descend at gen/moar/m-Perl6-Actions.nqp line 473 > Asked to remove 2 spaces, but the shortest indent is 0 spaces in any > descend at gen/moar/m-Perl6-Actions.nqp line 468 > Use of uninitialized value $conditions of type Any in string context > Any of .^name, .perl, .gist, or .say can stringify undefined things, if > needed. in sub MAIN at create-table.pl line 29 > Use of uninitialized value $hash-values of type Any in string context > > > tx Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/commit/7345e08c9b Test: https://github.com/perl6/roast/commit/171d5c6fa9
[perl #129763] [RTESTNEEDED] error when attempting to modify return value within phaser
Test added: https://github.com/rakudo/rakudo/commit/e327f3049a
[perl #130034] A andthen B orelse C leaks some internal Block
On Sun, 06 Nov 2016 20:25:50 -0800, lloyd.fo...@gmail.com wrote:
> 15:18 < llfourn_> m: say (Str andthen .uc orelse "foo") # more golfed
> 15:18 <+camelia> rakudo-moar 1c425f: OUTPUT«-> ;; $_ is raw {
> #`(Block|81391040) ... }»
> 15:23 < llfourn_> m: say (Str andthen .uc orelse "foo")("wee")
> 15:23 <+camelia> rakudo-moar 1c425f: OUTPUT«foo»
>
> unless I totally missed what these are meant to do a Block is not what
> should be returned from this expression.
Thank you for the report. This is now fixed.
Fix: https://github.com/rakudo/rakudo/commit/287af6a37e00ad
Test: https://github.com/perl6/roast/commit/8d6a6397e7
Re: perl 6 on EPEL is getting close!
On 12/10/2016 11:19 AM, ToddAndMargo wrote: EPEL = Extra packages for Enterprise Linux https://bugzilla.redhat.com/show_bug.cgi?id=1297077 --- Comment #8 from Fedora Update System --- rakudo-star-0.0.2016.11-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5483f2f1e9 -- Comment #9 from Fedora Update System --- moarvm-0.2016.11-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-a8d78e928d --- Comment #10 from Fedora Update System --- nqp-0.0.2016.11-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-09ef50a884 Yippee! And version 11 too!!! -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ Fedora Core 25 is keeping pace too: :-) [Bug 1397232] rakudo-star is out of date https://bugzilla.redhat.com/show_bug.cgi?id=1397232 --- Comment #2 from Fedora Update System --- rakudo-star-0.0.2016.11-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5bcfb4f3fc -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~
[perl #129763] [LTA] error when attempting to modify return value within phaser
On Thu, 29 Sep 2016 11:01:49 -0700, ajs wrote:
> Via IRC:
>
> [13:51] a very slightly LTA error:
> [13:51] m: sub test { return (state $x = 0 )++; POST { $_++ }
> }; say test
> [13:51] <+camelia> rakudo-moar 58cf9d: OUTPUT«Cannot resolve caller
> postfix:<++>(Int); none of these signatures match:(Mu:D $a is rw)
> (Mu:U $a is rw)(Int:D $a is rw)(int $a is rw)(Bool:U $a is
> rw)(Bool:D $a is rw)(Num:D $a is rw)(Num:U $a is rw)…»
> [13:52] It really would be nice if the error simply told me
> that I was trying to modify a non-read-only rather than making me visually
> parse the "is rw" on all of those.
> [13:52] Should I rakudobug that?
> [13:55] harmil_wk: sure, why not -- though I'm not sure the verdict
> will be "we can haz nice error" on that :/
>
> --
> Aaron Sherman, M.:
> P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com
> Toolsmith, developer, gamer and life-long student.
This has been addressed (as part of another ticket ticket, or perhaps it was
you on IRC who caused me to fix this). The new error is more A:
Cannot resolve caller postfix:<++>(Int); the following candidates
match the type but require mutable arguments:
(Mu:D $a is rw)
(Int:D $a is rw)
The following do not match for other reasons:
(Bool:D $a is rw)
(Bool:U $a is rw)
(Mu:U $a is rw)
(Num:D $a is rw)
(Num:U $a is rw)
(int $a is rw)
(num $a is rw --> num)
in sub test at -e line 1
in block at -e line 1
Marking as tests needed (which I think should go to into rakudo's t/, since
they'd be checking raw content of an output message).
[perl #130330] Whatever on the left side of array subscript range may cause hangs (@a[*-2..*]:exists)
On Tue, 13 Dec 2016 11:10:38 -0800, alex.jakime...@gmail.com wrote: > Sooo… Are you saying that the behavior in provided examples is consistent? > As far as I can see, yes. The first two are lazy Ranges. The second two are non-lazy WhateverCodes. And as jnthn++ pointed out "The array subscripter decides whether to auto-viv for not based on .is-lazy". The reason it does so is so things like `my @a; @a[3..5] = 1 xx *; say @a` autovivicate, while still letting you do stuff like `@a[2..*]` to get a truncated result. In the example you point out as problematic, you're exploiting the autovivication feature to create an infinite loop, hence the hang. Is there still an issue on this ticket not covered by those explanations?
[perl #127224] [BUG] Itemized slip has invalid .perl stringification
On Sat, 09 Jan 2016 05:37:07 -0800, lucasbuchala wrote: > The ".perl"-stringification of an itemized slip has a strange dollar > sign in the middle: > > > say slip(1,2).item.perl > slip$(1, 2) > > Lists come in itemized and non-itemized flavours; and Slips are Lists, > but I'm not certain that the itemization concept also applies to > slips. Either way, slip's ".perl"-stringification should not have a > dollar sign in the middle, so removing that "$" would fix the problem. > If it's really intended to have an itemized slip, then maybe stringify > it as "$(slip(...))" or "slip(...).item". Thank you for the report. This is now fixed. Fix: https://github.com/rakudo/rakudo/commit/8eef234a5b441a Test: https://github.com/perl6/roast/commit/7eea834e98
Re: [perl #130338] perl6 changes breaking code
Hi, I've rebuild rakudo from the ground up. Version I get now is 2016.11-236-g7b09bee built on MoarVM version 2016.11-41-gd2139b5 which looks better now. However, problem still exist. Can do for now with the unit package line before all use statements.
Re: [perl #130338] perl6 changes breaking code
Hi, How did you build your Perl 6? That version number looks suspicious. You say you're on 2016.11-238-g2f502b4, but the current HEAD/nom is 2016.11-226-g1d46004, 12 commits fewer than yours. The most obvious answer is you're in possession of a time machine and are reporting bugs from the future. In which case, would you mind including this week's lottery numbers in your reply? Let us know, Thank you. Hi, Well, it is one of those undocumented features of perl 6 :-) About the lottery: 42 42 42 42 42 42 42 ... What I do is pulling rakudo directly from the repo like I did this morning(11:05 CET); > git pull remote: Counting objects: 159, done. remote: Compressing objects: 100% (21/21), done. remote: Total 159 (delta 110), reused 102 (delta 102), pack-reused 35 Receiving objects: 100% (159/159), 47.58 KiB | 0 bytes/s, done. Resolving deltas: 100% (113/113), completed with 32 local objects. From git://github.com/rakudo/rakudo 5d6a8e9..7b09bee nom-> origin/nom ... Then > perl Configure.pl --gen-moar --backends=moar > make test > make install After the installation > perl6 -v This is Rakudo version 2016.11-271-g416e83b built on MoarVM version 2016.11-41-gd2139b5 What about this version? is it better? 40 commits further than 238. (maybe its a pull count instead of commit count ;-) Thanks for all of your work everyone (I must say it somewhere someplace) Marcel
