Date: Sun, 24 Apr 2022 22:36:40 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 263353] lang/python38: fix excessive ld.lld memory use with LTO in port options Message-ID: <bug-263353-21822-tLwuiFPEaH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263353-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-263353-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=3D263353 --- Comment #4 from Matthias Andree <mandree@FreeBSD.org> --- Created attachment 233456 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D233456&action= =3Dedit failing poudriere build log with LTO and optimization, showing excess -g. Kubilay, Python@ guys, the issue is an excess "-g" in spite of NOT setting WITH_DEBUG, not LTO. The FreeBSD ports Mk/* stuff properly omits -g, but the Python 3.8 build stuff = adds it specifically when LTO is in place. In the log, find lots of "-flto -g" (search for it, literally, of course without the quotes). This goes unnoticed because everything's stripped in the stage area, so no stage-qa complaints, just excess disk space use. The culprit is the upstream configure stuff, not something in FreeBSD. I am attaching my log. But I seriously ask everyone to respect my debugging= and solution and not fuss with distractions and excursions. Trust me to be able= to read my Poudriere error logs. All these questions are wasting my time.=20 So, unless there are substantiated vetos with better solutions brought up,= I may commit my patch 14 days after my proposal, or with maintainer approval, whichever comes first. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263353-21822-tLwuiFPEaH>