On 04/13/2013 09:53 AM, Waldek Hebisch wrote:
> Andrey Grozin wrote:
>> On Sat, 13 Apr 2013, James M. Lawrence wrote:
>>> On Sat, Apr 13, 2013 at 1:16 AM, <A.G.Grozin@...> wrote:
>>>> This is SBCL 1.1.6, an implementation of ANSI Common Lisp.
>>> You are headed for an unrelated problem -- there are reports that
>>> maxima doesn't build on sbcl-1.1.6 due to the SVREF issue.
>> Sorry for the noise. I had 2 different versions of asdf installed; after I
>> removed one, I can build maxima successfully (Gentoo linux, x86_64), and
>> sbcl shows the best time running the maxima testsuite.
> BTW: Do you know that by default Gentoo still ships broken sbcl?
> AFAICS default is 'dev-lisp/sbcl-1.0.55-r1' and in startup
> script it pulls 'dev-lisp/gentoo-init-0.1' which uses
> ASDF-BINARY-LOCATIONS. Effect:
> (require :sb-posix)
> gives compliants about ASDF 2 beeing incompatible with
> ASDF-BINARY-LOCATIONS. I saw the problem mentined in October 2012...
For those who don't use gentoo, and are unfamiliar with the rinky-dinky
details of portage and its common lisp support:
Any gentoo user who is serious about their common lisp uses the lisp
overlay. The main portage tree's lisp packages are ancient. For some
reason they keep sbcl sorta kinda up to date, but all the asdf packages
are worthlessly old. I think it's because the lisp maintainers don't
have access to the main tree, so they are forced to do everything in an
sbcl-1.1.6 is in the lisp overlay. Last I checked it was still masked
because it needed further testing. Masking it caused portage to try
installing the mainline sbcl, asdf-binary-locations and gentoo-init. It
is currently necessary to unmask dev-lisp/sbcl, dev-lisp/uiop and
dev-lisp/asdf in order to stay on the overlay's packages.
The lisp overlay maintainers have this bad habit of removing older
ebuilds as soon as a new one becomes available, making it impossible to
go back a version. That's why masking the latest sbcl in the overlay
causes portage to fall back on the mainline sbcl. 1.0.58 was the most
recent 1.0.x version in the overlay, but it is gone now.