lkml.org 
[lkml]   [1998]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: chown(2) vs lchown(2) and application breakage
From
Date
Jamie Lokier <lkd@tantalophile.demon.co.uk> writes:

|> 7. More symbol versioning is used so that an application calling
|> `lchown' in the newer libc can run with an older libc, with
|> the behaviour specified in points 1 and 2. This is optional,
|> it is only needed if we want to support downgrading libc version.
|> It could make the view in the debugger confusing.

This is impossible with symbol versioning. Older libc's won't have an
lchown entry point, and the dynamic linker cannot change the name of the
reference at runtime. Upward compatibility of libc isn't needed in
general anyway.

--
Andreas Schwab "And now for something
schwab@issan.informatik.uni-dortmund.de completely different"
schwab@gnu.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.579 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site