On Wed, Jan 24, 2024 at 10:34:16PM +0100, Lars Rustand wrote:
>
> Efraim Flashner 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 phas
Efraim Flashner 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 o
On Fri, Jan 19, 2024 at 08:26:23AM +0100, Lars Rustand wrote:
>
> Hello, I'm trying to package network-manager-sstp (and its dependency
> sstp-client), but I'm running into a weird error. I'm sure it is a very
> easy problem to solve for someone with a little more experience with the
> build-syste
Hi Lars,
On Sun, Jan 21 2024, Lars Rustand wrote:
> Maybe the setenv is only taking effect inside the added phase and is
> not propagated to the configure phase?
I don't think so. I used the same trick here:
https://codeberg.org/lechner/juix/src/commit/fc328c57a4bf100d6b16a7f14e9c96d29a083ba
On Sun, Jan 21 2024, Clément Lassieur wrote:
> On Sun, Jan 21 2024, Felix Lechner via wrote:
>
> I forgot to say that in this snippet #$(file-append bash ...), bash
> doesn't refer to the native input, it directly refers to the bash
> package. To refer to an input, you need to use ‘this-package-i
On Sun, Jan 21 2024, Felix Lechner via wrote:
> Hi Lars,
>
> On Fri, Jan 19 2024, Lars Rustand wrote:
>
>> ./autogen.sh: ./configure: /bin/sh: bad interpreter: No such file or
>> directory
>
> I would use something like this [1]
>
> (arguments
> (list
> #:phases
> #~(modify-p
Felix Lechner 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")))
Hello,
On Sun, Jan 21 2024, Felix Lechner via wrote:
> Hi Lars,
>
> On Fri, Jan 19 2024, Lars Rustand wrote:
>
>> ./autogen.sh: ./configure: /bin/sh: bad interpreter: No such file or
>> directory
>
> I would use something like this [1]
>
> (arguments
> (list
> #:phases
> #~(
Hi Lars,
On Fri, Jan 19 2024, Lars Rustand wrote:
> ./autogen.sh: ./configure: /bin/sh: bad interpreter: No such file or directory
I would use something like this [1]
(arguments
(list
#:phases
#~(modify-phases %standard-phases
(add-before 'configure 'provide-shell
> sstp-client is failing with the following error:
>
> --8<---cut here---start->8---
> ./autogen.sh: ./configure: /bin/sh: bad interpreter: No such file or
> directory error: in phase 'bootstrap': uncaught exception:
> %exception #<&invoke-error program: "./auto
Hello, I'm trying to package network-manager-sstp (and its dependency
sstp-client), but I'm running into a weird error. I'm sure it is a very
easy problem to solve for someone with a little more experience with the
build-system.
>From what I can tell these packages should be fairly standard auto
11 matches
Mail list logo
