From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: LimeSuite-20.10.0
Date: Sat, 21 Aug 2021 03:31:09 +0200 [thread overview]
Message-ID: <20210821013109.p0TExpprmNdohoqsKk7kWN3Caihl5nILvgnT0DuF3ak@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32573@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/32573#issuecomment-901666093
Comment:
### Current issues:
- [x] aarch64 and aarch64-musl fail because LimeSuite's cmake adds `-march=native`, which doesn't work
- [x] all the non-cross builds fail because LimeSuite's shlib isn't being found/resolved even though it's added to common/shlibs
- ~~this was previously resolved locally but has appeared again in the CI~~ locally, it happened when installing LimeSuite; now, it happens with SoapyLMS7 (and can be reproduced locally)
- caused by non-standard soname `libLimeSuite.so.20.10-1`
next prev parent reply other threads:[~2021-08-21 1:31 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 3:33 [PR PATCH] " classabbyamp
2021-08-19 7:09 ` classabbyamp
2021-08-20 2:32 ` classabbyamp
2021-08-21 0:20 ` [PR PATCH] [Updated] " classabbyamp
2021-08-21 0:27 ` classabbyamp
2021-08-21 0:29 ` classabbyamp
2021-08-21 1:23 ` [PR PATCH] [Updated] " classabbyamp
2021-08-21 1:31 ` classabbyamp [this message]
2021-08-21 1:36 ` classabbyamp
2021-08-21 3:05 ` q66
2021-08-21 4:14 ` [PR PATCH] [Updated] " classabbyamp
2021-08-21 4:15 ` classabbyamp
2021-08-21 4:52 ` [PR PATCH] [Updated] " classabbyamp
2021-08-21 11:19 ` q66
2021-08-21 17:08 ` classabbyamp
2021-08-21 17:09 ` classabbyamp
2021-08-21 17:10 ` [PR PATCH] [Updated] " classabbyamp
2021-08-21 17:46 ` q66
2021-08-21 18:31 ` classabbyamp
2021-08-21 18:37 ` classabbyamp
2021-08-21 19:05 ` q66
2021-08-21 19:06 ` q66
2021-08-21 19:08 ` q66
2021-08-22 4:04 ` classabbyamp
2021-08-22 4:04 ` classabbyamp
2021-08-22 7:23 ` q66
2021-08-22 14:45 ` [PR PATCH] [Updated] " classabbyamp
2021-11-05 23:23 ` classabbyamp
2021-11-05 23:27 ` [PR REVIEW] " Duncaen
2021-11-05 23:40 ` [PR PATCH] [Updated] " classabbyamp
2021-11-13 3:40 ` classabbyamp
2021-11-13 3:42 ` [PR REVIEW] " abenson
2021-11-13 3:43 ` abenson
2021-11-13 3:44 ` abenson
2021-11-13 3:47 ` classabbyamp
2021-11-13 3:53 ` classabbyamp
2021-11-13 3:56 ` [PR PATCH] [Updated] " classabbyamp
2021-11-13 4:09 ` [PR REVIEW] " classabbyamp
2021-11-13 4:12 ` classabbyamp
2021-11-13 4:12 ` classabbyamp
2021-11-13 6:06 ` [PR PATCH] [Updated] " classabbyamp
2021-11-13 15:20 ` [PR REVIEW] " abenson
2021-11-13 16:34 ` [PR PATCH] [Updated] " classabbyamp
2021-11-13 16:36 ` [PR REVIEW] " classabbyamp
2022-02-04 18:05 ` [PR PATCH] [Updated] " classabbyamp
2022-03-05 22:47 ` classabbyamp
2022-03-06 3:14 ` classabbyamp
2022-03-22 2:12 ` classabbyamp
2022-03-22 3:55 ` classabbyamp
2022-03-22 3:57 ` classabbyamp
2022-04-02 21:13 ` paper42
2022-04-02 21:33 ` [PR PATCH] [Updated] " classabbyamp
2022-04-02 21:33 ` classabbyamp
2022-04-03 0:06 ` [PR PATCH] [Updated] " classabbyamp
2022-04-03 8:20 ` [PR PATCH] [Merged]: " paper42
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=20210821013109.p0TExpprmNdohoqsKk7kWN3Caihl5nILvgnT0DuF3ak@z \
--to=classabbyamp@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).