Github messages for voidlinux
 help / color / mirror / Atom feed
From: Sqvid <Sqvid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: btdu: update to 0.5.0.
Date: Fri, 10 Feb 2023 17:11:43 +0100	[thread overview]
Message-ID: <20230210161143.EuD8vvh9bpEaqeJ23Js-WuQq4l1M--NXyfTbVBJkGfU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42148@inbox.vuxu.org>

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

New comment by Sqvid on void-packages repository

https://github.com/void-linux/void-packages/pull/42148#issuecomment-1426029490

Comment:
I would appreciate advice on whether the aarch64 build is possible? [Upstream](https://github.com/CyberShadow/btdu) provides such a build but `xbps-src` seems to fail at the linking stage with the following error:
```
Linking...
[cc-wrapper] ignoring -L/usr/lib
[cc-wrapper] ignoring -L/usr/lib
aarch64-linux-gnu-gcc: error: unrecognized command-line option '-m64'
Error: linker exited with status 1
/usr/bin/dmd failed with exit code 1.
=> ERROR: btdu-0.5.0_1: do_build: 'dub build -b release' exited with 2
=> ERROR:   in do_build() at srcpkgs/btdu/template:19
```
Of course for this attempt I modified the template by commenting out `nocross` and setting `archs="x86_64 aarch64"`.

I would appreciate any advice that might allow us to bring this package to aarch64 users.

  parent reply	other threads:[~2023-02-10 16:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 17:38 [PR PATCH] " Sqvid
2023-02-08 17:43 ` [PR PATCH] [Updated] " Sqvid
2023-02-08 17:46 ` Sqvid
2023-02-08 17:55 ` Sqvid
2023-02-10 16:10 ` Sqvid
2023-02-10 16:11 ` Sqvid
2023-02-10 16:11 ` Sqvid [this message]
2023-02-16  2:43 ` classabbyamp
2023-02-19 15:47 ` CyberShadow
2023-02-19 15:51 ` classabbyamp
2023-02-19 15:51 ` classabbyamp
2023-02-19 15:53 ` CyberShadow
2023-02-19 16:14 ` [PR PATCH] [Updated] " classabbyamp
2023-02-19 16:17 ` classabbyamp
2023-02-19 16:20 ` CyberShadow
2023-02-21 12:53 ` [PR PATCH] [Updated] " Sqvid
2023-02-21 12:57 ` Sqvid
2023-02-21 14:32 ` CyberShadow
2023-03-03 16:52 ` CyberShadow
2023-05-09 15:42 ` [PR PATCH] [Updated] " Sqvid
2023-05-09 15:55 ` Sqvid
2023-05-09 17:57 ` [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=20230210161143.EuD8vvh9bpEaqeJ23Js-WuQq4l1M--NXyfTbVBJkGfU@z \
    --to=sqvid@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).