I'm still getting this error sometimes when using the
WEBKIT_USE_SINGLE_WEB_PROCESS=1 workaround, so it seems like there must
be something else at work. Seems to be soemthing hardware specific, as
my computer at home doesn't seem to have this problem, but it would be
nice anyway to figure out the c
zimoun writes:
> To ease the debugging processing, you should not run '-j4'.
ok
> Well, first about your "last" error: […] It comes from the
> environment variable SHELL which is not defined because of
> '--pure'. So you need somehow to export SHELL or CONFIG_SHELL
> otherwise, you will get a
On Mon, 2020-03-02 at 14:29 -0500, Maxim Cournoyer wrote:
> Build log extract:
>
> --8<---cut here---start->8---
> starting phase `check'
> running "python setup.py" with command "test" and parameters ()
> running test
> running egg_info
> writing anndata.egg-in
Hello Janneke,
> Do you have a patch/branch where I can see this related error? If mes
> builds are an exception, it could be nice to solve it there? Or is
> this a Qemu thing and is Qemu the only package that suffers from this?
>
> Trying to help here, but I'm not sure if I understand what's
The sbcl build system generates a new .asd that refers to all the
required input explicitly in the store.
The asdf-build-system/source does not do that. Because of this,
installing the source packages in a profile does not work as expected:
loading the source in a Common Lisp REPL will fail, comp
