bug#41254: closed ([PATCH] gnu: boost: Add which to native-inputs.)

[GNU bug Tracking System]

Your message dated Thu, 14 May 2020 14:13:08 +0200
with message-id <87tv0id8a3.fsf@nckx>
and subject line Re: [bug#41254] [PATCH] gnu: boost: Add which to native-inputs.
has caused the debbugs.gnu.org bug report #41254,
regarding [PATCH] gnu: boost: Add which to native-inputs.
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
41254: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41254
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [PATCH] gnu: boost: Add which to native-inputs.
>
>
>
>
> Date: 
>
> Thu, 14 May 2020 12:13:53 +0200
>
>
>
>
> To fix:
> ./bootstrap.sh: line 28: which: command not found
>
> * gnu/packages/boost.scm (boost)[native-inputs]: Add which.
> ---
>  gnu/packages/boost.scm | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/boost.scm b/gnu/packages/boost.scm
> index 2f2ca289ab..f6f442c5bf 100644
> --- a/gnu/packages/boost.scm
> +++ b/gnu/packages/boost.scm
> @@ -38,6 +38,7 @@
>    #:use-module (guix build-system gnu)
>    #:use-module (guix build-system trivial)
>    #:use-module (gnu packages)
> +  #:use-module (gnu packages base)
>    #:use-module (gnu packages compression)
>    #:use-module (gnu packages icu4c)
>    #:use-module (gnu packages perl)
> @@ -82,7 +83,8 @@
>         ,@(if (%current-target-system)
>               '()
>               `(("python" ,python-wrapper)))
> -       ("tcsh" ,tcsh)))
> +       ("tcsh" ,tcsh)
> +       ("which" ,which)))
>      (arguments
>       `(#:imported-modules ((guix build python-build-system)
>                             ,@%gnu-build-system-modules)
> -- 
> 2.26.2
>
>
>
>
> --- End Message ---

--- Begin Message --- Subject: Re: [bug#41254] [PATCH] gnu: boost: Add which to native-inputs. Date: Thu, 14 May 2020 14:13:08 +0200

Vincent Legoll 写道：

On 14/05/2020 13:23, Tobias Geerinckx-Rice wrote:

I'm not convinced that increasing the number of inputs to silence

(harmless) warnings in the build logs is a way to go.

It did not look harmless to me...

I understand. It's actually quite common (as these things go) but tends to go unnoticed exactly because it's harmless. Once you notice it you see it everywhere.

Nope, feel free to close the issue

Done!

Kind regards,

T G-R

signature.asc
Description: PGP signature

--- End Message ---