From: Jack Hill <jackhill@jackhill.us>
To: guix-devel@gnu.org
Subject: Re: Help with $SHELL in perl package for backuppc
Date: Thu, 22 Aug 2019 10:49:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1908221045420.9756@marsh.hcoop.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1908211703530.9756@marsh.hcoop.net>
On Wed, 21 Aug 2019, Jack Hill wrote:
> However, that fails to build because it tries to invoke /bin/sh (see full
> build log at the end of this message).
>
> Line 2465 in configure.sh is suspicious as it reads:
>
> ```
> $SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 ||
> ```
>
> I tried modifying the package definition to add a phase that sets the SHELL
> variable, but that did not alter the build error. My package definition with
> that change looks like:
After a more careful reading of configure.sh, the variable to set is
CONFIG_SHELL, so a `(setenv "CONFIG_SHELL" (which "sh"))` does the trick.
That means I now have the following package definition that builds.
```
(define-public perl-backuppc-xs
(package
(name "perl-backuppc-xs")
(version "0.59")
(source
(origin
(method url-fetch)
(uri (string-append
"mirror://cpan/authors/id/C/CB/CBARRATT/BackupPC-XS-"
version
".tar.gz"))
(sha256
(base32
"1rp57x3amv4g3sa1az83f5xyw25cj7hhvmj3jczrkmfbrpnxlkca"))))
(build-system perl-build-system)
(arguments
'(#:phases
(modify-phases %standard-phases
(add-before 'configure 'set-environment-variables
(lambda _
(setenv "CONFIG_SHELL" (which "sh"))
#t)))))
(home-page
"https://backuppc.github.io")
(synopsis
"Perl extension for BackupPC libraries")
(description "to be written")
(license gpl3+)))
```
Now on to the other backuppc components.
Best,
Jack
prev parent reply other threads:[~2019-08-22 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 21:22 Help with $SHELL in perl package for backuppc Jack Hill
2019-08-22 14:49 ` Jack Hill [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1908221045420.9756@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guix-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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.