Github messages for voidlinux
 help / color / mirror / Atom feed
From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: QGIS
Date: Sun, 24 Sep 2023 17:02:40 +0200	[thread overview]
Message-ID: <20230924150240.9feFYYp3KhSRLmbumh2x3O6mm7hdTx_4NqfjHAU2oqI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41812@inbox.vuxu.org>

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

New comment by ar-jan on void-packages repository

https://github.com/void-linux/void-packages/pull/41812#issuecomment-1732591052

Comment:
I'm stuck. I've changed it to install to `/usr/lib/grass83`. I'm not quite sure why `/opt` was picked, but before that it was already strange to first install to `/usr/share` and then move the whole install dir to `/usr/lib` anyway. Grass has `--includedir=DIR` and `--libdir=DIR` options but I couldn't get those options to work, setting it to e.g. `--includedir=/usr/include` appears to do nothing.

The library paths for `grass.pc` had to be fixed, but I'm still getting the `unresolvable shlib` problem. Grass compile and install appears to work fine. QGIS can be compiled with grass and the configure phase reports finding grass, but then when actually installing qgis the grass libraries can't be found (if I remove grass-devel from qgis makedepends it can be installed).

If I compile QGIS with grass-devel in makedepends, it starts like this:
> ./xbps-src pkg -C qgis
> Package grass was not found in the pkg-config search path.
> Perhaps you should add the directory containing `grass.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'grass' found

But despite that, qgis__do_configure.log then says:
> -- Found GRASS 8: /usr/lib/grass83 (8.3.0, off_t size = )

(Maybe because of passing setting the location with configure arg `GRASS_PREFIX8`?)

When I install the grass-devel built in that same branch, I get this when testing:

> pkg-config --variable=prefix grass
> /usr/lib/grass83

While without `grass-devel` installed, I get the same `PKG_CONFIG_PATH` warning.

So the issue seems to come from pkg-config? Anyone want to try building it and see if they spot what's happening?

`https://github.com/ar-jan/void-packages/tree/qgis-proj`

  parent reply	other threads:[~2023-09-24 15:02 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 21:21 [PR PATCH] Qgis ar-jan
2023-01-28 20:33 ` [PR PATCH] [Updated] New package: qgis-3.28.2 ar-jan
2023-01-28 20:34 ` ar-jan
2023-01-28 20:43 ` ar-jan
2023-01-28 22:28 ` [PR PATCH] [Updated] New package: qgis-3.28.3 ar-jan
2023-04-18 19:47 ` ar-jan
2023-04-18 19:59 ` [PR PATCH] [Updated] New package: QGIS ar-jan
2023-04-29 15:26 ` ar-jan
2023-04-29 15:29 ` ar-jan
2023-04-29 15:30 ` ar-jan
2023-05-12 23:46 ` cinerion
2023-05-13  7:42 ` ar-jan
2023-06-20  8:22 ` ar-jan
2023-06-24 13:10 ` [PR PATCH] [Updated] " ar-jan
2023-06-24 13:11 ` ar-jan
2023-07-23  8:22 ` [PR PATCH] [Updated] " ar-jan
2023-07-23  8:22 ` ar-jan
2023-07-25  8:12 ` [PR PATCH] [Updated] " ar-jan
2023-07-28  0:40 ` classabbyamp
2023-07-28 12:40 ` ar-jan
2023-07-28 12:41 ` ar-jan
2023-07-28 12:45 ` ar-jan
2023-07-28 12:48 ` classabbyamp
2023-07-28 20:41 ` ar-jan
2023-07-28 20:50 ` classabbyamp
2023-07-28 21:04 ` ar-jan
2023-07-30 13:59 ` nezos
2023-07-30 14:01 ` nezos
2023-07-31 14:44 ` ar-jan
2023-07-31 14:44 ` ar-jan
2023-09-19 22:15 ` ar-jan
2023-09-19 22:16 ` ar-jan
2023-09-20  8:23 ` 0x5c
2023-09-20 14:13 ` ar-jan
2023-09-20 14:58 ` 0x5c
2023-09-20 15:19 ` 0x5c
2023-09-24 14:56 ` ar-jan
2023-09-24 15:02 ` ar-jan [this message]
2023-09-27  6:44 ` classabbyamp
2023-09-27  6:44 ` classabbyamp
2023-09-27 16:45 ` ar-jan
2023-09-27 22:18 ` [PR PATCH] [Updated] " ar-jan
2023-09-27 22:41 ` [PR REVIEW] " classabbyamp
2023-09-28 17:44 ` [PR PATCH] [Updated] " ar-jan
2023-09-28 17:45 ` [PR REVIEW] " ar-jan
2023-09-28 17:56 ` ar-jan
2023-09-28 17:57 ` ar-jan
2023-09-29  4:58 ` nezos
2023-09-29  5:01 ` nezos
2023-09-29  7:28 ` ar-jan
2023-09-30  4:27 ` nezos
2023-09-30  4:27 ` nezos
2023-11-01 20:30 ` nezos
2023-11-01 20:38 ` ar-jan
2023-11-01 20:39 ` ar-jan
2023-11-04  9:37 ` nezos
2023-11-12 19:36 ` [PR PATCH] [Updated] " ar-jan
2023-11-12 19:41 ` ar-jan
2023-11-12 21:10 ` ar-jan
2023-11-12 21:15 ` ar-jan
2023-11-12 21:48 ` [PR PATCH] [Updated] " ar-jan
2023-11-14  7:09 ` [PR REVIEW] " classabbyamp
2023-11-14  7:09 ` classabbyamp
2023-11-14  7:09 ` classabbyamp
2023-11-14  7:09 ` classabbyamp
2023-11-14  7:09 ` classabbyamp
2023-11-14 12:17 ` ar-jan
2023-11-14 12:37 ` ar-jan
2023-11-14 12:39 ` ar-jan
2023-11-14 12:41 ` ar-jan
2023-11-14 13:50 ` classabbyamp
2023-11-14 13:50 ` classabbyamp
2023-11-14 18:28 ` ar-jan
2023-11-14 18:30 ` ar-jan
2023-11-14 18:46 ` [PR PATCH] [Updated] " ar-jan
2023-11-14 18:47 ` ar-jan
2023-11-14 19:04 ` ar-jan
2023-11-14 21:10 ` ar-jan
2023-11-15 17:49 ` [PR REVIEW] " classabbyamp
2023-11-15 17:49 ` classabbyamp
2023-11-15 18:16 ` classabbyamp
2023-11-15 18:16 ` classabbyamp
2023-11-15 22:41 ` [PR PATCH] [Updated] " ar-jan
2023-11-16 20:26 ` [PR PATCH] [Merged]: " classabbyamp

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=20230924150240.9feFYYp3KhSRLmbumh2x3O6mm7hdTx_4NqfjHAU2oqI@z \
    --to=ar-jan@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).