On Mon, Sep 26, 2005 at 10:18:21AM -0400, Daniel Jacobowitz wrote:
> You are using a symbol whose name starts with "__libc". You are
> getting an error involving the string "GLIBC_PRIVATE". I'm really not
> sure how to make this any clearer...
>
> It is a private interface. Therefore it is subject to ABI-incompatible
> changes and sudden removal, which indeed has happened; it is no longer
> available. Whatever you're using __libc_stack_end for, don't.
For the background, bigloo ships a slightly modified version of libgc,
which is the one using libc_stack_end.
The fact is, IIRC this "removal" already happenned more than 2 years
ago(see #192039). And at that time, it was told that rebuilding libgc
against the new glibc would solve the problem, since then it will not
find the offending symbol to be available, and therefore would not use
it. And it seemed to work.
But every now and then this problem keeps resurfacing for bigloo,
while the libgc package does not seem to suffer from a similar issue.
Ryan, do you recall has any special treatment for the libgc package
for this issue ? According to the changelog, it seems not.
Best regards,
--
Yann Dirson <[EMAIL PROTECTED]> |
Debian-related: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
