Github messages for voidlinux
 help / color / Atom feed
* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
@ 2019-10-16 17:07 ` voidlinux-github
  2019-10-16 17:18 ` voidlinux-github
                   ` (28 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2019-10-16 17:07 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893

Comment:
For what it's worth, this came up in the [now 404'd](https://github.com/voidlinux/void-packages/issues/7022) original GitHub discussion: there are ways around this headache short of templating. 

What worked for me with the latest [zathura](https://github.com/pwmt/zathura) (namely 0.4.4) was the following procedure:

- got the latest libsynctex [arch package](https://www.archlinux.org/packages/extra/x86_64/libsynctex/)
- untarred it and populated the respective directories as shown in the corresponding [file list](https://www.archlinux.org/packages/extra/x86_64/libsynctex/files/)

That was pretty much it, as far as steps specific to `synctex` go. I then cloned the `zathura` repo, built and installed to a local directory `dir`, say. The `zathura` build system saw the `libsynctex` libraries and built in the `synctex` support as expected. 

I then made an xbps package out of the local installation directory with 

```
# xbps-create -n "zathura-0.4.4_1" -s "document viewer" -A "x86_64" <dir>
```
This will create that package in your `/root/` folder, and you can then install it with 
```
# xdowngrade zathura-0.4.4_1.x86_64.xbps
```
This second part will differ depending on your pdf viewer, but in any case, the first half of this, pertaining to `libsynctex` itself, should work and be fairly easily scriptable.  

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
  2019-10-16 17:07 ` Package request: libsynctex(-devel) voidlinux-github
@ 2019-10-16 17:18 ` voidlinux-github
  2019-10-17 16:14 ` voidlinux-github
                   ` (27 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2019-10-16 17:18 UTC (permalink / raw)
  To: ml

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

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-542803904

Comment:
Rofl nice 👌

El mié., 16 oct. 2019 19:08, stuart-little <notifications@github.com>
escribió:

> For what it's worth, this came up in the now 404'd
> <https://github.com/voidlinux/void-packages/issues/7022> original GitHub
> discussion: there are ways around this headache short of templating.
>
> What worked for me with the latest zathura
> <https://github.com/pwmt/zathura> (namely 0.4.4) was the following
> procedure:
>
>    - got the latest libsynctex arch package
>    <https://www.archlinux.org/packages/extra/x86_64/libsynctex/>
>    - untarred it and populated the respective directories as shown in the
>    corresponding file list
>    <https://www.archlinux.org/packages/extra/x86_64/libsynctex/files/>
>
> That was pretty much it, as far as steps specific to synctex go. I then
> cloned the zathura repo, built and installed to a local directory dir,
> say. The zathura build system saw the libsynctex libraries and built in
> the synctex support as expected.
>
> I then made an xbps package out of the local installation directory with
>
> # xbps-create -n "zathura-0.4.4_1" -s "document viewer" -A "x86_64" <dir>
>
> This will create that package in your /root/ folder, and you can then
> install it with
>
> # xdowngrade zathura-0.4.4_1.x86_64.xbps
>
> This second part will differ depending on your pdf viewer, but in any
> case, the first half of this, pertaining to libsynctex itself, should
> work and be fairly easily scriptable.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/5602?email_source=notifications&email_token=AAGR7KI2HBXFKGUPO6NJLLTQO5C7BA5CNFSM4GJI4BA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBNHQFI#issuecomment-542799893>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGR7KKEXWN4RZR4V734H5LQO5C7BANCNFSM4GJI4BAQ>
> .
>


^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
  2019-10-16 17:07 ` Package request: libsynctex(-devel) voidlinux-github
  2019-10-16 17:18 ` voidlinux-github
@ 2019-10-17 16:14 ` voidlinux-github
  2019-10-17 16:17 ` voidlinux-github
                   ` (26 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2019-10-17 16:14 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-543250009

Comment:
And actually, there's no reason why you wouldn't make your own `xbps` package out of the arch `libsynctex` binary too, for easier package management. I tried it just now:

Once you untar [the archive](https://www.archlinux.org/packages/extra/x86_64/libsynctex/) to some `<dir>` just run
```
# xbps-create -n libsynctex-2019.51075_1 -s "libsynctex" -A x86_64 <dir>
```
and then install the resulting package with `xdowngrade`, as in the [previous post](https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893).

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (2 preceding siblings ...)
  2019-10-17 16:14 ` voidlinux-github
@ 2019-10-17 16:17 ` voidlinux-github
  2019-10-17 16:43 ` voidlinux-github
                   ` (25 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2019-10-17 16:17 UTC (permalink / raw)
  To: ml

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

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-543251184

Comment:
👌

El jue., 17 oct. 2019 18:14, stuart-little <notifications@github.com>
escribió:

> And actually, there's no reason why you wouldn't make your own xbps
> package out of the arch libsynctex binary too, for easier package
> management. I tried it just now:
>
> Once you untar the archive
> <https://www.archlinux.org/packages/extra/x86_64/libsynctex/> to some
> <dir> just run
>
> # xbps-create -n libsynctex-2019.51075_1 -s "libsynctex" -A x86_64 <dir>
>
> and then install the resulting package with xdowngrade, as in the previous
> post
> <https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893>
> .
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/5602?email_source=notifications&email_token=AAGR7KNK5PQFXRODHHUJRH3QPCFOZA5CNFSM4GJI4BA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBQVMWI#issuecomment-543250009>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGR7KO3OHAY3N7ISO6QEBLQPCFOZANCNFSM4GJI4BAQ>
> .
>


^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (3 preceding siblings ...)
  2019-10-17 16:17 ` voidlinux-github
@ 2019-10-17 16:43 ` voidlinux-github
  2020-01-12 12:05 ` voidlinux-github
                   ` (24 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2019-10-17 16:43 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-543250009

Comment:
And actually, there's no reason why you wouldn't make your own `xbps` package out of the arch `libsynctex` binary too, for easier package management. I tried it just now:

Once you untar [the archive](https://www.archlinux.org/packages/extra/x86_64/libsynctex/) to some `<dir>` (so the directory tree structure is `<dir>/usr/...`) just run
```
# xbps-create -n libsynctex-2019.51075_1 -s "libsynctex" -A x86_64 <dir>
```
and then install the resulting package with `xdowngrade`, as in the [previous post](https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893).

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (4 preceding siblings ...)
  2019-10-17 16:43 ` voidlinux-github
@ 2020-01-12 12:05 ` voidlinux-github
  2020-01-12 12:06 ` voidlinux-github
                   ` (23 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 12:05 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573408538

Comment:
> And actually, there's no reason why you wouldn't make your own `xbps` package out of the arch `libsynctex` binary too, for easier package management. I tried it just now:
> 
> Once you untar [the archive](https://www.archlinux.org/packages/extra/x86_64/libsynctex/) to some `<dir>` (so the directory tree structure is `<dir>/usr/...`) just run
> 
> ```
> # xbps-create -n libsynctex-2019.51075_1 -s "libsynctex" -A x86_64 <dir>
> ```
> 
> and then install the resulting package with `xdowngrade`, as in the [previous post](https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893).

I installed libsynctex like you described, then changed the "configure_args" line in the template of zathura to `"-Dsynctex=enabled -Dtest=disabled"`. I also tried to add `libsynctex` to the hostmakedepends or makedepends. I'm getting the following error:
`=> ERROR: zathura-0.4.5_1: target dependency 'libsynctex' does not exist!`

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (5 preceding siblings ...)
  2020-01-12 12:05 ` voidlinux-github
@ 2020-01-12 12:06 ` voidlinux-github
  2020-01-12 13:02 ` voidlinux-github
                   ` (22 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 12:06 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573408538

Comment:
> And actually, there's no reason why you wouldn't make your own `xbps` package out of the arch `libsynctex` binary too, for easier package management. I tried it just now:
> 
> Once you untar [the archive](https://www.archlinux.org/packages/extra/x86_64/libsynctex/) to some `<dir>` (so the directory tree structure is `<dir>/usr/...`) just run
> 
> ```
> # xbps-create -n libsynctex-2019.51075_1 -s "libsynctex" -A x86_64 <dir>
> ```
> 
> and then install the resulting package with `xdowngrade`, as in the [previous post](https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893).

I installed libsynctex like you described, then changed the "configure_args" line in the template of zathura to `"-Dsynctex=enabled -Dtest=disabled"`. I also tried to add `libsynctex` to the hostmakedepends or makedepends. I'm getting the following error while building zathura:
`=> ERROR: zathura-0.4.5_1: target dependency 'libsynctex' does not exist!`


^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (6 preceding siblings ...)
  2020-01-12 12:06 ` voidlinux-github
@ 2020-01-12 13:02 ` voidlinux-github
  2020-01-12 13:02 ` voidlinux-github
                   ` (21 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 13:02 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573413211

Comment:
I wouldn't know what that's about: I am building `zathura` from source too (not through void's template system).

This means I cloned the `zathura` [repo](https://github.com/pwmt/zathura) and followed the build instructions in the `README` therein.

This has worked for me for a long time. In fact, I just built the latest `0.4.5` days ago. I can get back with a precise list of all of the steps I'm taking if you like, but again, this won't be via `void` templating.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (7 preceding siblings ...)
  2020-01-12 13:02 ` voidlinux-github
@ 2020-01-12 13:02 ` voidlinux-github
  2020-01-12 13:04 ` voidlinux-github
                   ` (20 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 13:02 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573413211

Comment:
I wouldn't know what that's about: I am building `zathura` from source too (not through void's template system).

This means I cloned the `zathura` [repo](https://github.com/pwmt/zathura) and followed the build instructions in the `README` therein.

This has worked for me for a long time. In fact, I just built the latest `0.4.5` days ago. I can get back with a more detailed list of all of the steps I'm taking if you like (do ask), but again, this won't be via `void` templating.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (8 preceding siblings ...)
  2020-01-12 13:02 ` voidlinux-github
@ 2020-01-12 13:04 ` voidlinux-github
  2020-01-12 13:09 ` voidlinux-github
                   ` (19 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 13:04 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573413211

Comment:
I wouldn't know what that's about: I am building `zathura` from source too (not through void's template system), as [one of the earlier posts](https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893) says.

This means I cloned the `zathura` [repo](https://github.com/pwmt/zathura) and followed the build instructions in the `README` therein.

This has worked for me for a long time. In fact, I just built the latest `0.4.5` days ago.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (9 preceding siblings ...)
  2020-01-12 13:04 ` voidlinux-github
@ 2020-01-12 13:09 ` voidlinux-github
  2020-01-12 16:09 ` voidlinux-github
                   ` (18 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 13:09 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573413211

Comment:
I wouldn't know what that's about: I am building `zathura` from source too (not through void's template system), as [one of the earlier posts](https://github.com/void-linux/void-packages/issues/5602#issuecomment-542799893) says.

This means I cloned the `zathura` [repo](https://github.com/pwmt/zathura) and followed the build instructions in the `README` therein.

This has worked for me for a long time. In fact, I just built the latest `0.4.5` days ago. I can be more specific about the precise list of steps I'm taking if you like (do ask).

The `void` `zathura` package is useful to me only as a notification mechanism: when `xbps-install -Su` tells me `zathura` has been upgraded I move to my repo clone and redo the build. At no point do I mess with `void` templating.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (10 preceding siblings ...)
  2020-01-12 13:09 ` voidlinux-github
@ 2020-01-12 16:09 ` voidlinux-github
  2020-01-12 16:23 ` voidlinux-github
                   ` (17 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 16:09 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573430202

Comment:
Thank you, i 'd like to take you up on your offer. 
The meson build output currently looks like this:
![image](https://user-images.githubusercontent.com/26022993/72221652-eac0f900-355c-11ea-9ff2-71428262d8f5.png)
From my understanding it looks fine, only libsynctex is missing. As already mentioned, i installed it using xdowngrade. 
`xbps-query libsnctex`-output:
![image](https://user-images.githubusercontent.com/26022993/72221807-4475f300-355e-11ea-8e7c-e5659c5c21be.png)
Thank you for your time.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (11 preceding siblings ...)
  2020-01-12 16:09 ` voidlinux-github
@ 2020-01-12 16:23 ` voidlinux-github
  2020-01-12 16:28 ` voidlinux-github
                   ` (16 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 16:23 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573431676

Comment:
Hmm.. OK, so you have `pkg-config`, which in turn the `meson` build system will use to look for dependencies. Can you find the `pkg-config` file for `libsynctex`? Try something like

```
find /usr/ -name *.pc |grep synctex
```
What does that return? For me it finds 

```
/usr/lib/pkgconfig/synctex.pc
```

I have checked that if I move that file out of the way temporarily, then running

```
meson --prefix /usr build
```
in the root folder of the `zathura` repo will fail to find `synctex`, just as in your case. If I move it back that command *will* find it.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (12 preceding siblings ...)
  2020-01-12 16:23 ` voidlinux-github
@ 2020-01-12 16:28 ` voidlinux-github
  2020-01-12 16:45 ` voidlinux-github
                   ` (15 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 16:28 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573432284

Comment:
Interestingly `find /usr/ -name "*.pc" | grep synctex` returns
/usr/lib/pkgconfig/synctex.pc

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (13 preceding siblings ...)
  2020-01-12 16:28 ` voidlinux-github
@ 2020-01-12 16:45 ` voidlinux-github
  2020-01-12 16:51 ` voidlinux-github
                   ` (14 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 16:45 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573432284

Comment:
Interestingly `find /usr/ -name "*.pc" | grep synctex` returns
/usr/lib/pkgconfig/synctex.pc

Addition: I forgot to mention: I'm on void-musl, as mentioned in this blog post https://blog.w1r3.net/2017/09/23/live-switching-void-linux-from-glibc-to-musl.html .

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (14 preceding siblings ...)
  2020-01-12 16:45 ` voidlinux-github
@ 2020-01-12 16:51 ` voidlinux-github
  2020-01-12 16:52 ` voidlinux-github
                   ` (13 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 16:51 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573434442

Comment:
I'm a bit stumped, but perhaps the `prefix` option might have something to do with it?

I notice your package-finding executables (`cmake`, `pkg-config`) are directly in `/bin/`. For me they're in `/usr/bin/`.

Maybe run 

```
meson --prefix /usr build
```
specifying the `prefix`?

On my system `/bin/` is a symlink to `/usr/bin/`, but the `meson` system actually resolves the path to `pkg-config` to the full `/usr`-prefixed directory, so there's clearly some such difference between our two systems..


^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (15 preceding siblings ...)
  2020-01-12 16:51 ` voidlinux-github
@ 2020-01-12 16:52 ` voidlinux-github
  2020-01-12 17:29 ` voidlinux-github
                   ` (12 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 16:52 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573434442

Comment:
I'm a bit stumped, but perhaps the `prefix` option might have something to do with it?

I notice your package-finding executables (`cmake`, `pkg-config`) are directly in `/bin/`. For me they're in `/usr/bin/`.

Maybe run 

```
meson --prefix /usr build
```
specifying the `prefix`?

On my system `/bin/` is a symlink to `/usr/bin/`, but the `meson` system actually resolves the path to `pkg-config` to the full `/usr`-prefixed directory, so there's clearly some such difference between our two systems..

---
**Edit:**

I'm on `glibc` myself, and have no clue how that might affect things.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (16 preceding siblings ...)
  2020-01-12 16:52 ` voidlinux-github
@ 2020-01-12 17:29 ` voidlinux-github
  2020-01-12 17:30 ` voidlinux-github
                   ` (11 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 17:29 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573437877

Comment:
I've also just tried this:

- moved 'synctex.pc' to some random directory I made up (say '/boo');

- set the `PKG_CONFIG_PATH` environment variable to that directory:

```
export PKG_CONFIG_PATH=/boo
```

- ran the `meson` command as before:

```
meson --prefix /usr build
```
It find `synctex`! So you can add directories to whatever search path is already built into `meson` for `pkg-config`. In your case maybe try something like

```
export PKG_CONFIG_PATH=/usr/lib/pkgconfig
```
before running the `meson` command.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (17 preceding siblings ...)
  2020-01-12 17:29 ` voidlinux-github
@ 2020-01-12 17:30 ` voidlinux-github
  2020-01-12 17:32 ` voidlinux-github
                   ` (10 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 17:30 UTC (permalink / raw)
  To: ml

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

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573437976

Comment:
Right, but pkgconfig files should always go to `/usr/lib/pkgconfig/`

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (18 preceding siblings ...)
  2020-01-12 17:30 ` voidlinux-github
@ 2020-01-12 17:32 ` voidlinux-github
  2020-01-12 20:37 ` voidlinux-github
                   ` (9 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 17:32 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573438132

Comment:
Certainly, but in this case that file is not found for some reason. I'm grasping at straws anyway, so was just suggesting something concrete to try.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (19 preceding siblings ...)
  2020-01-12 17:32 ` voidlinux-github
@ 2020-01-12 20:37 ` voidlinux-github
  2020-01-12 23:14 ` voidlinux-github
                   ` (8 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 20:37 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573454693

Comment:
So this might be barking up the wrong tree, but here's what I suspect happened.

The fact that `meson` locates executables in `/bin/` rather than `/usr/bin/` makes me think that perhaps on this system (`musl` vs. `glibc`?) these are built with `--prefix=""` instead of `--prefix=/usr`.

This would apply to `pkg-config`, which would then presumably be configured to search `/lib/` but not `/usr/lib`. Similarly, all other packages would install their respective `*.pc` files to `/lib/pkgconfig` instead of `/usr/lib/pkgconfig`.

This custom-made `synctex` package borrowed from `arch`, though, installs *its* `*.pc` file in `/usr/lib/pkgconfig`, where the system's `pkg-config` doesn't know to look for it.

For that reason, you might want to help `pkg-config` out as suggested, by running 

```
export PKG_CONFIG_PATH=/usr/lib/pkgconfig
```
I may well be off-track, but we won't know until @l4s8g gives it a go.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (20 preceding siblings ...)
  2020-01-12 20:37 ` voidlinux-github
@ 2020-01-12 23:14 ` voidlinux-github
  2020-01-12 23:16 ` voidlinux-github
                   ` (7 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 23:14 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573468634

Comment:
Thank you guys, lots of permission issues, yet again. libsynctex.pc was not readable by group and others. I then installed zathura-pdf-mupdf using `sudo xbps-install zathura-pdf-mupdf`. Again, a folder had wrong permissions so i could not display the pdf files. I had to change permissions of the file /usr/local/lib/zathura/libpdf-mupdf.so and of the folder containing this file. Are these permission issues specific to my setup? I would be happy to investigate and help out to contribute something back. 

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (21 preceding siblings ...)
  2020-01-12 23:14 ` voidlinux-github
@ 2020-01-12 23:16 ` voidlinux-github
  2020-01-12 23:23 ` voidlinux-github
                   ` (6 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 23:16 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573468634

Comment:
Thank you guys, lots of permission issues, yet again. libsynctex.pc was not readable by group and others. I then installed zathura-pdf-mupdf using `sudo xbps-install zathura-pdf-mupdf`. Again, i experienced  permissions issues so i could not display the pdf files. I had to change permissions of the file /usr/local/lib/zathura/libpdf-mupdf.so and of the folder containing this file. Are these permission issues specific to my setup? I would be happy to investigate and help out to contribute something back. 

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (22 preceding siblings ...)
  2020-01-12 23:16 ` voidlinux-github
@ 2020-01-12 23:23 ` voidlinux-github
  2020-01-12 23:25 ` voidlinux-github
                   ` (5 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 23:23 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573469436

Comment:
Is it `libsynctex.pc` or just plain `synctex.pc`? It's the latter for me..

Does `meson` find it if you make it readable by everyone? 

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (23 preceding siblings ...)
  2020-01-12 23:23 ` voidlinux-github
@ 2020-01-12 23:25 ` voidlinux-github
  2020-01-13  0:34 ` voidlinux-github
                   ` (4 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-12 23:25 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573469436

Comment:
Is it `libsynctex.pc` or just plain `synctex.pc`? It's the latter for me..

Does `meson` find it if you make it readable by everyone? 

**Edit:**

Oh, and about this:

> Are these permission issues specific to my setup?

All of my `/usr/lib/*.pc` files have `644` permissions, so are universally readable.


^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (24 preceding siblings ...)
  2020-01-12 23:25 ` voidlinux-github
@ 2020-01-13  0:34 ` voidlinux-github
  2020-01-13 10:52 ` voidlinux-github
                   ` (3 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-13  0:34 UTC (permalink / raw)
  To: ml

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

New comment by stuart-little on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573469436

Comment:
Is it `libsynctex.pc` or just plain `synctex.pc`? It's the latter for me..

Does `meson` find it if you make it readable by everyone? 

**Edit:**

Oh, and about this:

> Are these permission issues specific to my setup?

All of my `/usr/lib/*.pc` files have `644` permissions, so are universally readable.

I've also checked that if I remove the read bit from `/usr/lib/pkgconfig/synctex.pc` then `meson` no longer finds it.


^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (25 preceding siblings ...)
  2020-01-13  0:34 ` voidlinux-github
@ 2020-01-13 10:52 ` voidlinux-github
  2020-01-13 10:52 ` voidlinux-github
                   ` (2 subsequent siblings)
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-13 10:52 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573605841

Comment:
I'm sorry, i guess i wasn't clear in my last comment, i got zathura working with forward and backward search now., after changing the permissions of the files. These permission problems are really bugging me though and i haven't experienced anything like this before. That's why i asked if others also experience permission issues. 

> Is it libsynctex.pc or just plain synctex.pc? It's the latter for me..
-> synctex.pc
> All of my /usr/lib/*.pc files have 644 permissions, so are universally readable.
I have to set 644 permissions myself for new .pc files. Also for new folders.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (26 preceding siblings ...)
  2020-01-13 10:52 ` voidlinux-github
@ 2020-01-13 10:52 ` voidlinux-github
  2020-01-13 10:53 ` voidlinux-github
  2020-01-13 18:12 ` voidlinux-github
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-13 10:52 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573605841

Comment:
I'm sorry, i guess i wasn't clear in my last comment, i got zathura working with forward and backward search now., after changing the permissions of the files. These permission problems are really bugging me though and i haven't experienced anything like this before. That's why i asked if others also experience permission issues. 

> Is it libsynctex.pc or just plain synctex.pc? It's the latter for me..

-> synctex.pc

> All of my /usr/lib/*.pc files have 644 permissions, so are universally readable.

I have to set 644 permissions myself for new .pc files. Also for new folders.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (27 preceding siblings ...)
  2020-01-13 10:52 ` voidlinux-github
@ 2020-01-13 10:53 ` voidlinux-github
  2020-01-13 18:12 ` voidlinux-github
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-13 10:53 UTC (permalink / raw)
  To: ml

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

New comment by l4s8g on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573605841

Comment:
I'm sorry, i guess i wasn't clear in my last comment, i got zathura working with forward and backward search now., after changing the permissions of the files and folders. These permission problems are really bugging me though and i haven't experienced anything like this before. That's why i asked if others also experience permission issues. 

> Is it libsynctex.pc or just plain synctex.pc? It's the latter for me..

-> synctex.pc

> All of my /usr/lib/*.pc files have 644 permissions, so are universally readable.

I have to set 644 permissions myself for new .pc files. Also for new folders.

^ permalink raw reply	[flat|nested] 30+ messages in thread

* Re: Package request: libsynctex(-devel)
       [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
                   ` (28 preceding siblings ...)
  2020-01-13 10:53 ` voidlinux-github
@ 2020-01-13 18:12 ` voidlinux-github
  29 siblings, 0 replies; 30+ messages in thread
From: voidlinux-github @ 2020-01-13 18:12 UTC (permalink / raw)
  To: ml

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

New comment by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/5602#issuecomment-573796366

Comment:
Folders typically need exec permissions as well, e.g. 755 here

^ permalink raw reply	[flat|nested] 30+ messages in thread

end of thread, back to index

Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5602@inbox.vuxu.org>
2019-10-16 17:07 ` Package request: libsynctex(-devel) voidlinux-github
2019-10-16 17:18 ` voidlinux-github
2019-10-17 16:14 ` voidlinux-github
2019-10-17 16:17 ` voidlinux-github
2019-10-17 16:43 ` voidlinux-github
2020-01-12 12:05 ` voidlinux-github
2020-01-12 12:06 ` voidlinux-github
2020-01-12 13:02 ` voidlinux-github
2020-01-12 13:02 ` voidlinux-github
2020-01-12 13:04 ` voidlinux-github
2020-01-12 13:09 ` voidlinux-github
2020-01-12 16:09 ` voidlinux-github
2020-01-12 16:23 ` voidlinux-github
2020-01-12 16:28 ` voidlinux-github
2020-01-12 16:45 ` voidlinux-github
2020-01-12 16:51 ` voidlinux-github
2020-01-12 16:52 ` voidlinux-github
2020-01-12 17:29 ` voidlinux-github
2020-01-12 17:30 ` voidlinux-github
2020-01-12 17:32 ` voidlinux-github
2020-01-12 20:37 ` voidlinux-github
2020-01-12 23:14 ` voidlinux-github
2020-01-12 23:16 ` voidlinux-github
2020-01-12 23:23 ` voidlinux-github
2020-01-12 23:25 ` voidlinux-github
2020-01-13  0:34 ` voidlinux-github
2020-01-13 10:52 ` voidlinux-github
2020-01-13 10:52 ` voidlinux-github
2020-01-13 10:53 ` voidlinux-github
2020-01-13 18:12 ` voidlinux-github

Github messages for voidlinux

Archives are clonable: git clone --mirror http://inbox.vuxu.org/voidlinux-github

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.github.voidlinux


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git