From: rantlivelintkale <rantlivelintkale@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ardour: update to 7.0.
Date: Mon, 24 Oct 2022 10:17:24 +0200 [thread overview]
Message-ID: <20221024081724.XvJYkUJQ6Tto3VYfue-EoqK5igXXCly_vHI4J633-g4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40054@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
New comment by rantlivelintkale on void-packages repository
https://github.com/void-linux/void-packages/pull/40054#issuecomment-1288609029
Comment:
```
2022-10-23T02:14:07.9145074Z [1103/1148] Linking build/gtk2_ardour/ardour-7.0.0
2022-10-23T02:14:08.7255634Z /usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: gtk2_ardour/audio_clock.cc.1.o: undefined reference to symbol '__atomic_compare_exchange_8'
2022-10-23T02:14:08.7256544Z /usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: /usr/arm-linux-musleabihf/lib/libatomic.so.1: error adding symbols: DSO missing from command line
2022-10-23T02:14:08.7257064Z collect2: error: ld returned 1 exit status
```
I assume that's why the armv6l-musl failed, I'll try building it locally as well.
The lint complains about the `PATH` variable not being prefixed, but I assume that it should not be prefixed since it is the `PATH` variable.
next prev parent reply other threads:[~2022-10-24 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 8:15 [PR PATCH] " rantlivelintkale
2022-10-23 1:21 ` classabbyamp
2022-10-24 8:17 ` rantlivelintkale [this message]
2022-10-31 9:32 ` rantlivelintkale
2022-10-31 15:26 ` classabbyamp
2022-11-01 18:10 ` [PR PATCH] [Updated] " rantlivelintkale
2022-11-01 18:13 ` rantlivelintkale
2022-11-01 20:24 ` [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=20221024081724.XvJYkUJQ6Tto3VYfue-EoqK5igXXCly_vHI4J633-g4@z \
--to=rantlivelintkale@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).