Bug#327016: Any insights on this GLIBC_PRIVATE issue ?
reassign 327016 bigloo
thanks
On Sat, Sep 24, 2005 at 03:45:44PM +0200, Yann Dirson wrote:
> Does anyone has a precise idea of the reason for such mismatches ? It
> would look like the 1st step towards getting rid of them once and for
> all.
>
> It looks like such an issue would get in the way of the possiblity to
> mix-and-match packages from various sources, which would indeed be bad
> news...
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.
--
Daniel Jacobowitz
CodeSourcery, LLC
Reply to: