Am 30.08.2011 04:48, schrieb Al Viro:

On Tue, Aug 30, 2011 at 01:23:31AM +0100, Al Viro wrote:

quoted

On Tue, Aug 30, 2011 at 12:25:25AM +0200, Richard Weinberger wrote:

quoted

I'm building most of the time static.
Using defconfig and
CONFIG_STATIC_LINK=y
it builds fine here (x86_64 and i386)

32bit build works, 64bit one breaks with

/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/libc.a(strrchr.o): In function `rindex':
(.text+0x0): multiple definition of `strrchr'

on squeeze/amd64 with stock toolchain and libc (2.11.2-10).  .config, if
you care, is as below, but I really suspect that most of that is irrelevant.

As the matter of fact, on the same build system defconfig + STATIC_LINK +
UML_NET_VDE is enough to reproduce it.

Toolchain:
	libc6		2.11.2-10
	vde2		2.2.3-3
	gcc		4.4.5-8
	binutils	2.20.1-16

all from stock stable/amd64.  Note that debian has the original of that
patch in their user-mode-linux package; see http://bugs.debian.org/494995
for history.

defconfig + STATIC_LINK +  UML_NET_VDE builds fine for me.

Toolchain (openSUSE 11.4):
glibc: 2.11.3
vde2: 2.3.1
gcc: 4.5.3
binutils: 2.21.1

Is my vde too new?
BTW: Why is only strstr affected, what makes it so special?

Thanks,
//richard