View previous topic :: View next topic |
Author |
Message |
Pilsner Tux's lil' helper
Joined: 14 Mar 2008 Posts: 89
|
Posted: Thu May 24, 2012 11:54 am Post subject: [SOLVED] failure to emerge maxima |
|
|
Hello to all.
There is a weird LISP-related failure when compiling Maxima package. This error look like:
Code: | ; - Compiling module "server"
; - Compiling source file
; "/var/tmp/portage/sci-mathematics/maxima-5.18.1/work/maxima-5.18.1/src/server.lisp"
; compiling file "/var/tmp/portage/sci-mathematics/maxima-5.18.1/work/maxima-5.18.1/src/server.lisp" (written 31 MAR 2009 11:40:58 PM):
; compiling (IN-PACKAGE :MAXIMA)
; compiling (REQUIRE (QUOTE ASDF))
; compiling (REQUIRE (QUOTE SB-POSIX))
; loading #P"/usr/lib64/sbcl/sb-posix/sb-posix.asd"
ASDF could not load sb-posix because
Error while trying to load definition for system sb-posix from pathname
/usr/lib64/sbcl/sb-posix/sb-posix.asd:
ASDF 2 is not compatible with ASDF-BINARY-LOCATIONS, which you are using.
ASDF 2 now achieves the same purpose with its builtin ASDF-OUTPUT-TRANSLATIONS,
which should be easier to configure. Please stop using ASDF-BINARY-LOCATIONS,
and instead use ASDF-OUTPUT-TRANSLATIONS. See the ASDF manual for details.
In case you insist on preserving your previous A-B-L configuration, but
do not know how to achieve the same effect with A-O-T, you may use function
ASDF:ENABLE-ASDF-BINARY-LOCATIONS-COMPATIBILITY as documented in the manual;
call that function where you would otherwise have loaded and configured A-B-L..
debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR in thread
#<THREAD "initial thread" RUNNING {1002999893}>:
Error while trying to load definition for system sb-posix from pathname
/usr/lib64/sbcl/sb-posix/sb-posix.asd:
ASDF 2 is not compatible with ASDF-BINARY-LOCATIONS, which you are using.
ASDF 2 now achieves the same purpose with its builtin ASDF-OUTPUT-TRANSLATIONS,
which should be easier to configure. Please stop using ASDF-BINARY-LOCATIONS,
and instead use ASDF-OUTPUT-TRANSLATIONS. See the ASDF manual for details.
In case you insist on preserving your previous A-B-L configuration, but
do not know how to achieve the same effect with A-O-T, you may use function
ASDF:ENABLE-ASDF-BINARY-LOCATIONS-COMPATIBILITY as documented in the manual;
call that function where you would otherwise have loaded and configured A-B-L.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry EVAL of current toplevel form.
1: [CONTINUE ] Ignore error and continue loading file "/usr/lib64/sbcl/sb-posix/sb-posix.asd".
2: [ABORT ] Abort loading file "/usr/lib64/sbcl/sb-posix/sb-posix.asd".
3: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system sb-posix
after reinitializing the
source-registry.
4: Ignore runtime option --eval "(progn (load \"../lisp-utils/defsystem.lisp\") (funcall (intern (symbol-name :operate-on-system) :mk) \"maxima\" :compile :verbose t) (sb-ext:quit))".
5: Skip rest of --eval and --load options.
6: Skip to toplevel READ/EVAL/PRINT loop.
7: [QUIT ] Quit SBCL (calling #'QUIT, killing the process).
((FLET #:LAMBDA1984 :IN ASDF::LOAD-SYSDEF)
#<SIMPLE-ERROR
"ASDF 2 is not compatible with ASDF-BINARY-LOCATIONS, which you are using.
ASDF 2 now achieves the same purpose with its builtin ASDF-OUTPUT-TRANSLATIONS,
which should be easier to configure. Please stop using ASDF-BINARY-LOCATIONS,
and instead use ASDF-OUTPUT-TRANSLATIONS. See the ASDF manual for details.
In case you insist on preserving your previous A-B-L configuration, but
do not know how to achieve the same effect with A-O-T, you may use function
ASDF:ENABLE-ASDF-BINARY-LOCATIONS-COMPATIBILITY as documented in the manual;
call that function where you would otherwise have loaded and configured A-B-L."
{1003970D23}>) |
Package sbcl has recently been upgraded, this could have some impact.
How to rectify this?
Last edited by Pilsner on Tue Jun 19, 2012 6:05 am; edited 1 time in total |
|
Back to top |
|
|
caracoles007 n00b
Joined: 30 May 2012 Posts: 1
|
|
Back to top |
|
|
Pilsner Tux's lil' helper
Joined: 14 Mar 2008 Posts: 89
|
Posted: Fri Jun 08, 2012 9:10 am Post subject: |
|
|
How does your /etc/sblcrc file looks like, now?
To me it still fails, at even earlier stage. |
|
Back to top |
|
|
momesana Apprentice
Joined: 20 Sep 2004 Posts: 212 Location: Germany (Bremen)
|
Posted: Sun Jun 10, 2012 4:28 pm Post subject: |
|
|
I have the same problem ... _________________ in the world I see, you're stalking elk throught the grand canyon forests, around the ruins of the rockefeller center. You'll wear leather clothes, that will last you the rest of your life... (Tylers Vision) |
|
Back to top |
|
|
Slow_cyclist n00b
Joined: 11 Apr 2009 Posts: 6
|
Posted: Sun Jun 10, 2012 6:50 pm Post subject: |
|
|
I commented out these rows in '/etc/gentoo-init.lisp':
;(asdf:oos 'asdf:load-op :asdf-binary-locations)
;(setf asdf:*centralize-lisp-binaries* t)
;(setf asdf:*source-to-target-mappings* '((#p"/usr/lib/sbcl/" nil) (#p"/usr/lib64/sbcl/" nil)))
Not sure if this causes other problems, but it solved this one...
I also found that I had to upgrade to the masked 2010-11-03 version of slime, because
the 2008 one doesn't compile in the current version of sbcl.
Please take all this with a big grain of salt! |
|
Back to top |
|
|
phd n00b
Joined: 12 Oct 2005 Posts: 68 Location: Warszawa (Poland)
|
Posted: Sun Jun 17, 2012 9:58 am Post subject: |
|
|
A few days ago, I had the similar problem with the use of maxima in emacs (imaxima). The problem solved me itself by emerging the maxima-5.27.0-r1
ACCEPT_KEYWORDS="~amd64" emerge -pv maxima
[ebuild R ] sci-mathematics/maxima-5.27.0-r1 USE="X emacs latex nls unicode -clisp -clozurecl (-cmucl) -ecls (-gcl) -sbcl -tk -xemacs" LINGUAS="-es -pt -pt_BR"
Probably, in my case, the essential was the option +emacs which induced for other packages the dependencies among others: +sbcl and +asdf and maybe something more. |
|
Back to top |
|
|
Pilsner Tux's lil' helper
Joined: 14 Mar 2008 Posts: 89
|
Posted: Tue Jun 19, 2012 6:04 am Post subject: |
|
|
Quote: | I commented out these rows in '/etc/gentoo-init.lisp':
;(asdf:oos 'asdf:load-op :asdf-binary-locations)
;(setf asdf:*centralize-lisp-binaries* t)
;(setf asdf:*source-to-target-mappings* '((#p"/usr/lib/sbcl/" nil) (#p"/usr/lib64/sbcl/" nil))) |
Brilliant, that solved mine compilation problem as well!
Wonder what it does. |
|
Back to top |
|
|
stephandale Tux's lil' helper
Joined: 28 Jan 2006 Posts: 86
|
|
Back to top |
|
|
nihil39 Tux's lil' helper
Joined: 15 Nov 2005 Posts: 97 Location: Italy
|
Posted: Mon Aug 20, 2012 8:58 am Post subject: |
|
|
Should we file a bug for this? After all we don't know well what that lines that we are commenting out do. I don't know if it's safe to edit a file like '/etc/gentoo-init.lisp only to fix a compilation issue in an ebuild.
Are we sure that enabling or disabling any use flag can't solve the issue? |
|
Back to top |
|
|
stephandale Tux's lil' helper
Joined: 28 Jan 2006 Posts: 86
|
|
Back to top |
|
|
MacGuges n00b
Joined: 26 Aug 2011 Posts: 4 Location: Rochester, NY
|
Posted: Sun Sep 02, 2012 2:27 am Post subject: |
|
|
I recently installed SBCL and SLIME, then encountered the same error when starting slime from emacs,
Quote: | (progn (load "/usr/share/emacs/site-lisp/slime/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank:start-server") "/tmp/slime.14430" :coding-system "iso-latin-1-unix"))
This is SBCL 1.0.55, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
STYLE-WARNING: redefining ASDF::LISP-VERSION-STRING in DEFUN
*
; loading #P"/usr/share/emacs/site-lisp/slime/swank-loader.lisp"
debugger invoked on a SIMPLE-ERROR in thread
#<THREAD "initial thread" RUNNING {1002998D43}>:
ASDF 2 is not compatible with ASDF-BINARY-LOCATIONS, which you are using.
ASDF 2 now achieves the same purpose with its builtin ASDF-OUTPUT-TRANSLATIONS,
which should be easier to configure. Please stop using ASDF-BINARY-LOCATIONS,
and instead use ASDF-OUTPUT-TRANSLATIONS. See the ASDF manual for details.
In case you insist on preserving your previous A-B-L configuration, but
do not know how to achieve the same effect with A-O-T, you may use function
ASDF:ENABLE-ASDF-BINARY-LOCATIONS-COMPATIBILITY as documented in the manual;
call that function where you would otherwise have loaded and configured A-B-L.
|
Applying the suggestions in this thread, I've been able to get to the CL-USER prompt. Here's my /etc/gentoo-init.lisp:
Code: | (in-package #:cl-user)
#+(or sbcl ecl) (require :asdf)
#-(or sbcl ecl) (load #p"/usr/share/common-lisp/source/asdf/asdf.lisp")
(push #p"/usr/share/common-lisp/systems/" asdf:*central-registry*)
;;; added to correct error "ASDF 2 is not compatible with ASDF-BINARY-LOCATIONS" starting SLIME in emacs
;(asdf:oos 'asdf:load-op :asdf-binary-locations)
;(setf asdf:*centralize-lisp-binaries* t)
;(setf asdf:*source-to-target-mappings* '((#p"/usr/lib/sbcl/" nil) (#p"/usr/lib64/sbcl/" nil)))
(asdf:enable-asdf-binary-locations-compatibility :centralize-lisp-binaries t :source-to-target-mappings '((#p"/usr/lib/sbcl/" nil) (#p"/usr/lib64/sbcl/" nil)))
|
Thank you! |
|
Back to top |
|
|
oquol n00b
Joined: 23 Apr 2011 Posts: 12
|
Posted: Sun Nov 04, 2012 5:52 pm Post subject: |
|
|
phd wrote: | Probably, in my case, the essential was the option +emacs which induced for other packages the dependencies among others: +sbcl and +asdf and maybe something more. | Thank you
I had the same problem and
Code: | #echo 'sci-mathematics/maxima clisp -sbcl' >> /etc/portage/package.use |
solved it. _________________ Dell N5010, ATI HD5650 1GiB, HDD 500GiB, Core i3 370 2,4GHz |
|
Back to top |
|
|
rickj Guru
Joined: 06 Feb 2003 Posts: 427 Location: Calgary, Alberta, Canada
|
|
Back to top |
|
|
rickj Guru
Joined: 06 Feb 2003 Posts: 427 Location: Calgary, Alberta, Canada
|
Posted: Wed Feb 05, 2014 9:20 pm Post subject: |
|
|
This is not going well. Having found that sbcl and clisp will not compile, experiment shows that gcl can no longer be selected, leaving only cmucl as a possible lisp to support the maxima
package.
but cmucl will not compile:
Code: | ../../src/lisp/x86-assem.S:82: Error: operand type mismatch for `fnstsw'
gmake[1]: *** [x86-assem.o] Error 1 |
So apparently there is no lisp that supports maxima at present |
|
Back to top |
|
|
spitzmaus n00b
Joined: 14 Feb 2014 Posts: 6
|
|
Back to top |
|
|
|