Github messages for voidlinux
 help / color / mirror / Atom feed
From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Cannot cross-compile libevent for armv5tel-musl
Date: Sun, 24 Jan 2021 02:16:09 +0100	[thread overview]
Message-ID: <20210124011609.i6Qk2LcaKJyr39NpZD7F1jsVo9EqEoiL11tDf8D9qK4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28103@inbox.vuxu.org>

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

Closed issue by lfdebrux on void-packages repository

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

Description:
### System

* xuname:  Void 5.10.8_1 x86_64-musl GenuineIntel/VM notuptodate rF
* package:  libressl-devel, libevent, nghttp2, curl, elfutils, binutils, gcc

### Expected behavior

Running `./xbps-src -a armv5tel-musl libevent` builds and installs `libevent`

### Actual behavior

Build does not start due to issue installing libressl-devel as libssp is missing:

```
=> xbps-src: cleaning up / masterdir...
=> libevent-2.1.12_1: removing autodeps, please wait...
=> libevent-2.1.12_1: removing autocrossdeps, please wait...
=> libevent-2.1.12_1: building [gnu-configure] for armv5tel-musl...
   [target] libressl-devel-3.1.5_2: found (/host/binpkgs)
   [runtime] libressl-devel-3.1.5_2: found (/host/binpkgs)
   [runtime] libevent-2.1.12_1: not found (self, ignored)
=> libevent-2.1.12_1: installing target dependencies: libressl-devel-3.1.5_2 ...
=> libevent-2.1.12_1: removing autodeps, please wait...
=> libevent-2.1.12_1: removing autocrossdeps, please wait...
=> ERROR: libevent-2.1.12_1: failed to install 'libressl-devel-3.1.5_2' dependency! (error 19)
MISSING: libssp>=4.4.0_1
MISSING: libssp>=4.4.0_1
MISSING: libssp>=4.4.0_1
MISSING: libssp>=4.4.0_1
Transaction aborted due to unresolved dependencies.
=> ERROR: Please see above for the real error, exiting...
```

This is particularly annoying because libssp is part of the gcc package, which depends on libevent transitively, so there is a circular dependency. I end up with the same issue trying to build any package in the dependency chain from gcc to libevent.

Strangely however I can build libressl-devel without issues using `./xbs-src -a armv5tel-musl pkg libressl`.

### Steps to reproduce the behavior

On Void Linux x86_64-musl, clone void-packages, install bootstrap and try to build libevent targeting armv5tel-musl. 

  parent reply	other threads:[~2021-01-24  1:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 16:51 [ISSUE] " lfdebrux
2021-01-22 17:12 ` pullmoll
2021-01-22 17:20 ` pullmoll
2021-01-22 17:22 ` pullmoll
2021-01-22 17:26 ` pullmoll
2021-01-22 19:49 ` Johnnynator
2021-01-22 20:11 ` pullmoll
2021-01-22 20:13 ` pullmoll
2021-01-22 20:30 ` q66
2021-01-22 20:34 ` q66
2021-01-22 20:48 ` q66
2021-01-22 20:52 ` q66
2021-01-23 20:49 ` lfdebrux
2021-01-23 22:21 ` lfdebrux
2021-01-23 22:21 ` lfdebrux
2021-01-24  1:16 ` q66 [this message]
2022-02-17  5:11 ` RossComputerGuy
2022-03-26  3:27 ` Xlaits
2022-03-26  3:28 ` Xlaits

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=20210124011609.i6Qk2LcaKJyr39NpZD7F1jsVo9EqEoiL11tDf8D9qK4@z \
    --to=q66@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).