* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
@ 2021-04-22 22:16 ` ericonr
2021-04-25 9:26 ` jcgruenhage
` (5 subsequent siblings)
6 siblings, 0 replies; 7+ messages in thread
From: ericonr @ 2021-04-22 22:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 217 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-825218762
Comment:
Needs `libatomic-devel` and `LDFLAGS=-latomic` for `XBPS_TARGET_NO_ATOMIC8`.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
2021-04-22 22:16 ` cargo-about: update to 0.3.0 ericonr
@ 2021-04-25 9:26 ` jcgruenhage
2021-04-25 9:38 ` jcgruenhage
` (4 subsequent siblings)
6 siblings, 0 replies; 7+ messages in thread
From: jcgruenhage @ 2021-04-25 9:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-826290617
Comment:
> Needs `libatomic-devel` and `LDFLAGS=-latomic` for `XBPS_TARGET_NO_ATOMIC8`.
@ericonr how did you figure that out? The failed build doesn't show any logs for me for some reason, so I couldn't see where it failed..
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
2021-04-22 22:16 ` cargo-about: update to 0.3.0 ericonr
2021-04-25 9:26 ` jcgruenhage
@ 2021-04-25 9:38 ` jcgruenhage
2021-04-25 15:34 ` ericonr
` (3 subsequent siblings)
6 siblings, 0 replies; 7+ messages in thread
From: jcgruenhage @ 2021-04-25 9:38 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 180 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-826292363
Comment:
Oh, it still errors on armv6-musl..
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
` (2 preceding siblings ...)
2021-04-25 9:38 ` jcgruenhage
@ 2021-04-25 15:34 ` ericonr
2021-07-04 23:36 ` ericonr
` (2 subsequent siblings)
6 siblings, 0 replies; 7+ messages in thread
From: ericonr @ 2021-04-25 15:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2899 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-826343499
Comment:
```
stats.c:(.text.mi_stat_update.part.0+0xcc): undefined reference to `__atomic_fetch_add_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_update.part.0+0xe8): undefined reference to `__atomic_load_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_update.part.0+0x11c): undefined reference to `__atomic_compare_exchange_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_update.part.0+0x14c): undefined reference to `__atomic_fetch_add_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_update.part.0+0x16c): undefined reference to `__atomic_fetch_add_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: /builddir/cargo-about-0.3.0/target/arm-unknown-linux-musleabihf/release/deps/liblibmimalloc_sys-707880f4e08a2449.rlib(stats.o): in function `mi_stat_add.constprop.0':
stats.c:(.text.mi_stat_add.constprop.0+0x48): undefined reference to `__atomic_fetch_add_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_add.constprop.0+0x58): undefined reference to `__atomic_fetch_add_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_add.constprop.0+0x68): undefined reference to `__atomic_fetch_add_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: /builddir/cargo-about-0.3.0/target/arm-unknown-linux-musleabihf/release/deps/liblibmimalloc_sys-707880f4e08a2449.rlib(stats.o):stats.c:(.text.mi_stat_add.constprop.0+0x78): more undefined references to `__atomic_fetch_add_8' follow
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: /builddir/cargo-about-0.3.0/target/arm-unknown-linux-musleabihf/release/deps/liblibmimalloc_sys-707880f4e08a2449.rlib(stats.o): in function `mi_stat_process_info':
stats.c:(.text.mi_stat_process_info+0xb4): undefined reference to `__atomic_load_8'
/usr/lib/gcc/arm-linux-musleabihf/10.2.1/../../../../arm-linux-musleabihf/bin/ld: stats.c:(.text.mi_stat_process_info+0xc8): undefined reference to `__atomic_load_8'
collect2: error: ld returned 1 exit status
error: aborting due to previous error
error: could not compile `cargo-about`
To learn more, run the command again with --verbose.
=> ERROR: cargo-about-0.3.0_1: do_build: '${make_cmd} build --release --target ${RUST_TARGET} ${configure_args}' exited with 101
```
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
` (3 preceding siblings ...)
2021-04-25 15:34 ` ericonr
@ 2021-07-04 23:36 ` ericonr
2021-08-11 21:11 ` jcgruenhage
2021-08-11 23:12 ` ericonr
6 siblings, 0 replies; 7+ messages in thread
From: ericonr @ 2021-07-04 23:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-873685814
Comment:
Ping
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
` (4 preceding siblings ...)
2021-07-04 23:36 ` ericonr
@ 2021-08-11 21:11 ` jcgruenhage
2021-08-11 23:12 ` ericonr
6 siblings, 0 replies; 7+ messages in thread
From: jcgruenhage @ 2021-08-11 21:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-897157661
Comment:
I can't seem to figure this out, sorry.. I don't think `LDFLAGS` is respected in the cargo build-style, and my attempts to pass `-latomic` to `ld` with a `.cargo/config.toml` seem to all fail. Any hints how to tackle this?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: cargo-about: update to 0.3.0.
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30324@inbox.vuxu.org>
` (5 preceding siblings ...)
2021-08-11 21:11 ` jcgruenhage
@ 2021-08-11 23:12 ` ericonr
6 siblings, 0 replies; 7+ messages in thread
From: ericonr @ 2021-08-11 23:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30324#issuecomment-897220755
Comment:
There's a neat workaround called `broken="can't be made to link libatomic"` :p
You can also inspect the code to try and find the place where it's unnecessarily using 64-bit atomics instead of `usize` atomics.
^ permalink raw reply [flat|nested] 7+ messages in thread