Re: dlopen(3) and symbol conflicts

[Emmanuel Dreyfus <manu%netbsd.org@localhost>]

On Fri, Mar 20, 2015 at 01:52:46PM +0100, Edgar Fuß wrote:
> But any third-party program or library should be able to choose whichever 
> symbol names it likes to choose (unless reserved by an official standard) 
> without risking to interfere with the system C library, shouldn't it? What 
> point would you make if Linux/GNU would pollute your favourite namespace 
> with symbols from some ``XYZ interface present in Linux, Irix and Windows 
> at least''?

Agreed. Morover, it is disturbing that it works fine in a program linked 
with -lglusterfs but not in a program that dlopen() an object linked with
-lglusterfs.

-- 
Emmanuel Dreyfus
manu%netbsd.org@localhost