From: Andy Tai <atai@atai.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46724@debbugs.gnu.org
Subject: [bug#46724] [PATCH] gnu: vtk: Update to 9.0.1
Date: Fri, 19 Mar 2021 10:43:55 -0700 [thread overview]
Message-ID: <CAJsg1E-yu6jP4zCejD-h60zXayd2QU5fj25AgYHjyvk_aCQX=g@mail.gmail.com> (raw)
In-Reply-To: <877dm3jzgo.fsf_-_@gnu.org>
Ok, I'll take a look.
On Fri, Mar 19, 2021 at 1:54 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi Andy,
>
> Thanks for the update! I spent some time checking whether dependents,
> as returned by ‘guix refresh -l vtk’, would still build.
>
> It turns out tha ‘mia’ no longer builds after this update because the
> ‘VTK_INCLUDE_DIRS’ CMake variable remains empty. I’m not
> familiar (or averse to?) CMake, and I couldn’t figure out why that is
> the case.
>
> Could you take a look?
>
> As a last resort, we could preserve VTK 8.2 and use it in MIA.
>
> Attached is my variant of the patch, which propagates libogg, as was
> needed for some dependents, but really we could/should propagate
> libtheora, lz4, and double-conversion for the same reasons it seems.
>
> Let me know what you think!
>
> Thanks,
> Ludo’.
>
--
Andy Tai, atai@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2021 民國110年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能
next prev parent reply other threads:[~2021-03-19 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 19:16 [bug#46724] [PATCH] gnu: vtk: Update to 9.0.1 Andy Tai
2021-02-23 19:25 ` [bug#46724] helps OpenCV build Andy Tai
2021-03-02 19:23 ` [bug#46724] [PATCH] gnu: vtk: Update to 9.0.1 Ludovic Courtès
2021-03-02 19:37 ` Andy Tai
2021-03-06 10:36 ` Ludovic Courtès
2021-03-07 0:08 ` Andy Tai
2021-03-18 7:59 ` Andy Tai
2021-03-18 9:03 ` Andy Tai
2021-03-19 8:54 ` Ludovic Courtès
2021-03-19 17:43 ` Andy Tai [this message]
2021-03-29 6:42 ` Andy Tai
2021-04-02 6:55 ` Ludovic Courtès
2021-04-02 7:03 ` bug#46724: " Ludovic Courtès
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='CAJsg1E-yu6jP4zCejD-h60zXayd2QU5fj25AgYHjyvk_aCQX=g@mail.gmail.com' \
--to=atai@atai.org \
--cc=46724@debbugs.gnu.org \
--cc=ludo@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.
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).