unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: add lispf4
Date: Sun, 14 Feb 2016 22:36:39 +0100	[thread overview]
Message-ID: <87h9hb55zs.fsf@elephly.net> (raw)
In-Reply-To: <87k2m77zcn.fsf@grrlz.net>


Nils Gillmann <niasterisk@grrlz.net> writes:

> open("SYSATOMS", O_RDONLY)              = -1 ENOENT (No such file or directory)
> write(2, "Can't open 'SYSATOMS'\n", 22Can't open 'SYSATOMS'
> ) = 22
> exit_group(1)                           = ?
> +++ exited with 1 +++

Does this also happen when you run lispf4 from the very same directory
that contains SYSATOMS?  It seems to me that we should patch the sources
such that it opens SYSATOMS with its full path.

~~ Ricardo

  reply	other threads:[~2016-02-14 21:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 18:45 [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-06 22:14 ` Leo Famulari
2016-02-07  0:01   ` Nils Gillmann
2016-02-07 10:59     ` Ricardo Wurmus
2016-02-07 11:09     ` Ricardo Wurmus
2016-02-07 15:09       ` Nils Gillmann
2016-02-18 11:38         ` [PATCH] gnu: add lispf4 (Update) Nils Gillmann
2016-02-18 11:48           ` Ricardo Wurmus
2016-02-07 16:50 ` [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-08  0:36   ` Leo Famulari
2016-02-08 11:17     ` Nils Gillmann
2016-02-08 20:14       ` Leo Famulari
2016-02-09  1:31         ` Nils Gillmann
2016-02-09  7:16           ` Efraim Flashner
2016-02-09 10:30             ` Nils Gillmann
2016-02-10  5:36               ` Leo Famulari
2016-02-10 13:48                 ` Nils Gillmann
2016-02-12  4:00                   ` Leo Famulari
2016-02-14  3:52             ` Nils Gillmann
2016-02-14  8:10               ` Ricardo Wurmus
2016-02-14 21:31                 ` Nils Gillmann
2016-02-14 21:36                   ` Ricardo Wurmus [this message]
2016-02-14  4:05             ` Nils Gillmann

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=87h9hb55zs.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=niasterisk@grrlz.net \
    /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).