Re: conflict between gcc and bash malloc lib with static link

[Mike Frysinger]

On 08 Apr 2015 09:40, Chet Ramey wrote:
> I suspect the problem with malloc is that there are one or more additional
> symbols in the file (malloc.o) that glibc uses to satisfy some internal
> reference, which causes the rest of the symbols from malloc.o to be
> loaded, which causes conflicts with the already-loaded bash malloc library.

glibc tries pretty hard to avoid symbol conflicts even when static linking.
if you're aware of such conflicts, please let us know.  there should be no
leaking of plain symbols like "foo" or "xmalloc" even w/static libs.
-mike

signature.asc
Description: Digital signature