| === doko_ is now known as doko | |
| === chihchun is now known as chihchun_afk | |
| === chihchun_afk is now known as chihchun | |
| [18:58] <q3k> Hm. Is there any particular reason why ARM Ubuntu packages come without static libraries? | |
| [18:59] <q3k> I need to link statically against libdevmapper and libudev from Go, and it's ruining my day :< | |
| [20:00] <infinity> q3k: So don't link statically (or, y'know, use Go). | |
| [20:00] <q3k> That's not really solving my problem :P | |
| [20:01] <q3k> I can link Go dynamically but it's all shitty and seems to crush in weird places (ugh Go) | |
| [20:01] <q3k> But I can't really escape that codebase. | |
| [20:02] <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. | |
| [20:03] <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 | |
| [20:03] <q3k> and it's weird, because all these packages seem to have .a's in amd64 | |
| [20:04] <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? | |
| [20:06] <infinity> q3k: Err, no. It doesn't have a .a on either arch. | |
| [20:07] <infinity> q3k: There should be no discrepancy, where do you see one? | |
| [20:07] <infinity> q3k: libudev-dev and libdevmapper-dev on amd64 sure don't have static libs in them. | |
| [20:07] <q3k> oh, right | |
| [20:07] <q3k> not on trusty | |
| [20:08] <q3k> only on precise | |
| [20:08] <q3k> well, fuck me | |
| [20:08] <q3k> my bad ,_, | |
| [20:08] <q3k> http://packages.ubuntu.com/trusty/amd64/libudev-dev/filelist | |
| [20:08] <q3k> vs | |
| [20:08] <q3k> http://packages.ubuntu.com/precise/amd64/libudev-dev/filelist | |
| [20:09] <q3k> sorry about this, let me take this to somewhere else than -arm then. | |
| === chihchun is now known as chihchun_afk | |