**** BEGIN LOGGING AT Mon Oct 20 02:59:59 2014
Oct 20 18:58:47 <q3k> Hm. Is there any particular reason why ARM Ubuntu packages come without static libraries?
Oct 20 18:59:06 <q3k> I need to link statically against libdevmapper and libudev from Go, and it's ruining my day :<
Oct 20 20:00:17 <infinity> q3k: So don't link statically (or, y'know, use Go).
Oct 20 20:00:54 <q3k> That's not really solving my problem :P
Oct 20 20:01:18 <q3k> I can link Go dynamically but it's all shitty and seems to crush in weird places (ugh Go)
Oct 20 20:01:26 <q3k> But I can't really escape that codebase.
Oct 20 20:02:49 <infinity> q3k: So, you could file bugs on both packages to produce and ship the .a, but it's not going to get fixed in the middle of release week.
Oct 20 20:03:20 <q3k> yeah, I already did this for libdevmapper, but I think there's gonna be like 9001 other packages that will also require to be fixed
Oct 20 20:03:29 <q3k> and it's weird, because all these packages seem to have .a's in amd64
Oct 20 20:04:12 <q3k> and this is my real question - why is that? Is that a decision from the package maintianers, or just nobody really gave a crap about static libraries before me?
Oct 20 20:06:57 <infinity> q3k: Err, no.  It doesn't have a .a on either arch.
Oct 20 20:07:12 <infinity> q3k: There should be no discrepancy, where do you see one?
Oct 20 20:07:24 <infinity> q3k: libudev-dev and libdevmapper-dev on amd64 sure don't have static libs in them.
Oct 20 20:07:53 <q3k> oh, right
Oct 20 20:07:56 <q3k> not on trusty
Oct 20 20:08:01 <q3k> only on precise
Oct 20 20:08:02 <q3k> well, fuck me
Oct 20 20:08:10 <q3k> my bad ,_,
Oct 20 20:08:39 <q3k> http://packages.ubuntu.com/trusty/amd64/libudev-dev/filelist
Oct 20 20:08:41 <q3k> vs
Oct 20 20:08:48 <q3k> http://packages.ubuntu.com/precise/amd64/libudev-dev/filelist
Oct 20 20:09:19 <q3k> sorry about this, let me take this to somewhere else than -arm then.
**** ENDING LOGGING AT Tue Oct 21 02:59:59 2014