Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
Set by moderator on 5 September 2017.
jdv79 m: 1+1 01:36
camelia WARNINGS for <tmp>:?Useless use of "+" in expression "1+1" in sink context (line 1)?
01:52 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
04:00 llfourn joined 05:30 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
05:52 domidumont joined 05:59 domidumont joined 06:01 leont joined 06:43 lizmat_ joined 07:24 lizmat joined 08:50 lizmat joined 09:37 lizmat joined 09:38 lizmat_ joined 09:40 lizmat__ joined 09:43 lizmat joined 11:03 stmuk_ joined 12:50 perlpilot joined 14:24 llfourn joined 14:43 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
14:49 ilbot3 joined
moderator Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec
18:18 leont joined
ugexe nine: is there a best way to handle the need to quote full paths in the rakudo/nqp/moarvm makefiles? cant just PREFIX="blah", because then "$(PREFIX)/foo" is ""blah"/foo". i simply quoted everything when it was used, but noticed that $(DESTDIR)/$(PREFIX) would be incorrect on windows. To fix DESTDIR we can just default it to the previous volume of PREFIX (which then defaults to 21:12
.dirname.child(.basename)). but i figured maybe its better to generate these values inside the build tools?
i was doing this in an attempt to get rakudo to build on windows when the user has a space in the name (or the path to perl). while i got the changes to the build tools working, precomp does not (Proc::Async or the perl6-m.bat on windows splits the first argument on a space if any of the other arguments contain a space or quotes) 21:16
although i have to wonder if the spaces thing isn't just windows
nine Sounds like a couple of issues? My experience is that it's better to generate paths in build tools rather than in a Makefile. 21:28
Seems like on Linux paths with spaces are fine for precomp
ugexe the path to perl6 has spaces in it? 21:29
im not sure the build tools can build rakudo is they are installing to a location with a space. but particularly if the path to perl(5) has a space 21:30
21:43 lizmat joined
[Coke] pretty sure rakudo isn't space-in-path-clean; I did some work on that, I think mst did... but pretty sure there's still open tickets for it on rt 22:16
RT #76930