Le 12/04/2012 13:50, Junichi Uekawa a écrit : > Yeah, that's expected in the current design. > > What's the multiarch-way of LD_PRELOADing ?
A simple thing to do (and that would be enough for me) would be to put libcowdancer.so in a Multiarch:same package (so, basically, put it in an architecture-dependent path), not put the absolute path in LD_PRELOAD but instead extend LD_LIBRARY_PATH with the location of libcowdancer.so. This assumes that whatever state is used by the LD_PRELOADed library is compatible across architectures... I don't necessarily expect LD_LIBRARY_PATH to contain all possible paths, but it sounds reasonnable (if nothing better is found) to expect the user to install libcowdancer:$foreign_arch and extend LD_LIBRARY_PATH as needed before using foreign executables. See also the thread at [1]. [1] https://lists.debian.org/debian-devel/2011/12/msg00592.html Cheers, -- Stéphane -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
