Front page | perl.perl5.porters |
Postings from September 2017
On 16 Sep 2017 11:15, "Achim Gratz" <Stromeko@nexgo.de> wrote:
Steve Hay via perl5-porters writes:
> The final v5.26.1 is expected to ship within the next fortnight.
Does the CVE fix that was mentioned in another thread get added to
5.26.1 and does that imply an RC2?
The File-Path change has been dropped from 5.26.1, so I'm not currently
planning on an RC2.
BTW, Configure doesn't yet know about gcc 6.x and 7.x, which looks like
an oversight that should be corrected:
--- origsrc/perl-5.26.1-RC1/Configure
+++ src/perl-5.26.1-RC1/Configure
@@ -23612,7 +23612,7 @@
: add -D_FORTIFY_SOURCE if feasible and not already there
case "$gccversion" in
-[45].*) case "$optimize$ccflags" in
+[4567].*) case "$optimize$ccflags" in
*-O*) case "$ccflags$cppsymbols" in
*_FORTIFY_SOURCE=*) # Don't add it again.
echo "You seem to have -D_FORTIFY_SOURCE already,
not adding it." >&4
Thanks. That's this commit:
https://perl5.git.perl.org/perl.git/commitdiff/b9486474d36974b83d0b00fdcbfd1530299a0f7c
which jhi previously suggested to me, but privately, rather than in the
voting file... That one fell off my radar, for which I apologize.
I will put it in the voting files, but I don't think it would warrant an
RC2: It's such a minor change that I think it would be fine to simply add
it to the release.
Thread Previous
|
Thread Next