From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: scons: update to 4.0.1.
Date: Mon, 07 Sep 2020 23:07:54 +0200 [thread overview]
Message-ID: <20200907210754.cWRKOLcCaYB6cx6MN68ToUn_-tf2SDdssOcGNbfAIps@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24448@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/pull/24448#issuecomment-688511270
Comment:
Relevant sections of release notes with my annotations:
> NOTE: The 4.0.0 Release of SCons dropped Python 2.7 Support
This is what we want largely. Need to test build of packages using scons because the build scripts are literally python files.
> - Allow user specified location for vswhere.exe specified by VSWHERE.
> NOTE: This must be set at the time the 'msvc' 'msvs' and/or 'mslink' tool(s) are initialized to have any effect.
Does not apply to us.
> - Resolve Issue #3248 - Removing '-Wl,-Bsymbolic' from SHLIBVERSIONFLAGS
> NOTE: If your build depends on the above you must now add to your SHLIBVERSIONFLAGS
Might apply to us? We will see during rebuild I guess.
> - Fixed Github Issue 3628 - Hardcoding pickle protocol to 4 (supports python 3.4+)
> and skipping Python 3.8's new pickle protocol 5 whose main advantage is for out-of-band data buffers.
> NOTE: If you used Python 3.8 with SCons 3.0.0 or above, you may get a a pickle protocol error. Remove your
> .sconsign.dblite. You will end up with a full rebuild.
Does not apply to us (only ever used python2).
next prev parent reply other threads:[~2020-09-07 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 2:40 [PR PATCH] " CameronNemo
2020-08-24 2:50 ` [PR PATCH] [Updated] " CameronNemo
2020-08-24 2:52 ` CameronNemo
2020-08-24 2:55 ` CameronNemo
2020-08-24 11:33 ` sgn
2020-08-24 12:37 ` sgn
2020-08-24 12:41 ` sgn
2020-09-07 21:07 ` CameronNemo [this message]
2020-09-08 0:05 ` sgn
2020-10-19 14:53 ` sgn
2020-10-25 4:47 ` [PR PATCH] [Closed]: " sgn
2020-10-19 11:33 [PR PATCH] " kkga
2020-10-19 15:00 ` Duncaen
2020-10-19 16:06 ` kkga
2020-10-19 16:13 ` Duncaen
2020-10-22 15:53 [PR PATCH] " sgn
2020-10-22 15:54 ` 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=20200907210754.cWRKOLcCaYB6cx6MN68ToUn_-tf2SDdssOcGNbfAIps@z \
--to=cameronnemo@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).