From: Trev <trev@trevdev.ca>
To: Timo Wilken <timo@twilken.net>
Cc: help-guix@gnu.org
Subject: Re: Packaging timewarrior
Date: Mon, 16 Jan 2023 15:42:12 -0800 [thread overview]
Message-ID: <20230116234212.rjll3pyspuybdvka@guix> (raw)
In-Reply-To: <F39B87D5-AD86-4D38-8524-94B0C2FDF2EB@twilken.net>
On 23/01/16 06:03PM, Timo Wilken wrote:
> Hi Trev,
>
>
> On 16 January 2023 17:44:45 CET, Trev <trev@trevdev.ca> wrote:
> >If it's of any use to anybody, I have attached the full build log. Any
> >guidance would be appreciated.
>
> Make logs can be a bit annoying -- it runs multiple processes, and one make child can keep spewing info lines after another has already failed.
>
This is really good to know. I will try to be more patient with these
log files going forward.
> In your case, the "real" error is further up in the log:
>
> /gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/sh: line 1: /bin/sh: No such file or directory
> make[2]: *** [src/commands/CMakeFiles/generate_additional_help.dir/build.make:76: src/commands/additional-help.h] Error 127
>
> In Guix build containers, the /bin/sh symlink does not exist. Check timewarrior's makefiles for lines like "SHELL=/bin/sh" and substitute* them out with the result of something like #+(file-append bash-minimal "/bin/sh").
>
This did the trick!
-----
(arguments (list
#:phases #~(modify-phases %standard-phases
(add-after 'patch-source-shebangs 'patch-hardcoded-paths
(lambda _
(substitute* "src/commands/CMakeLists.txt"
(("/bin/sh") (string-append
#$(this-package-input
"bash-minimal")
"/bin/sh"))))))))
-----
I will clean my code up and get this contributed upstream :)
> Cheers,
> Timo
Cheers to you too. Thank you for the coaching and assistance.
--
Trev : 0FB7 D06B 4A2A F07E AD5B 1169 183B 6306 8AA1 D206
prev parent reply other threads:[~2023-01-16 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 16:44 Packaging timewarrior Trev
2023-01-16 17:03 ` Timo Wilken
2023-01-16 23:42 ` Trev [this message]
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=20230116234212.rjll3pyspuybdvka@guix \
--to=trev@trevdev.ca \
--cc=help-guix@gnu.org \
--cc=timo@twilken.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.
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).