Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-06-15

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:03 stevieb9 joined #perl6-toolchain
00:51 b2gills joined #perl6-toolchain
01:49 ilbot3 joined #perl6-toolchain
01:49 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
03:51 jrusso joined #perl6-toolchain
06:15 domidumont joined #perl6-toolchain
06:20 domidumont joined #perl6-toolchain
09:33 lizmat joined #perl6-toolchain
09:55 M-tadzik joined #perl6-toolchain
09:59 lizmat joined #perl6-toolchain
10:37 tadzik joined #perl6-toolchain
11:47 domidumont Hi, why is dyncall source embedded in nqp sources ? As far as I know, dyncall is used only to build moar.
11:57 [Coke] domidumont: where do you see it embedded in nqp?
11:58 domidumont in 3rdparty directory
11:59 domidumont https://github.com/perl6/nqp/tree/master/3rdparty/dyncall
11:59 nine Maybe for nqp-j?
11:59 nine nqp-m seems to build fine without 3rdparty/dyncall
12:00 domidumont got it: Configure.PL uses dyncall with parrot backend
12:03 domidumont although Parrot's Configure.PL does not mention dyncall...
12:05 domidumont ok, since I don't plan to build rakudo with parrot for Debian, I'll try to remove 3rdparty directory from nqp source before building the next version...
12:09 nine domidumont: sounds sensible
12:09 nine domidumont: I'm curious: have you been following the work on making precomp files packageable?
12:10 domidumont No... Sorry, Looks like I missed this
12:11 domidumont Currently, I'm trimming down perl6 main package (moar, nqp and rakudo). I've setup moar to use libuv shipped by Debian instead of the embedded copy.
12:13 domidumont I may do the same with dyncall (OTOH, if only moar uses dyncall in Debian, there's no much advantages besides reducing the load on our build systems)
12:13 domidumont nine: do your have links that I can read for this work on precomp files ?
12:16 [Coke] domidumont: we have custom versions of those libs for a reason
12:17 [Coke] so as long as you're picking a version which has the modifications we've made (hopefully they've been submitted back upstream)
12:17 [Coke] er, as long.... then you're ok.
12:25 nine domidumont: https://github.com/rakudo/rakudo/commit/2801780673f7f5a32f72e0a1d2b9a81e01f7f2e9 should give you a hint
12:29 domidumont [Coke]: Agreed. I use Debian's version of a library when the embedded copy was not modified for quite a while or match an upstream version (e.g. libuv is a submodule of upstream libuv 1.8)
12:31 domidumont I'm more cautious with dyncall since the submodule refers to dyncal repo in moar organisation
12:31 domidumont nine: thanks for the pointer
14:26 mst joined #perl6-toolchain
14:40 mst joined #perl6-toolchain
14:41 mst joined #perl6-toolchain
15:10 stevieb joined #perl6-toolchain
16:46 stevieb joined #perl6-toolchain
16:50 TimToady joined #perl6-toolchain
16:55 domidumont joined #perl6-toolchain
17:04 FROGGS joined #perl6-toolchain
17:21 sjn joined #perl6-toolchain
19:22 domidumont joined #perl6-toolchain
19:29 hankache joined #perl6-toolchain
19:31 sivoais joined #perl6-toolchain
20:37 domidumont joined #perl6-toolchain
21:07 Kassandry joined #perl6-toolchain
22:15 sjn joined #perl6-toolchain
22:21 stevieb9 joined #perl6-toolchain
22:42 stevieb9 joined #perl6-toolchain
23:07 moritz_ joined #perl6-toolchain
23:08 [Coke]_ joined #perl6-toolchain
23:08 jdv79_ joined #perl6-toolchain
23:15 MadcapJake left #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary