Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16042 - [allegro] does not build

Attached to Project: Arch Linux
Opened by Andrea Scarpino (BaSh) - Saturday, 05 September 2009, 20:33 GMT
Last edited by Ionut Biru (wonder) - Saturday, 07 November 2009, 17:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
gcc -DALLEGRO_MODULES_PATH=\"/usr/lib/allegro\" -DHAVE_CONFIG_H -I. -Iinclude -Iinclude/allegro -I./include -I./include/allegro -march=i686 -mtune=generic -O2 -pipe -DALLEGRO_LIB_BUILD -mtune=pentium -O2 -funroll-loops -ffast-math -fomit-frame-pointer -Wall -Wno-unused -x assembler-with-cpp -c ./src/i386/icpus.s -o obj/unix/shared/alleg/icpus.o
./src/i386/icpus.s: Assembler messages:
./src/i386/icpus.s:70: Error: suffix or operands invalid for `fnstsw'
make: *** [obj/unix/shared/alleg/icpus.o] Error 1

Additional info:
* allegro 4.2.2-1
This task depends upon

Closed by  Ionut Biru (wonder)
Saturday, 07 November 2009, 17:58 GMT
Reason for closing:  Fixed
Comment by Laurent Carlier (lordheavy) - Sunday, 01 November 2009, 16:27 GMT
After some search i've found that bugreport (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518732) in Debian for the explaination:
"Hi. The following patch fixes this bug. FNSTSW is "Store FPU Status
Word". This status word is a 16-bit value so the destination register
should be %ax, not %eax. Apparently old versions of binutils were a
bit lax."

Please test attached files to see if that fix the issue.

++
   fix-cpu-fnstsw.diff (0.4 KiB)
   PKGBUILD (1.2 KiB)
Comment by Ionut Biru (wonder) - Friday, 06 November 2009, 17:17 GMT
the fix is in the new version 4.2.3.1

Loading...