Control: clone -1 -2
control: reassign -2 eatmydata 82-1
control: severity -2 normal
control: retitle -2 the eatmydata binary should work with different
arches transparently

On Sat, Oct 18, 2014 at 12:51 PM, Thorsten Glaser <[email protected]> wrote:
> Mattia Rizzolo dixit:
>
>>It should work just fine provided that
>>1) the target arch is the same as the host
>
> This is something that will, for me, almost never be the case.
[...]
> But to work like that, or in the foreign-arch /bin/bzip2
> example we had earlier in this mail thread, is precisely
> what’s needed in a M-A scenario. We *really* need that to
> work.
>
> Maybe we should involve the glibc people and ask how we
> can do an automatic-architecture LD_PRELOAD.

You're right, cloned this bug where I'll track this (I already have
sketched up an ugly workaround; if you, for some odd reasons, want a
fix right now)

For now, manually set LD_PRELOAD to "libeatmydata.so" works, though.

>>2) the target chroot has the libeatmydata1 package installed
>
> That is something I can easily do (backport it).

I already planned a classic backport to wheezy-backports, once I'm
sure there are no more real big bugs with this new version.

-- 
regards,
Mattia Rizzolo

GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to