From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update mesa
Date: Tue, 26 Sep 2023 02:20:31 +0200 [thread overview]
Message-ID: <20230926002031.f0Z1KfUNVU8OM2JesYPo2XjKQklzuK_laTrmdL3rmRE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46246@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
New comment by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/46246#issuecomment-1734639380
Comment:
mesa hasn't been building 32bit since 23.1.3 afaict https://github.com/void-linux/void-packages/actions/runs/6266633057/job/17018028135?pr=46172
`80-prepare-32bit.sh` got added end of august i think https://github.com/void-linux/void-packages/commit/337d270447d62d4be99cfa062f6e7ac85df25bc3
```
=> mesa-ati-dri-23.1.8_1: running post-install hook: 80-prepare-32bit ...
cp: cannot stat '/destdir//mesa-ati-dri-23.1.8/*': No such file or directory
=> ERROR: mesa-ati-dri-23.1.8_1: post-install_80-prepare-32bit: 'cp -a ${PKGDESTDIR}/* ${destdir32}/' exited with 1
=> ERROR: in hook() at common/hooks/post-install/80-prepare-32bit.sh:64
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:57
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:298
=> ERROR: in main() at common/xbps-src/libexec/xbps-src-doinstall.sh:66
```
next prev parent reply other threads:[~2023-09-26 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 14:14 [ISSUE] " darkralts
2023-09-26 0:20 ` zlice [this message]
2023-10-05 17:02 ` TeusLollo
2023-10-07 9:40 ` SpidFightFR
2023-10-11 0:44 ` TeusLollo
2023-10-11 6:16 ` SpidFightFR
2023-10-11 6:22 ` SpidFightFR
2023-11-02 20:08 ` TeusLollo
2023-11-02 20:11 ` SpidFightFR
2023-11-02 20:16 ` TeusLollo
2023-11-02 20:45 ` TeusLollo
2023-11-02 20:45 ` TeusLollo
2023-11-02 20:54 ` TeusLollo
2023-11-02 21:26 ` TeusLollo
2023-12-07 3:40 ` [ISSUE] [CLOSED] " ahesford
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=20230926002031.f0Z1KfUNVU8OM2JesYPo2XjKQklzuK_laTrmdL3rmRE@z \
--to=zlice@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).