[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#33755: error: execlp: No such file or directory from guix environmen

From: Timothy Sample
Subject: bug#33755: error: execlp: No such file or directory from guix environment
Date: Sun, 16 Dec 2018 23:41:38 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Hi Ludo,

Ludovic Courtès <address@hidden> writes:

> Hello comrades!
> Timothy Sample <address@hidden> skribis:
>> [...]
>> From aedc745a3f9765ae00dc61a59fa53d22a458551b Mon Sep 17 00:00:00 2001
>> From: Timothy Sample <address@hidden>
>> Date: Sat, 15 Dec 2018 23:17:46 -0500
>> Subject: [PATCH] environment: Print command name on execlp error.
>> Fixes <https://bugs.gnu.org/33755>.
>> * guix/scripts/environment.scm (launch-environment): When execlp fails,
>> include the command name in the error message.
> Another option would be to do:
>   (set! execl
>     (error-reporting-wrapper …))
> in (guix ui), as done for a few other procedures that have the same
> issue.

Aha!  I didn’t know about “error-reporting-wrapper”.  I think this makes
sense.  It fixes the same issue in the container script, too.  I’ve
attached an updated patch.

I had to modify “error-reporting-wrapper” to deal with the fact that
“execlp” takes a variable number of arguments.  I tested it and it works
for the old use-case as well as the new.  On whether or not it works
stylistically, I defer to you.

-- Tim

Attachment: 0001-ui-Report-file-names-in-system-error-exceptions-from.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]