WindowMaker 0.92.0 released. Please provide e-build for it Reproducible: Always Steps to Reproduce: 1. 2. 3.
ebuild committed -- please test
It failes to compile `echo /bin/sh ../libtool --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include -march=k8 -O2 -pipe | sed -e s/-fomit-frame-pointer//` -O0 -c x86_specific.c x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/include -march=k8 -O2 -pipe -O0 -c x86_specific.c -fPIC -DPIC -o .libs/x86_specific.o {standard input}: Assembler messages: {standard input}:25: Error: suffix or operands invalid for `pusha' {standard input}:26: Error: suffix or operands invalid for `pushf' {standard input}:27: Error: suffix or operands invalid for `pop' {standard input}:30: Error: suffix or operands invalid for `push' {standard input}:31: Error: suffix or operands invalid for `popf' {standard input}:32: Error: suffix or operands invalid for `pushf' {standard input}:33: Error: suffix or operands invalid for `pop' {standard input}:42: Error: suffix or operands invalid for `popa' {standard input}:47: Error: suffix or operands invalid for `popa' {standard input}:74: Error: suffix or operands invalid for `pusha' {standard input}:188: Error: suffix or operands invalid for `popa' {standard input}:210: Error: suffix or operands invalid for `pusha' {standard input}:258: Error: suffix or operands invalid for `popa' {standard input}:280: Error: suffix or operands invalid for `pusha' {standard input}:423: Error: suffix or operands invalid for `popa' make[2]: *** [x86_specific.lo] Error 1 make[2]: Leaving directory `/var/tmp/portage/windowmaker-0.92.0/work/WindowMaker-0.92.0/wrlib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/windowmaker-0.92.0/work/WindowMaker-0.92.0/wrlib' make: *** [all-recursive] Error 1 emerge info Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r11 x86_64) ================================================================= System uname: 2.6.11-gentoo-r11 x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.6.12 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 12 2005, 16:22:40)] distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.7.9-r1, 1.6.3, 1.9.5, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa berkdb bitmap-fonts cdr crypt cups curl dvd eds esd fam flac font-server foomaticdb fortran gdbm gif gimpprint gkt2 gnome gpm gstreamer gtk imagemagick imlib ipv6 jp2 jpeg lzw lzw-tiff mad motif mozilla mp3 ncurses nls nptl nptlonly ogg opengl oss pam perl png ppds python readline samba spell ssl tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xine xml xml2 xmms xpm xrandr xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Created attachment 62641 [details, diff] amd64-mmx-fix.patch Try this patch. WindowMaker has a problem with mmx on amd64. I've been using this patch for quite a while now.
georgi: are you using amd64? do you get the same error as vano if you do not use this patch you provided? ... also, next time please create a new bug for something like this, as *this bug* is solved, whereas amd64/mmx issues are a totally new topic.
> georgi: are you using amd64? do you get the same error as vano if you do not > use this patch you provided? > > ... also, next time please create a new bug for something like this, as *this > bug* is solved, whereas amd64/mmx issues are a totally new topic. OK, bug #97963, as to not clutter this bug with further amd64-related comments. And to answer your questions, yes I do and yes I do.
how should I apply this patch?
closing
