On 1 November 2013 08:26, Glenn Fowler <[email protected]> wrote: > thanks for reporting back > > dgk has a brand new ubuntu installation that is having runtime symbol > clashes > the known one is standalone libcmd grep referencing the ast error() but > getting bound to the glibc error() > its as if the runtime resolves glibc symbols before libast symbols > assuming it *can't really be doing that* its a mystery why it seems that way
The Linux runtime linker is different from the Unix runtime linker. If two libraries have the same symbol name the Linux runtime linker will first search all loaded libraries for a symbol in the order in which they were loaded. If libc was loaded before libcmd the symbols will override anything with the same symbol name coming from libcmd. Use the maplibc ast build option to avoid this. Or use a real Unix with ELF conforming symbol lookup. Ced -- Cedric Blancher <[email protected]> Institute Pasteur _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
