From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: failed to create path for auto-compiled file
Date: Tue, 15 Jan 2019 17:59:04 -0800 [thread overview]
Message-ID: <bace82b6-0575-bdfc-738a-ccd12b6eb45f@gmail.com> (raw)
Hi All,
I maintain an add-on package to Guile. I have a user reporting the following
WARNING:
;;; compiling /usr/share/guile/site/2.2/nyacc/lang/c99/ffi-help.scm
;;; WARNING: compilation of /usr/share/guile/site/2.2/nyacc/lang/c99/ffi-help.scm failed:
;;; failed to create path for auto-compiled file "/usr/share/guile/site/2.2/nyacc/lang/c99/ffi-help.scm"
So my part of my package, including the file above, depends on scheme-bytestructures.
If, on installation (presumably as root), bytestructures is not found, then only the
sources are installed. Now it seems a user has bytestructures in his own path and
now he wants to use ffi-help, but it's not getting compiled. I would expect
Guile to compile and install in the user's .cache directory if write to a root-owned
directory (e.g., /usr/lib/guile/2.2/site-ccache) fails.
Am I missing something? Should this be reported as a bug?
Matt
next reply other threads:[~2019-01-16 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 1:59 Matt Wette [this message]
2019-01-17 13:34 ` failed to create path for auto-compiled file Matt Wette
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bace82b6-0575-bdfc-738a-ccd12b6eb45f@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@gnu.org \
/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.
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).