Bug 371711 - tre compilation fails on ix86 due to memmove redefinition in glibc-headers
tre compilation fails on ix86 due to memmove redefinition in glibc-headers
Product: Fedora
Classification: Fedora
Component: glibc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
Depends On:
Blocks: 355241
  Show dependency treegraph
Reported: 2007-11-08 14:24 EST by Dominik 'Rathann' Mierzejewski
Modified: 2007-12-17 08:11 EST (History)
0 users

See Also:
Fixed In Version: 2.7.90-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-17 08:11:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dominik 'Rathann' Mierzejewski 2007-11-08 14:24:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20071019 Fedora/ Firefox/

Description of problem:
tre-0.7.5 fails to build on i386 (tested in koji as above and locally in mock). It builds fine on x86_64.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Try building tre on i386

Actual Results:
gcc -DHAVE_CONFIG_H -I. -I.. -I../gnulib/lib -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -MT tre-match-approx.lo -MD -MP -MF .deps/tre-match-approx.Tpo -c tre-match-approx.c  -fPIC -DPIC -o .libs/tre-match-approx.o
In file included from /usr/include/string.h:428,
                 from tre-match-approx.c:48:
/usr/include/bits/string3.h:58: error: redefinition of 'memmove'
make[3]: *** [tre-match-approx.lo] Error 1
make[3]: Leaving directory `/builddir/build/BUILD/tre-0.7.5/lib'

Expected Results:
It should compile successfully, like on x86_64.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.