Re: Multiple definition of __memcpy_chk

[Mike Frysinger <vapier at gentoo dot org>]

On Friday, August 19, 2011 12:34:08 Bryan Ischo wrote:
> I think I was confused between the linking of gcc itself and the linking
> of programs generated by that gcc.  I had assumed that gcc used its ssp
> as another library that it automatically links into programs, like it
> does for libgcc, and given that I didn't understand how gcc could do
> that if it was linking programs that linked against glibc with the
> duplicate symbols.

that is how gcc uses libssp.  if you enable libssp support, gcc will 
automatically add its libssp to the link line when it is invoked to link 
programs, and you're using the respective stack protector flags.

> Your terse and almost completely uninformative
> answer did at least lead me to the line of thinking which in which I
> believe I came to the correct conclusion, which is: disable ssp if
> you're linking gcc against glibc, otherwise enable it.

there is one or two other C libs out there that dont need libssp, but 
certainly this line of reasoning is correct for glibc targets.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.