Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Oct 2013 02:39:04 +0000
From:      Brendan Fabeny <bf1783@gmail.com>
To:        Joseph Mingrone <jrm@ftfl.ca>
Cc:        ports@freebsd.org, bf@freebsd.org
Subject:   Re: FreeBSD Port: lang/sbcl
Message-ID:  <CAGFTUwOxdOW4X24o%2BvwfiRhva3a4BZM-WJB7Lo6J0wAQyYqNpQ@mail.gmail.com>
In-Reply-To: <86siwa2ykr.fsf@gly.ath.cx>
References:  <86siwa2ykr.fsf@gly.ath.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/9/13, Joseph Mingrone <jrm@ftfl.ca> wrote:
> Hi,
>
> After upgrading sbcl to 1.1.12, stumpwm no longer compiles.  I'm
> compiling stumpwm from the git repository, which hasn't changed in quite
> awhile.
>
> If there is anything I can test or any other information I can provide,
> please let me know.
>
> Joseph
>
> % gmake
> /usr/local/bin/sbcl --load ./make-image.lisp
> This is SBCL 1.1.12, 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.
> WARNING:
>    compiling #<STATIC-FILE "sb-bsd-sockets" "NEWS"> completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/NEWS"
> WARNING:
>    loading #<STATIC-FILE "sb-bsd-sockets" "NEWS"> completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/NEWS"
> WARNING:
>    compiling #<STATIC-FILE "sb-bsd-sockets" "TODO"> completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/TODO"
> WARNING:
>    loading #<STATIC-FILE "sb-bsd-sockets" "TODO"> completed without its
> input file #P"/usr/local/lib/sbcl/sb-bsd-sockets/TODO"
>
> debugger invoked on a ASDF/FIND-SYSTEM:MISSING-COMPONENT:
>   Component STUMPWM not found
>

Yes, lang/sbcl switched to a newer version of ASDF, which handles the
loading of modules differently.  I had hoped to patch the two
dependent ports that are now broken because of this as part of the
sbcl update, but I was coming under some pressure to update sbcl, and
I didn't have a lot of time. From my cursory look during the sbcl
update, I believe that this error can be fixed by patching the broken
dependent ports so that they issue a pathspec to the working directory
in the "require" statement in the Makefile, or by splitting eache of
the broken ports into two subports, one of which installs source code
in the system module directory, and another which subsequently
compiles it, as is done now for some of the cl-* ports.  I don't know
if there are other problems. When the ASDF port and other CL compilers
are updated to newer versions of ASDF, the broken ports will probably
not work with them, either.

Regards,
          b.


> Type HELP for debugger help, or (SB-EXT:EXIT) 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/home/jrm/scm/stumpwm.git/./make-image.lisp".
>   2: [ABORT   ] Abort loading file
> "/usr/home/jrm/scm/stumpwm.git/./make-image.lisp".
>   3:            Ignore runtime option --load "./make-image.lisp".
>   4:            Skip rest of --eval and --load options.
>   5:            Skip to toplevel READ/EVAL/PRINT loop.
>   6: [EXIT    ] Exit SBCL (calling #'EXIT, killing the process).
>
> ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP STUMPWM)
> [fast-method]
> 0]
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGFTUwOxdOW4X24o%2BvwfiRhva3a4BZM-WJB7Lo6J0wAQyYqNpQ>