From: "Ludovic Courtès" <ludo@gnu.org>
To: Brendan Tildesley <mail@brendan.scot>
Cc: 51783@debbugs.gnu.org, Vinicius Monego <monego@posteo.net>,
Leo Famulari <leo@famulari.name>
Subject: [bug#51783] [PATCH core-updates-frozen] gnu: Complete renaming openexr to openexr-2.
Date: Thu, 18 Nov 2021 15:30:05 +0100 [thread overview]
Message-ID: <87k0h5pmdu.fsf@gnu.org> (raw)
In-Reply-To: <20211112064010.17943-1-mail@brendan.scot> (Brendan Tildesley's message of "Fri, 12 Nov 2021 17:40:10 +1100")
Hi,
Brendan Tildesley <mail@brendan.scot> skribis:
> * gnu/packages/kde.scm (krita):[configure-flags]: d71336b2e3 missed one
> reference of openexr that should have become openexr-2, breaking krita's
> build. Rename it.
> ---
> gnu/packages/kde.scm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gnu/packages/kde.scm b/gnu/packages/kde.scm
> index 2b843f163a..b74ea81b61 100644
> --- a/gnu/packages/kde.scm
> +++ b/gnu/packages/kde.scm
> @@ -471,7 +471,7 @@ (define-public krita
> `(#:tests? #f
> #:configure-flags
> ,#~(list "-DBUILD_TESTING=OFF"
> - (string-append "-DCMAKE_CXX_FLAGS=-I" #$openexr
> + (string-append "-DCMAKE_CXX_FLAGS=-I" #$openexr-2
> "/include/OpenEXR"))))
Hmm what branch are you looking at? On today’s ‘core-updates-frozen’,
it looks like this:
#:configure-flags
(list "-DBUILD_TESTING=OFF"
(string-append "-DCMAKE_CXX_FLAGS=-I"
(assoc-ref %build-inputs "openexr")
"/include/OpenEXR"))
Use of gexps would be welcome but it hasn’t landed on
‘core-updates-frozen’ AFAICS.
Ludo’.
next prev parent reply other threads:[~2021-11-18 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 6:40 [bug#51783] [PATCH core-updates-frozen] gnu: Complete renaming openexr to openexr-2 Brendan Tildesley
2021-11-18 14:30 ` Ludovic Courtès [this message]
2021-11-20 11:06 ` Brendan Tildesley
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=87k0h5pmdu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51783@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=mail@brendan.scot \
--cc=monego@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).