Wow, I didn't think anyone was following that close on rPi. The reason it broke was because we pushed a new feature to luvit that required a new version of luvi-binaries. I didn't wait till the rPi build had finished since it takes so much longer.
Now that I know someone follows closely on raspi, I'll wait for all builds before pushing changes to luvit. Btw, the build finished a while ago, you can manually update luvi-builds in the lit submodule. -----Original Message----- From: "Jay Vaughan" <[email protected]> Sent: 2/15/2015 4:50 AM To: "[email protected]" <[email protected]> Subject: Building on rPi broke .. On my "luvit pi", a raspberry Pi running Debian GNU/Linux 7.8 (wheezy): * 03b8766 2015-02-13 | Merge pull request #608 from luvit/string_extension (HEAD, origin/luvi-up, origin/HEAD, luvi-up) [Ryan Phillip $ make test LUVI_APP=app ./luvit tests/run.lua [string "bundle:modules/process.lua"]:105: attempt to call field 'getpid' (a nil value) Makefile:18: recipe for target 'test' failed make: *** [test] Error 255 * 0d901cf 2015-02-13 | Update lit and luvi versions (HEAD) [Tim Caswell] $ make test (SUCCESS) On Ubuntu 14.04LTS, (SUCCESS) for both states. So something broke rPi compatability in between 0d901cf and 03b8766 .. in case anyone cares. I'm going to stick to using the rPi as my "luvit pi", so I'll always be running the tests on it as things progress, in case its of use .. -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "luvit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
