Hi, from #debian-qa this morning:
<h01ger> | #766921 - anybody have an idea why adding gcc to the chroot helps? <ntyni> | h01ger: looks like eatmydata calls dpkg-architecture which calls gcc <h01ger> | ah! <h01ger> | so the options are really just disabling eatmydata or adding gcc? <mapreri> | h01ger: you can install libeatmydata1 and LD_PRELOAD=libeatmydata.so instead of using the the eatmydata helper script <h01ger> | thanks <mapreri> (not sure of how you use eatmydata, but the eatmydata package is actually useless, the actual library is in libeatmydata1) <mapreri> | h01ger: this will fixed by 105, but only on sid for jessie+1 (as a part of #765810) <zwiebelbot> | (#debian-qa) Debian#765810: the eatmydata binary should work with different arches transparently - https://bugs.debian.org/765810 * h01ger ponders removing / disabling eatmydata then for now <h01ger> | adding gcc everywhere doesnt seem like a good idea to me <mapreri> | h01ger: just replace "eatmydata" by LD_PRELOAD="${LD_PRELOAD: +$LD_PRELOAD:}libeatmydata.so" and install libeatmydata1 instead of eatmydata. should work fine. * h01ger doubts that this is the right syntax for python :) <mapreri> ouch <h01ger> | mapreri: thanks. i will dump this in the bug report for now and then see what i'll do. this week nothing for sure <mapreri> | h01ger: well, is there a pythonic way to preload library? :) cheers, Holger
signature.asc
Description: This is a digitally signed message part.
