Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
@ 2020-03-24  6:15 mnabid
  2020-03-24  6:25 ` pullmoll
                   ` (23 more replies)
  0 siblings, 24 replies; 25+ messages in thread
From: mnabid @ 2020-03-24  6:15 UTC (permalink / raw)
  To: ml

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

New issue by mnabid on void-packages repository

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

Description:
I was trying to compile nautilus and got the error: 

```
=> ERROR: glib-2.62.5_2: failed to install 'gettext-0.20.1_2' dependency! (error 8)
python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
Transaction aborted due to unresolved shlibs.
```

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
@ 2020-03-24  6:25 ` pullmoll
  2020-03-24  6:30 ` mnabid
                   ` (22 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-24  6:25 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603041872

Comment:
@mnabid Exactly. You'll have to wait until the packages are built:
https://build.voidlinux.org/waterfall
It may take some time because libffi affects a lot of big packages.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
  2020-03-24  6:25 ` pullmoll
@ 2020-03-24  6:30 ` mnabid
  2020-03-25  1:24 ` q66
                   ` (21 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: mnabid @ 2020-03-24  6:30 UTC (permalink / raw)
  To: ml

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

New comment by mnabid on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603043711

Comment:
Guess I'll wait then.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
  2020-03-24  6:25 ` pullmoll
  2020-03-24  6:30 ` mnabid
@ 2020-03-25  1:24 ` q66
  2020-03-25  2:03 ` pullmoll
                   ` (20 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25  1:24 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603588796

Comment:
@pullmoll btw, in order to unstage the musl repo, we'll need a new tarball for `ghc-bin`; do you think you could build one? In order to not repeat this problem, make sure *not* to build it with `--with-system-libffi`, as that's what's causing the whole mess for `x86_64-musl` only; my `ppc64le` tarball does not have the problem, nor do the official bindists.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (2 preceding siblings ...)
  2020-03-25  1:24 ` q66
@ 2020-03-25  2:03 ` pullmoll
  2020-03-25  2:57 ` pullmoll
                   ` (19 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  2:03 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603598447

Comment:
@q66 Sure, I can do that. Is there a description how I build the x86_64-musl ghc-bin tarball?
I read I should "make binary-dist" but where?

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (3 preceding siblings ...)
  2020-03-25  2:03 ` pullmoll
@ 2020-03-25  2:57 ` pullmoll
  2020-03-25  3:09 ` q66
                   ` (18 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  2:57 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603612113

Comment:
FWIW Here's what I think could work:
+ In a x86_64-musl build env extract `bsdtar xvf /host/binpkgs/ghc-bin-8.6.5_1.x86_64.xbps`
+ Create a symlink for a fake `libffi.so.6` with `ln -sf libffi.so.7.1.0 /usr/lib/libffi.so.6`
+ Modify ghc template to **not** depend on `ghc-bin` for the host
+ Also remove the `configure_args="--with-system-libffi"` from the template
+ Add a `make_build_args="binary-dist"` (?)
+ `./xbps-src -m x86_64-musl pkg ghc`
+ Save the resulting tarball (?) somewhere


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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (4 preceding siblings ...)
  2020-03-25  2:57 ` pullmoll
@ 2020-03-25  3:09 ` q66
  2020-03-25  3:10 ` q66
                   ` (17 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25  3:09 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603615110

Comment:
i don't think the glibc build of `ghc` will work in a musl env... you need to take the existing musl `ghc-bin` tarball, extract it in your env, get a `libffi.so.6`, provide it, then build `ghc` with `binary-dist` like you said (having removed `--with-system-libffi`)

as for uploads: normally on `alpha.de.repo.voidlinux.org` in `distfiles` as usual

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (5 preceding siblings ...)
  2020-03-25  3:09 ` q66
@ 2020-03-25  3:10 ` q66
  2020-03-25  3:16 ` pullmoll
                   ` (16 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25  3:10 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603615512

Comment:
i will take care of revbumping `stack` and the other haskell things that need rebuilding, as e.g. `stack` needs build fixes (like always...) and so on, i just need you to provide the bindist, since i can't build that myself (no spare x86_64 machine with enough power)

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (6 preceding siblings ...)
  2020-03-25  3:10 ` q66
@ 2020-03-25  3:16 ` pullmoll
  2020-03-25  3:18 ` pullmoll
                   ` (15 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  3:16 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603612113

Comment:
FWIW Here's what I think could work:
+ In a x86_64-musl build env extract `bsdtar xvf /host/binpkgs/ghc-bin-8.6.5_1.x86_64-musl.xbps`
+ Create a symlink for a fake `libffi.so.6` with `ln -sf libffi.so.7.1.0 /usr/lib/libffi.so.6`
+ Modify ghc template to **not** depend on `ghc-bin` for the host
+ Also remove the `configure_args="--with-system-libffi"` from the template
+ Add a `make_build_args="binary-dist"` (?)
+ `./xbps-src -m x86_64-musl pkg ghc`
+ Save the resulting tarball (?) somewhere


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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (7 preceding siblings ...)
  2020-03-25  3:16 ` pullmoll
@ 2020-03-25  3:18 ` pullmoll
  2020-03-25  3:18 ` pullmoll
                   ` (14 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  3:18 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603617351

Comment:
Oops, I of course extracted the ghc-bin-8.6.5_1.x86_64-musl.xbps and it seems to work so far. Currently running `make all` and will then try what `make binary-dist` gives me.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (8 preceding siblings ...)
  2020-03-25  3:18 ` pullmoll
@ 2020-03-25  3:18 ` pullmoll
  2020-03-25  3:19 ` q66
                   ` (13 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  3:18 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603617351

Comment:
Oops, I of course extracted the `ghc-bin-8.6.5_1.x86_64-musl.xbps` and it seems to work so far. Currently running `make all` and will then try what `make binary-dist` gives me.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (9 preceding siblings ...)
  2020-03-25  3:18 ` pullmoll
@ 2020-03-25  3:19 ` q66
  2020-03-25  3:19 ` pullmoll
                   ` (12 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25  3:19 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603617603

Comment:
alright. Make sure to try building `ghc` with it before we put it somewhere.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (10 preceding siblings ...)
  2020-03-25  3:19 ` q66
@ 2020-03-25  3:19 ` pullmoll
  2020-03-25  4:49 ` pullmoll
                   ` (11 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  3:19 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603617793

Comment:
Yep. I'll upload it to my `https://distfiles.voidlinux.de` and see if it works.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (11 preceding siblings ...)
  2020-03-25  3:19 ` pullmoll
@ 2020-03-25  4:49 ` pullmoll
  2020-03-25  5:08 ` pullmoll
                   ` (10 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  4:49 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603617793

Comment:
Yep. I'll upload it to my `https://distfiles.voidlinux.de` and see if it works.

/me drumming his fingers on the desk...

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (12 preceding siblings ...)
  2020-03-25  4:49 ` pullmoll
@ 2020-03-25  5:08 ` pullmoll
  2020-03-25  6:11 ` pullmoll
                   ` (9 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  5:08 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603643536

Comment:
The first try failed. The [tarball](https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz) is missing lots of files. I'll try again without manually going to the chroot, but rather preparing everything, e.g. need `tar` and `xz` in the host, to finally `make binary-dist` in `post_install()` and copy the result.


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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (13 preceding siblings ...)
  2020-03-25  5:08 ` pullmoll
@ 2020-03-25  6:11 ` pullmoll
  2020-03-25  6:12 ` pullmoll
                   ` (8 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  6:11 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603660088

Comment:
Ok, second try resulted in a much larger tarball with all files it seems:
[https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz](https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz)
Checksum e335578cf199588dbfd5a3c678a4fc0b0d44ec83771a902a01e510b993b3e01e
Building `ghc-bin-8.6.5_2` for `x86_64-musl` worked for me.

I wonder if we should add a `build_option="bindist"` to the `ghc` template to make it easier in the future.

Who's going to update `ghc-bin` or should we wait for someone to put in on `alpha.de.repo.voidlinux.org/distfiles` ?

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (14 preceding siblings ...)
  2020-03-25  6:11 ` pullmoll
@ 2020-03-25  6:12 ` pullmoll
  2020-03-25  9:21 ` pullmoll
                   ` (7 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  6:12 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603660088

Comment:
Ok, second try resulted in a much larger tarball with all files it seems:
[https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz](https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz)
Checksum e335578cf199588dbfd5a3c678a4fc0b0d44ec83771a902a01e510b993b3e01e
Building `ghc-bin-8.6.5_2` for `x86_64-musl` worked for me.

I wonder if we should add a `build_option="bindist"` to the `ghc` template to make it easier in the future.
I also wonder if and how I could create a `ghc-bin` for `i686-musl`.

Who's going to update `ghc-bin` or should we wait for someone to put in on `alpha.de.repo.voidlinux.org/distfiles` ?

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (15 preceding siblings ...)
  2020-03-25  6:12 ` pullmoll
@ 2020-03-25  9:21 ` pullmoll
  2020-03-25 14:08 ` Duncaen
                   ` (6 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: pullmoll @ 2020-03-25  9:21 UTC (permalink / raw)
  To: ml

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

New comment by pullmoll on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603660088

Comment:
Ok, second try resulted in a much larger tarball with all files it seems:
[https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz](https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz)
Checksum e335578cf199588dbfd5a3c678a4fc0b0d44ec83771a902a01e510b993b3e01e
Building `ghc-bin-8.6.5_2` for `x86_64-musl` worked for me.

I wonder if we should add a `build_option="bindist"` to the `ghc` template to make it easier in the future.
I also wonder if and how I could create a `ghc-bin` for `i686-musl`.


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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (16 preceding siblings ...)
  2020-03-25  9:21 ` pullmoll
@ 2020-03-25 14:08 ` Duncaen
  2020-03-25 14:08 ` q66
                   ` (5 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: Duncaen @ 2020-03-25 14:08 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603859880

Comment:
Replaced the previous archive on https://alpha.de.repo.voidlinux.org/distfiles/ with the new one.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (17 preceding siblings ...)
  2020-03-25 14:08 ` Duncaen
@ 2020-03-25 14:08 ` q66
  2020-03-25 22:39 ` Francesco149
                   ` (4 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25 14:08 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-603859886

Comment:
the new tarball is now mirrored, i'll take care of properly bumping all the haskell things...

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (18 preceding siblings ...)
  2020-03-25 14:08 ` q66
@ 2020-03-25 22:39 ` Francesco149
  2020-03-25 22:41 ` q66
                   ` (3 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: Francesco149 @ 2020-03-25 22:39 UTC (permalink / raw)
  To: ml

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

New comment by Francesco149 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-604124260

Comment:
the libffi issues appear to be mostly resolved as a lot of rev bumped packages came through today

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (19 preceding siblings ...)
  2020-03-25 22:39 ` Francesco149
@ 2020-03-25 22:41 ` q66
  2020-03-25 22:41 ` [ISSUE] [CLOSED] " q66
                   ` (2 subsequent siblings)
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25 22:41 UTC (permalink / raw)
  To: ml

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-604124989

Comment:
yeah this is fixed (besides aarch64 builder, which has something wrong with it)

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

* Re: [ISSUE] [CLOSED] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (20 preceding siblings ...)
  2020-03-25 22:41 ` q66
@ 2020-03-25 22:41 ` q66
  2020-03-26  9:40 ` mnabid
  2020-03-26 11:02 ` Duncaen
  23 siblings, 0 replies; 25+ messages in thread
From: q66 @ 2020-03-25 22:41 UTC (permalink / raw)
  To: ml

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

Closed issue by mnabid on void-packages repository

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

Description:
I was trying to compile nautilus and got the error: 

```
=> ERROR: glib-2.62.5_2: failed to install 'gettext-0.20.1_2' dependency! (error 8)
python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
Transaction aborted due to unresolved shlibs.
```
**EDIT:**
libffi update to 3.3 is probably causing this error.

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (21 preceding siblings ...)
  2020-03-25 22:41 ` [ISSUE] [CLOSED] " q66
@ 2020-03-26  9:40 ` mnabid
  2020-03-26 11:02 ` Duncaen
  23 siblings, 0 replies; 25+ messages in thread
From: mnabid @ 2020-03-26  9:40 UTC (permalink / raw)
  To: ml

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

New comment by mnabid on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-604327677

Comment:
Still getting same error for `i686` .

...and another error in `aarch64` and `aarch64-musl`: 
`=> ERROR: libffi-3.3_2: failed to fetch libffi-3.3.tar.gz.` I don't know why. 

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

* Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
  2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
                   ` (22 preceding siblings ...)
  2020-03-26  9:40 ` mnabid
@ 2020-03-26 11:02 ` Duncaen
  23 siblings, 0 replies; 25+ messages in thread
From: Duncaen @ 2020-03-26 11:02 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/20336#issuecomment-604365258

Comment:
i686 should be unstaged now, aarch64 is still catching up.
https://build.voidlinux.org/waterfall

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

end of thread, other threads:[~2020-03-26 11:02 UTC | newest]

Thread overview: 25+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-24  6:15 [ISSUE] python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6' mnabid
2020-03-24  6:25 ` pullmoll
2020-03-24  6:30 ` mnabid
2020-03-25  1:24 ` q66
2020-03-25  2:03 ` pullmoll
2020-03-25  2:57 ` pullmoll
2020-03-25  3:09 ` q66
2020-03-25  3:10 ` q66
2020-03-25  3:16 ` pullmoll
2020-03-25  3:18 ` pullmoll
2020-03-25  3:18 ` pullmoll
2020-03-25  3:19 ` q66
2020-03-25  3:19 ` pullmoll
2020-03-25  4:49 ` pullmoll
2020-03-25  5:08 ` pullmoll
2020-03-25  6:11 ` pullmoll
2020-03-25  6:12 ` pullmoll
2020-03-25  9:21 ` pullmoll
2020-03-25 14:08 ` Duncaen
2020-03-25 14:08 ` q66
2020-03-25 22:39 ` Francesco149
2020-03-25 22:41 ` q66
2020-03-25 22:41 ` [ISSUE] [CLOSED] " q66
2020-03-26  9:40 ` mnabid
2020-03-26 11:02 ` Duncaen

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).