Bug 107978 – mplayer: fails to build with gcc-4.0.1

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Stefaan De Roeck (RETIRED) 2005-10-03 05:11:55 UTC]

mplayer fails to build on AMD64 with gcc-4.0.1

in /var/tmp/portage/mplayer-1.0_pre7-r1/work/MPlayer-1.0pre7try2/libavcodec:

[s]aries libavcodec # make
cc -I../libvo -I../../libvo -I/usr/X11R6/include -O4   -pipe -ffast-math
-fomit-frame-pointer -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib64/glib/include
-DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE
 -c -o libpostproc/postprocess.o libpostproc/postprocess.c
In file included from libpostproc/postprocess.c:655:
libpostproc/postprocess_template.c: In function 'postProcess_MMX2':
libpostproc/postprocess_template.c:3513: warning: pointer targets in passing
argument 6 of 'blockCopy_MMX2' differ in signedness
libpostproc/postprocess_template.c:3659: warning: pointer targets in passing
argument 6 of 'blockCopy_MMX2' differ in signedness
libpostproc/postprocess_template.c:3760: warning: pointer targets in passing
argument 4 of 'tempNoiseReducer_MMX2' differ in signedness
libpostproc/postprocess_template.c:3784: warning: pointer targets in passing
argument 4 of 'tempNoiseReducer_MMX2' differ in signedness
libpostproc/postprocess_template.c:3484: error: memory input 4 is not directly
addressable
libpostproc/postprocess_template.c:3484: error: memory input 5 is not directly
addressable
libpostproc/postprocess_template.c:3630: error: memory input 4 is not directly
addressable
libpostproc/postprocess_template.c:3630: error: memory input 5 is not directly
addressable
make: *** [libpostproc/postprocess.o] Error 1

Using gcc-3.4.4 to compile the same file does work.

Portage 2.0.53_rc3 (default-linux/amd64/2005.1, gcc-4.0.1, glibc-2.3.5-r1,
2.6.13-1.1526_FC4smp x86_64)
=================================================================
System uname: 2.6.13-1.1526_FC4smp x86_64 AMD Opteron(tm) Processor 250
Gentoo Base System version 1.12.0_pre8
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.13
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=opteron"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /var/bind
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe -march=opteron"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig collision-protect distlocks sandbox sfperms strict userpriv
usersandbox"
GENTOO_MIRRORS="ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/ownportage"
SYNC="rsync://ftp.belnet.be/gentoo-portage"
USE="amd64 X alsa avi berkdb bitmap-fonts crypt cups curl eds emboss encode esd
fam foomaticdb fortran gif gnome gpm gstreamer gtk gtk2 imagemagick imlib ipv6
java jpeg kde lzw lzw-tiff mad motif mozilla mp3 mpeg ncurses nls ogg opengl pam
pdflib perl png python qt quicktime readline sdl spell ssl tcpd tiff
truetype-fonts type1-fonts usb userlocales vorbis xml2 xpm xv zlib userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

[Comment 1 SpanKY 2005-10-03 06:31:09 UTC]

chances are they're using inline asm that gets a deprecated warning with
gcc-3.4.4, but people ignore it because it doesnt abort :P

find a fix from upstream

[Comment 2 Mark Loeser (RETIRED) 2005-10-03 12:23:48 UTC]

Created attachment 69805 [details, diff]
Upstream amd64 fixes

Here's the fixes I found upstream that seem to fix the build problems.

[Comment 3 Reimar Döffinger 2005-10-04 01:58:20 UTC]

Make sure you double and triple check these kind of patches. There was one 
version that caused gcc 3.3 to emit wrong code.

[Comment 4 Luca Barbato 2005-10-10 06:00:17 UTC]

It should be a backport from the cvs, committed after a brief test.