Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16540
| Path | csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod |
|---|---|
| From | Soren Stoutner <soren@debian.org> |
| Newsgroups | linux.debian.maint.python |
| Subject | blhc failing due to non-verbose build |
| Date | Fri, 06 Dec 2024 03:10:01 +0100 |
| Message-ID | <JQvX3-e3bO-3@gated-at.bofh.it> (permalink) |
| X-Original-To | Debian Python <debian-python@lists.debian.org> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Fri Dec 6 02:01:14 2024 |
| Old-Return-Path | <soren@debian.org> |
| X-Amavis-Spam-Status | No, score=-114.749 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.34, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no |
| Organization | Debian |
| MIME-Version | 1.0 |
| Content-Type | multipart/signed; boundary="nextPart78795596.AHtpVlIhoJ"; micalg="pgp-sha512"; protocol="application/pgp-signature" |
| X-Debian-User | soren |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/22625 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/7225104.MRShDI54Kn@soren-desktop |
| Approved | robomod@news.nic.it |
| Lines | 79 |
| Sender | robomod@news.nic.it |
| X-Original-Date | Thu, 05 Dec 2024 19:00:50 -0700 |
| X-Original-Message-ID | <7225104.MRShDI54Kn@soren-desktop> |
| Xref | csiph.com linux.debian.maint.python:16540 |
Show key headers only | View raw
[Multipart message — attachments visible in raw view] - view raw
I am working on PyInstaller, which is mostly written in Python, but compiles a bootloader written in c. blhc failes because the longs do not contain verbose compile flags. 111:NONVERBOSE BUILD: [ 1/21] Compiling src/pyi_utils.c 112:NONVERBOSE BUILD: [ 2/21] Compiling src/pyi_main.c 113:NONVERBOSE BUILD: [ 3/21] Compiling src/pyi_exception_dialog.c 114:NONVERBOSE BUILD: [ 4/21] Compiling src/pyi_apple_events.c 115:NONVERBOSE BUILD: [ 5/21] Compiling src/pyi_splashlib.c 116:NONVERBOSE BUILD: [ 6/21] Compiling src/pyi_global_posix.c 117:NONVERBOSE BUILD: [ 7/21] Compiling src/pyi_multipkg.c https://salsa.debian.org/python-team/packages/pyinstaller/-/jobs/6701977 The standard tricks for most C/C++ packages don’t work. # Enable all build hardening flags. export DEB_BUILD_MAINT_OPTIONS = hardening=+all # Export the DPKG default build flags. DPKG_EXPORT_BUILDFLAGS = 1 # Include the default build flags. <https://wiki.debian.org/Hardening#dpkg-buildflags> include /usr/share/dpkg/buildflags.mk # Append the CPPFLAGS to the standard CFLAGS and CXXFLAGS variables, which is how CMake likes it. <https://wiki.debian.org/ Hardening#Notes_for_packages_using_CMake> CFLAGS += $(CPPFLAGS) CXXFLAGS += $(CPPFLAGS) https://salsa.debian.org/python-team/packages/pyinstaller/-/blob/debian/ master/debian/rules?ref_type=heads Does anyone know how to convince it to populate the logs with the full flags used to compile the binaries? -- Soren Stoutner soren@debian.org
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar
blhc failing due to non-verbose build Soren Stoutner <soren@debian.org> - 2024-12-06 03:10 +0100
Re: blhc failing due to non-verbose build Bo YU <tsu.yubo@gmail.com> - 2024-12-06 04:30 +0100
Re: use of waf in pyinstaller (was: blhc) Simon McVittie <smcv@debian.org> - 2024-12-06 11:30 +0100
Re: use of waf in pyinstaller (was: blhc) Soren Stoutner <soren@debian.org> - 2024-12-07 18:40 +0100
Re: use of waf in pyinstaller (was: blhc) Scott Kitterman <debian@kitterman.com> - 2024-12-07 19:30 +0100
Re: use of waf in pyinstaller (was: blhc) Soren Stoutner <soren@debian.org> - 2024-12-07 19:40 +0100
csiph-web