Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [FTBFS] cross compiling poppler broken (broken libopenjpeg2 cmake file?)
Date: Mon, 25 Jan 2021 22:55:15 +0100	[thread overview]
Message-ID: <20210125215515.idIiQXim4fy-W5H3aidmH-Bw1rCmrfLeK8WBJCOybp4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28219@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

Closed issue by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/issues/28219

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
* package:  
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``

### Expected behavior
`./xbps-src -t poppler -a aarch64` to succeed

### Actual behavior

```
/builddir/poppler-20.09.0/poppler/JPEG2000Stream.cc:20:10: fatal error: openjpeg.h: No such file or directory
   20 | #include <openjpeg.h>
      |          ^~~~~~~~~~~~
```

Would expect this line in `usr/lib/openjpeg-2.4/OpenJPEGConfig.cmake` to be the problem
```cmake
  set(INC_DIR "/usr/include/openjpeg-2.4")
```

### Steps to reproduce the behavior



  parent reply	other threads:[~2021-01-25 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 14:33 [ISSUE] " Johnnynator
2021-01-25 21:55 ` Johnnynator
2021-01-25 21:55 ` Johnnynator [this message]
2021-01-25 21:55 ` Johnnynator

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=20210125215515.idIiQXim4fy-W5H3aidmH-Bw1rCmrfLeK8WBJCOybp4@z \
    --to=johnnynator@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).