From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: scons: update to 4.7.0
Date: Sun, 31 Mar 2024 03:22:49 +0200 [thread overview]
Message-ID: <20240331012249.7763F26728@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49596@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
New comment by wpbirney on void-packages repository
https://github.com/void-linux/void-packages/pull/49596#issuecomment-2028083719
Comment:
> Did you try recompile all packages that use `scons`?
I have not yet, but i will now to be sure
- [x] godot
- [x] goxel
- [x] gpsd
- [x] libffado
- [x] pingus - 77d36c47c3faf56b12f52855dfe0cb5b7390d57d
- [x] rmlint
- [x] serf
- [x] vdrift
- [x] xboxdrv a6c1b46d0eeb0d5a52a118bfc5055ff685029cfc
- [x] endless-sky-gl21 - compile errors with both scons 4.4 and the PR 4.7
- [x] cbang - b50b3e2d16c18ec9c8d42b1c922077263e54809d
- [x] sunpinyin
SCons 4.7.0 update didn't break any packages using build_style=scons
Both `pingus` and `xboxdrv` have gitlab distfiles that 404 currently.
`endless-sky-gl21` and `cbang` have compile errors regardless of which scons version is used.
next prev parent reply other threads:[~2024-03-31 1:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 21:13 [PR PATCH] scons: Update " wpbirney
2024-03-30 9:43 ` scons: update " sgn
2024-03-30 14:14 ` wpbirney
2024-03-30 14:20 ` wpbirney
2024-03-30 14:21 ` wpbirney
2024-03-30 14:22 ` wpbirney
2024-03-30 14:24 ` wpbirney
2024-03-30 14:25 ` wpbirney
2024-03-30 14:26 ` wpbirney
2024-03-30 14:28 ` wpbirney
2024-03-30 14:32 ` wpbirney
2024-03-30 14:32 ` wpbirney
2024-03-30 14:32 ` wpbirney
2024-03-30 14:34 ` wpbirney
2024-03-30 14:43 ` wpbirney
2024-03-30 23:38 ` sgn
2024-03-31 1:02 ` sgn
2024-03-31 1:18 ` sgn
2024-03-31 1:22 ` sgn [this message]
2024-03-31 1:22 ` [PR PATCH] [Merged]: " sgn
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=20240331012249.7763F26728@inbox.vuxu.org \
--to=sgn@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).