Re: Package requiring a customised version of another package
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Justin Pryzby wrote:
[...]
>> I have an application I'd like to package --- plasticfs. Unfortunately, due to
>> glibc weirdnesses, it needs a copy of glibc built using custom (non-standard)
>> options. Is this doable, or is it likely to be a lost cause?
> Please can you give the details of why this is necessary?
It's an LD_PRELOAD hack. When glibc calls itself --- for example when fopen()
calls open() --- it does so using a hidden private interface, which means the
preloader library doesn't get a chance to override it. plasticfs wants a glibc
compiled with --disable-hidden-plt to expose this interface.
Or so the plasticfs docs say --- I'm sure this can be worked around, since
fakeroot and fakechroot manage it, but I wouldn't know how to do that. Also,
I'm working on the assumption that upstream at least know something about what
they're talking about...
- --
┌── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─── http://www.cowlark.com ───────────────────
│
│ "There does not now, nor will there ever, exist a programming language in
│ which it is the least bit hard to write bad programs." --- Flon's Axiom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGzfuLf9E0noFvlzgRAiq/AJ0XJAopwbtk0Kmw+0FKfht8NL1YZgCgkT2b
9PsElxgRWVm+0ccZbf+WpEg=
=O/mh
-----END PGP SIGNATURE-----
Reply to: