[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: authbind (LD_PRELOAD) and multiarch

Osamu Aoki wrote:

> Also, for such input method plugins, we have a hook and configuration script
> "im-config" to initialize such input method environment while starting X.

Could you spell this out more?  What environment variables will
im-config set that include architecture names?  Which architecture
should they name --- the architecture of the /usr/bin/X binary?

> To update im-config for multiarch, I would like to have access to following
> commands without depending on the dpkg-dev package since user program depending
> on -dev package is weired:
> * current-library-path
>   equivalent of
>   $ dpkg-architecture|sed -n 's/^DEB_HOST_MULTIARCH=\(.*\)/\1/p'

When building a new program, "gcc -print-multiarch" seems to be the
usual way.

> * installed-library-path
>   list all library-path
>   I do not know how to get this reliably

ld.so does not expose that information.  However, you can search for a
library used by a binary on the library path with "ldd".

> On Thu, Dec 22, 2011 at 08:01:24PM +0100, Goswin von Brederlow wrote:

>> This is something that could use some native english speaker to write a
>> proposal/specs for with some examples where it is needed. Any takers?
> Yes.
> (I guess since we are talking spec, there is no tools such as apt-get nor
> aptitude to manage such dependencies.)

While the kind of interfaces you are talking about would be welcome, I
don't think they are what Ian and Goswin were looking for.  I think they
wanted a way to tell the packaging system "This package (fakeroot)
depends on this library (libfakeroot) from all enabled architectures",
or "This package (something-input-method-related) depends on this
library (some-input-method-plugin) from the same architecture as this
other package (some-daemon-that-will-dlopen-it)".

Hope that helps,

Reply to: