From: Lars Rustand <rustand.lars@gmail.com>
To: help-guix@gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: Help packaging network-manager-sstp and sstp-client
Date: Sun, 21 Jan 2024 15:40:02 +0100 [thread overview]
Message-ID: <87il3md9ec.fsf@yoga.mail-host-address-is-not-set> (raw)
In-Reply-To: <87sf2qydct.fsf@lease-up.com>
Felix Lechner <felix.lechner@lease-up.com> writes:
> Hi Lars,
>
> I would use something like this [1]
>
> (arguments
> (list
> #:phases
> #~(modify-phases %standard-phases
> (add-before 'configure 'provide-shell
> (lambda _
> (setenv "CONFIG_SHELL" (which "sh")))))))
> (native-inputs (list bash))
>
> although the (which "sh") is kind of lazy and should probably be
> replaced by something like
>
> #$(file-append bash "/bin/sh")
>
> Kind regards
> Felix
>
> [1] https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/config_002estatus-Invocation.html
Thanks Felix, I tried your suggestion (with the file-append instead of
which), but it still fails the same way. I tried building with
`--keep-failed` and checked the contents of `environment-variables`, but
the variable is not inside this file. Maybe the setenv is only taking
effect inside the added phase and is not propagated to the configure phase?
Also, I thought the gnu-build-system should already take care of setting
this variable? From the below output I can see that it is at least set
correctly for network-manager-sstp, which uses an almost identical
package definition.
Lars Rustand <rustand.lars@gmail.com> writes:
> And network-manager-sstp fails with:
>
> checking for find... yes
> ./configure: line 13451: syntax error near unexpected token `fcntl.h'
> ./configure: line 13451: ` fcntl.h'
> error: in phase 'configure': uncaught exception:
> %exception #<&invoke-error program: "/gnu/store/m6c5hgqg569mbcjjbp8l8m7q82ascpdl-bash-5.1.16/bin/bash" arguments: ("./configure" "CONFIG_SHELL=/gnu/store/m6c5hgqg569mbcjjbp8l8m7q82ascpdl-bash-5.1.16/bin/bash" "SHELL=/gnu/store/m6c5hgqg569mbcjjbp8l8m7q82ascpdl-bash-5.1.16/bin/bash" "--prefix=/gnu/store/rly5wz0vmbfawl7xiwdkgphsjwz8lgzm-network-manager-sstp-1.3.2" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu") exit-status: 2 term-signal: #f stop-signal: #f>
> phase `configure' failed after 1.5 seconds
> command "/gnu/store/m6c5hgqg569mbcjjbp8l8m7q82ascpdl-bash-5.1.16/bin/bash" "./configure" "CONFIG_SHELL=/gnu/store/m6c5hgqg569mbcjjbp8l8m7q82ascpdl-bash-5.1.16/bin/bash" "SHELL=/gnu/store/m6c5hgqg569mbcjjbp8l8m7q82ascpdl-bash-5.1.16/bin/bash" "--prefix=/gnu/store/rly5wz0vmbfawl7xiwdkgphsjwz8lgzm-network-manager-sstp-1.3.2" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" failed with status 2
next prev parent reply other threads:[~2024-01-21 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 7:26 Help packaging network-manager-sstp and sstp-client Lars Rustand
2024-01-21 7:25 ` Marek Paśnikowski
2024-01-21 14:23 ` Felix Lechner via
2024-01-21 14:40 ` Lars Rustand [this message]
2024-01-21 16:03 ` Felix Lechner via
2024-01-21 14:50 ` Clément Lassieur
2024-01-21 15:37 ` Clément Lassieur
2024-01-21 16:00 ` Felix Lechner via
2024-01-23 7:23 ` Efraim Flashner
2024-01-24 21:34 ` Lars Rustand
2024-01-28 17:42 ` Efraim Flashner
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=87il3md9ec.fsf@yoga.mail-host-address-is-not-set \
--to=rustand.lars@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=help-guix@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).