Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

I was trying to investigate what it would take to build e2fsdroid from
the e2fsprgs sources (since there has been some demand to ship e2fsdriod
as a separate Android package) and ione of the problems that I ran into
was that the linker could not find libcutils.so because it was in
/usr/lib/x86_64-linux-gnu/android/libcutils.so, and there is no way for
the linker to find the link library when -lcutils is specified.

I can work around the problem via:

% sudo ln -s android/libcutils.so /usr/lib/x86_64-linux-gnu

But (a) that won't work on a debian build machine, and (b) obviously
it needs to be different on different architectures.  (The resulting
executable also won't find the library without my manually specifying an
rpath or hacking LD_LIBRARY_PATH, but I can deal with that somehow.)

(There is another issue which is that e2fsdroid needs the private header
files from libcutils's source package, but I have an inquiry with some
folks in the Android team about what's the right way to handle this.)