unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: jesse <jgibbons2357@gmail.com>
Cc: 34922@debbugs.gnu.org
Subject: bug#34922: guile-wm crashes on login
Date: Wed, 20 Mar 2019 20:12:27 +0100	[thread overview]
Message-ID: <87ftrh8in8.fsf@elephly.net> (raw)
In-Reply-To: <f442696d-bd36-29b7-5f5d-8697d665e792@gmail.com>


Hi Jesse,

> I am trying to use guile-wm, but it fails when I launch it.

Thank you for this excellent bug report!

> From what I can tell, it is attempting to re-compile guile-wm, and
> cannot find the prerequisite guile-xcb package files.

> Possible solutions:
>
> -Edit the guile-wm package to include guile-xcb in the
> propagated-inputs. As the manual says, "Another example where
> |propagated-inputs| is useful is for languages that lack a facility to
> record the run-time search path akin to the |RUNPATH| of ELF files; this
> includes Guile, Python, Perl, and more. To ensure that libraries written
> in those languages can find library code they depend on at run time,
> run-time dependencies must be listed in |propagated-inputs| rather than
> |inputs|."

The guile-wm executable is already wrapped in GUILE_LOAD_PATH and
GUILE_LOAD_COMPILED_PATH, which should accomplish the same thing.  The
problem seems to be that the directories on GUILE_LOAD_COMPILED_PATH are
incorrect — they don’t contain any .go files!

The problem lies in the guile-wm package’s “'set-load-path” phase.
Instead of “share/guile/site/2.2” it should be using
“lib/guile/2.2/site-ccache” for the compiled load path.

--
Ricardo

  parent reply	other threads:[~2019-03-20 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 22:58 bug#34922: guile-wm crashes on login jesse
2019-03-20 17:32 ` ng0
2019-03-20 19:12 ` Ricardo Wurmus [this message]
2019-03-20 20:05   ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftrh8in8.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=34922@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).