From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] FTBFS: gmic
Date: Thu, 14 Oct 2021 06:15:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33534@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
New issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/33534
Description:
The `gmic` package fails to build from source. Attempting to update to a newer version in the `2.8.x` series produces similar errors, while attempting to update to the latest `2.9.9` causes other failures. The initial failure is documented in the log [gmic.build01.log](https://github.com/void-linux/void-packages/files/7342918/gmic.build01.log)
After the first failure, the file `gmic-2.8.0/src/use_libgmic.cpp` can be patched to uncomment the following two lines near the top of the file:
```c++
#include "CImg.h"
using namespace cimg_library;
```
The `use_libgmic` target will compile succesfully, but build failures appear when building the gimp plugin. The later failure is documented in the log [gmic.build02.log](https://github.com/void-linux/void-packages/files/7342919/gmic.build02.log).
The errors appear when compiling with `python3-3.10.0_1` and `opencv-3.4.15_1` currently in the repo. However, I also reverted to commit e7ca6798247, and the build also fails with `python3-3.9.7_1` and `opencv-3.4.10_2`. Note that, to test this, I had to grab an old version of the `opencv` packages from the repo, because `opencv-3.4.10` also fails to build from source. (The error in `opencv` seems to be related to JPEG-2000.)
next reply other threads:[~2021-10-14 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 4:15 ahesford [this message]
2021-10-14 16:59 ` newbluemoon
2021-12-22 16:39 ` [ISSUE] [CLOSED] " ahesford
2021-12-22 16:39 ` ahesford
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33534@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).