From: Lars Rustand <rustand.lars@gmail.com>
To: help-guix@gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: Re: Help packaging network-manager-sstp and sstp-client
Date: Wed, 24 Jan 2024 22:34:16 +0100 [thread overview]
Message-ID: <87le8ecqkj.fsf@yoga.mail-host-address-is-not-set> (raw)
In-Reply-To: <Za9pgA15K-v0jFQp@3900XT>
Efraim Flashner <efraim@flashner.co.il> writes:
> Looking at the source code¹ it looks like the included autoconf script
> tries to execute configure. This doesn't work because between the
> bootstrap phase and the configure phase we have a phase to adjust the
> locations of /bin/sh and other binaries. I'd suggest overriding the
> 'bootstrap phase with something like:
>
> (replace 'bootstrap
> (lambda _
> (invoke "autoconf" "-vfi")))
>
> ¹ https://gitlab.com/sstp-project/sstp-client/-/blob/master/autogen.sh?ref_type=heads#L19
Thanks Efraim, that worked (with a small modification - I had to use
autoreconf instead of autoconf, since autoconf did not recognize the
-vfi flags), so now the package built successfully.
Do you have any ideas for the other package as well? I still have not
figured out how to build that one. From looking at the autogen.sh script
there seems to be a similar situation here, this script also tries to
execute configure, but replacing the bootstrap phase did not do anything
for this package.
next prev parent reply other threads:[~2024-01-24 22:31 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
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 [this message]
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=87le8ecqkj.fsf@yoga.mail-host-address-is-not-set \
--to=rustand.lars@gmail.com \
--cc=efraim@flashner.co.il \
--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).