From: MechDR <MechDR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: amarok
Date: Thu, 16 May 2024 09:20:46 +0200 [thread overview]
Message-ID: <20240516072046.088952629A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49953@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
New comment by MechDR on void-packages repository
https://github.com/void-linux/void-packages/issues/49953#issuecomment-2114252513
Comment:
The functions were just for testing, the final was supposed to have just `build_style=cmake`, `configure_args` and `build_wrksrc`, but the `build_wrksrc` didn't get parsed by xbps-src (or maybe I didn't define it properly, IDK), so I just thought I'd try and see if it can build like this, then clean up the template and just use the built in variables.
It actually does make the `/usr/etc` dir when installing, but I just moved it to the root of `$DESTDIR` (as it should be).
The building is not the actual problem, it builds without problems on x86_64 (needs a bit more work for cross), the problem is, it won't run, lol 😄.
next prev parent reply other threads:[~2024-05-16 7:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 9:58 [ISSUE] " Eloitor
2024-04-23 11:24 ` MechDR
2024-04-23 11:38 ` Eloitor
2024-04-23 14:09 ` MechDR
2024-05-03 7:20 ` mvf
2024-05-08 22:08 ` MechDR
2024-05-15 13:09 ` MechDR
2024-05-16 7:09 ` mvf
2024-05-16 7:20 ` MechDR [this message]
2024-05-16 7:22 ` MechDR
2024-05-16 7:38 ` mvf
2024-05-16 16:30 ` MechDR
2024-05-20 23:28 ` MechDR
2024-05-24 22:33 ` MechDR
2024-05-24 22:33 ` MechDR
2024-05-24 22:42 ` MechDR
2024-05-24 23:55 ` MechDR
2024-05-25 0:00 ` MechDR
2024-05-25 0:09 ` MechDR
2024-05-25 0:12 ` MechDR
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=20240516072046.088952629A@inbox.vuxu.org \
--to=mechdr@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).