01:09 <Praetonus> SeanTAllen: fails in a clean environment too. I tried Debian and Archlinux. I'll open an issue

03:24 <SeanTAllen> Praetonus: what version of Debian? what version of Arch? It builds fine in the travis builds. I need more info if I'm going to look into this.

09:07 <sylvanc> Praetonus: works for debug and release on LLVM 3.6.2, 3.7.1 in travis and on my various linux VMs

09:08 <sylvanc> 64 bit wily, 32 bit trusty, 64 bit trusty, etc

09:08 <sylvanc> there is a known problem with a debug build on linux using LLVM 3.8 if you install LLVM from apt due to the apt package having no debug symbols

09:09 <sylvanc> but i can't reproduce your problem with the release build, i'm afraid

11:28 <SeanTAllen> sylvanc: install from apt how?

12:19 <sylvanc> using these sources: http://llvm.org/apt/

12:19 <sylvanc> on ubuntu, but apparently not debian

13:08 <darach> Slightly more convenient than MIPS. So jealous! :)

15:05 <SeanTAllen> yeah. per conversation that wasn't here. i found out llvm 3.8 for debian is built with debug symbols (but for ubuntu, it isnt because ¯\_(ツ)_/¯)

19:06 <mcguire> Well, fine and dandy, then.

19:08 <mcguire> ponyc is passing "-fuse-ld=gold" during linking. ld.gold ignores LD_RUN_PATH. (There's been a bug open since 2012 with a patch: https://sourceware.org/bugzilla/show_bug.cgi?id=13764)

19:25 <mcguire> I opened issue #651 on it. https://github.com/ponylang/ponyc/issues/651

20:19 <TwoNotes> If I have a packages that defines 3 classes, and I only refer to one of them, is the code for the other two still included in my executable?

20:26 <jemc> TwoNotes: off the top of my head, I think the answer is "no" - I think the compiler excludes types from other packages that are "unreachable" from the code in the main package

20:27 <TwoNotes> ok good

20:27 <TwoNotes> I assume that the largish size for even the simplest Pony program is due to the scheduler, GC, etc

20:28 <TwoNotes> Though libponyrt is an .so hmmm

20:28 <shepheb> it is, but isn't it linked in directly?

20:29 <shepheb> otherwise the output binaries would have a runtime dependency on libponyrt being findable, and I don't think that's the case.

20:29 <TwoNotes> That would certainly explain the size, and it makes finished programs standalone, which is nice for deployment

20:29 <TwoNotes> A big advantage over Erlang. The OTP package is huge

20:52 <jemc> I've recently dealt with the process of trying to package up a docker container for an OTP app and attempting to pare it down to only the minimal amount of OTP it needs - it's certainly not for the faint of heart, and at a certain point I stopped short of fully minimal because the time investment was getting to be too much for the savings

20:52 <jemc> being able to deploy a standalone binary that just works is a big headache lifted

20:53 <jemc> even if there might be *some* waste if you have multiple applications that all statically linked the same base (probably the reason OTP went with the shared base approach, with multi-application deployments being the OTP way)

20:54 <jemc> however, if you want to isolate those applications into docker applications as is so common today, you end up with the same "waste"

20:57 <TwoNotes> There is a way to make a big binary from an Erlang app, but it is real complicated.

20:57 <TwoNotes> It sucks the whole BEAM engine into it

20:58 <TwoNotes> And I think you lose the rolling-upgrade feature anyway if you do that