Bug#593179: common-lisp-controller: clbuild with ccl fails to use user-writable cache for compiled files
What is the value returned by (asdf::compute-output-translations) ?
Could you provide your operation?
On Mon, Aug 16, 2010 at 08:32, John Foerch <jjfoerch at earthlink.net> wrote:
> Package: common-lisp-controller
> Version: 7.2
> Severity: normal
>
> When clbuild is configured to use ccl (instead of sbcl), during autocompilation
> of libraries installed through clbuild, the system attempts to put compiled
> files into the /usr/share/common-lisp/clbuild/source/... directory tree,
> resulting in a write-permissions error.
>
>
>
> -- System Information:
> Debian Release: squeeze/sid
> ?APT prefers testing
> ?APT policy: (990, 'testing'), (650, 'stable'), (600, 'unstable'), (500, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages common-lisp-controller depends on:
> ii ?adduser ? ? ? ? ? ? ? ? ? ? ? 3.112 ? ? ?add and remove users and groups
> ii ?bash ? ? ? ? ? ? ? ? ? ? ? ? ?4.1-3 ? ? ?The GNU Bourne Again SHell
> ii ?cl-asdf ? ? ? ? ? ? ? ? ? ? ? 2:1.704-1 ?Another System Definition Facility
> ii ?debconf [debconf-2.0] ? ? ? ? 1.5.33 ? ? Debian configuration management sy
> ii ?debianutils ? ? ? ? ? ? ? ? ? 3.4 ? ? ? ?Miscellaneous utilities specific t
> ii ?perl ? ? ? ? ? ? ? ? ? ? ? ? ?5.10.1-13 ?Larry Wall's Practical Extraction
> ii ?realpath ? ? ? ? ? ? ? ? ? ? ?1.15 ? ? ? Return the canonicalized absolute
>
> common-lisp-controller recommends no packages.
>
> Versions of packages common-lisp-controller suggests:
> ii ?sbcl ? ? ? ? ? ? ? ? ? ? ? ?1:1.0.40.0-2 A Common Lisp compiler and develop
>
> -- debconf information excluded
>
>
>
> _______________________________________________
> pkg-common-lisp-devel mailing list
> pkg-common-lisp-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
>
Reply to: