Emerging sbcl on Linux x86 prefix portage fails. The following is seen in the console log: cc -g -Wall -Wsign-compare -O3 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I. -c -o x86-linux-os.o x86-linux-os.c cc -g -Wall -Wsign-compare -O3 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I. -c -o gencgc.o gencgc.c cc -g -Wall -Wsign-compare -O3 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I. -c -o x86-assem.o x86-assem.S x86-assem.S: Assembler messages: x86-assem.S:133: Error: suffix or operands invalid for `fnstsw' make: *** [x86-assem.o] Error 1 make: Leaving directory `/local/scratch/portage/dev-lisp/sbcl-1.0.15/work/sbcl-1.0.15/src/runtime' * ERROR: dev-lisp/sbcl-1.0.15 failed: * make failed * * Call stack: * ebuild.sh: 49: <call src_compile> * environment:2445: env - HOME="${T}" PATH="${bindir}/src/runtime:${PATH}" SBCL_HOME="${bindir}/output" GNUMAKE=make ./make.sh "sbcl --sysinit /dev/null --userinit /dev/null --disable-debugger --core ${bindir}/output/sbcl.core" || die "make failed"; * * If you need support, post the topmost build error, and the call stack if relevant. * build log: '/local/scratch/portage/dev-lisp/sbcl-1.0.15/temp/build.log' * ebuild environment: '/local/scratch/portage/dev-lisp/sbcl-1.0.15/temp/environment' * S: '/local/scratch/portage/dev-lisp/sbcl-1.0.15/work/sbcl-1.0.15' An attempt was done to mask some recent versions of sbcl, causing 1.0.9 to be emerged. This did not help; the same error occurs.
I fixed this issue. Please use the patch that I will upload here in a sec. From [1]: "Starting from the 2.18.50.0.4 release, the x86 assembler no longer accepts fnstsw %eax fnstsw stores 16bit into %ax and the upper 16bit of %eax is unchanged. Please use fnstsw %ax " [1]: http://www.nabble.com/The-Linux-binutils-2.18.50.0.4-is-released-td15360254.html
Created attachment 149251 [details, diff] applies to ${S}/src/runtime/x86-assem.S
Created attachment 149253 [details] patch applies to sbcl-1.0.15.ebuild @grobian: This one needs to be assigned to the common-lisp herd. I believe they should fix this..yes?
adding common-lisp to CC, we're probably the first to see it since we don't have stable keywords ;)
patch sent upstream
Fixed in r21842, closing bug. Patch sent upstream (comment #5) so resolving as UPSTREAM.