From: Matthias Koeppe <mkoeppe@math.ucdavis.edu>
To: cygwin@cygwin.com
Subject: Re: python 3.9 package leaks CFLAGS into user packages via sysconfig
Date: Fri, 31 Dec 2021 11:33:08 -0800 [thread overview]
Message-ID: <CAJ_wo5i1MMFnniJy0_Qu3+JOQK7MTTRWvOK3koG8Gq-EXfLKtg@mail.gmail.com> (raw)
In-Reply-To: <CAJ_wo5gZp2ChiNWokn3vryB1Dzwrs-4sJQwm-28r1Ym_m5mH_A@mail.gmail.com>
On Mon, Dec 27, 2021 at 5:27 PM Matthias Koeppe <mkoeppe@math.ucdavis.edu>
wrote:
> $ python3.9 -m sysconfig | grep CFLAGS
> CFLAGS = "-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall
> -ggdb -O2 -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> -fstack-protector-strong --param=ssp-buffer-size=4 -DOPENSSL_NO_SSL3=1
> -I/usr/include/uuid/
> -fdebug-prefix-map=/pub/devel/python/python39/python39-3.9.9-1.x86_64/build=/usr/src/debug/python39-3.9.9-1
> -fdebug-prefix-map=/pub/devel/python/python39/python39-3.9.9-1.x86_64/src/Python-3.9.9=/usr/src/debug/python39-3.9.9-1
> -ggdb -O2 -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
> -fstack-protector-strong --param=ssp-buffer-size=4 -DOPENSSL_NO_SSL3=1
> -I/usr/include/uuid/
> -fdebug-prefix-map=/pub/devel/python/python39/python39-3.9.9-1.x86_64/build=/usr/src/debug/python39-3.9.9-1
> -fdebug-prefix-map=/pub/devel/python/python39/python39-3.9.9-1.x86_64/src/Python-3.9.9=/usr/src/debug/python39-3.9.9-1"
>
> These flags will end up in builds of user Python packages with extensions
> via sysconfig/distutils.
> This should be fixed by putting the necessary flags for the Python build
> into CFLAGS_NODIST instead [...]
>
Thanks, Marco, for the python-3.9.9-3 test package.
It has been reported to work well for us (
https://trac.sagemath.org/ticket/33078#comment:34), solving the reported
problem.
Matthias
next prev parent reply other threads:[~2021-12-31 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 1:27 Matthias Koeppe
2021-12-28 2:19 ` Marco Atzeri
2021-12-28 15:16 ` Marco Atzeri
2021-12-31 19:33 ` Matthias Koeppe [this message]
2021-12-31 21:22 ` Marco Atzeri
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=CAJ_wo5i1MMFnniJy0_Qu3+JOQK7MTTRWvOK3koG8Gq-EXfLKtg@mail.gmail.com \
--to=mkoeppe@math.ucdavis.edu \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).