Bugzilla Bug 165682

media-libs/xvid-1.1.2 wants an executable stack. This is happening since the
patch was updated to xvid-1.1.2-noexec-stack.patch.bz2, the patch before it was
working fine for me.

Portage 2.1.2-r8 (selinux/2005.1/x86/hardened, gcc-3.4.6, glibc-2.3.6-r5,
2.6.19-hardened-r5 i686)
=================================================================
System uname: 2.6.19-hardened-r5 i686 Intel(R) Pentium(R) 4 CPU 1.60GHz
Gentoo Base System release 1.12.9
Timestamp of tree: Tue, 06 Feb 2007 17:50:01 +0000
dev-java/java-config: 1.3.7, 2.0.31-r3
dev-lang/python:     2.4.4
dev-python/pycrypto: 2.0.1-r5
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.4_p6, 1.7.9-r1, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.14
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.20
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=pentium4 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-O2 -pipe -march=pentium4 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--alphabetical"
FEATURES="autoconfig collision-protect distlocks loadpolicy parallel-fetch
sandbox selinux sesandbox sfperms strict userfetch userpriv usersandbox"
GENTOO_MIRRORS="ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo
ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/"
LANG="de_DE.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common"
LINGUAS="de"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from /etc/portage/rsync_excludes"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X a52 aac alsa bzip2 cairo caps cjk crypt cups dts dvd dvdread ffmpeg ftp
gif hardened iconv idn ipv6 jpeg kdeenablefinal mmap mmx mp3 nls nptl offensive
ogg pam pic png selinux sse sse2 ssl symlink theora threads truetype unicode
vorbis win32codecs x86 xv xvid zlib" ALSA_CARDS="ens1371"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file
hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route
share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses
text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="nvidia"
Unset:  CTARGET, INSTALL_MASK, LC_ALL

Created an attachment (id=109380) [edit]
scanelf-execstack.log

Do you have yasm or only nasm installed ? 

I've got nasm-0.98.39-r3 over here.

@vapier: what do you think, should I revert your changes and patch the build
system to use only nasm on x86 ? Is there a better way to solve that without
getting again in bug #159498 ?

Note that I'll have to force using nasm on x86 because of the patch in bug
#135326

xvid-1.1.2 forces yasm rather than allowing nasm

once next version of yasm comes out, we can revisit this