Date: Thu, 27 Jun 2019 11:04:40 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 238821] lang/python35: Fix packaging on GCC architectures Message-ID: <bug-238821-21822-swBYm6wLHi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238821-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-238821-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238821 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-patch --- Comment #8 from Kubilay Kocak <koobs@FreeBSD.org> --- Issue 28017 [1] shows that that commit was followed up by a subsequent comm= it: compile with -std=3Dc99 instead of -std=3Dgnu99; use kiddie-gloves with bluetooth/bluetooh.h https://hg.python.org/cpython/rev/91017e2202ae Changing just the cstd doesn't appear to be sufficient, we should backport 91017e22 incl. the bluetooth header check block too. FWIW, the bluetooth headers were fixed to compile with strict C in=20 https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit?id=3Dcf52a40 So theoretically we could fix the root cause, but unless Python went down t= hat track later (maybe they did?), its probably not best course of action to deviate from upstream code and carry the patch locally. [1] https://bugs.python.org/issue28017 --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238821-21822-swBYm6wLHi>