On Wed, Feb 16, 2022 at 6:45 PM Marc Haber <mh+debian-packa...@zugschlus.de> wrote: > On Tue, Feb 15, 2022 at 09:58:49PM +0200, Martin-Éric Racine wrote: > > On Tue, Feb 15, 2022 at 9:10 PM Marc Haber > > <mh+debian-packa...@zugschlus.de> wrote: > > > > > > On Tue, Feb 15, 2022 at 09:03:01PM +0200, Martin-Éric Racine wrote: > > > > 1.9.8p2-1 FTBFS on Geode testing host (log attached earlier) > > > > 1.9.9-1 FTBFS on Geode testing host (log attached earlier) > > > > > > I apologize, I didnt see earlier that your builds were already failing > > > at build time. The error is > > > > > > config.status:1474: error: cannot find input file: > > > `plugins/sudoers/sudoers' > > > > > > Was that file actually missing in your build chroot? If not, I don't > > > know what went wrong there. > > > > No idea. I unpacked the source and types debuild. That's all.
Btw, the build log has tons of the following: ./configure: cannot duplicate fd -19201 to fd 0: Bad file descriptor > Can you retry building with the lines 4863-4866: > > AX_CHECK_LINK_FLAG([-fcf-protection], [ > AX_APPEND_FLAG([-fcf-protection], [SSP_CFLAGS]) > AX_APPEND_FLAG([-Wc,-fcf-protection], [SSP_LDFLAGS]) > ]) > > of configure.ac removed? There is suspicion that the hardening options don't > play too well with Geode LX. I cannot help but wonder why the build doesn't simply parse $(HARDENING_CFLAGS) and $(HARDENING_LDFLAGS). Hard-coded hardening options tend to be a bad idea. GCC supports them all, but the target host's CPU won't always support them. during GIMPLE pass: cunroll ../../../lib/util/event.c: In function ‘sudo_ev_add_v2’: ../../../lib/util/event.c:465:1: internal compiler error: in graphds_scc, at graphds.c:316 465 | sudo_ev_add_v2(struct sudo_event_base *base, struct sudo_event *ev, | ^~~~~~~~~~~~~~ 0xb754d904 __libc_start_main ../csu/libc-start.c:332 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. *** diff -Nru sudo-1.9.9/debian/changelog sudo-1.9.9/debian/changelog --- sudo-1.9.9/debian/changelog 2022-01-31 21:19:55.000000000 +0200 +++ sudo-1.9.9/debian/changelog 2022-02-16 18:56:31.000000000 +0200 @@ -1,3 +1,9 @@ +sudo (1.9.9-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + + -- Martin-Éric Racine <martin-eric.rac...@iki.fi> Wed, 16 Feb 2022 18:56:31 +0200 + sudo (1.9.9-1) unstable; urgency=medium * new upstream version diff -Nru sudo-1.9.9/debian/patches/remove-fcf-protection.patch sudo-1.9.9/debian/patches/remove-fcf-protection.patch --- sudo-1.9.9/debian/patches/remove-fcf-protection.patch 1970-01-01 02:00:00.000000000 +0200 +++ sudo-1.9.9/debian/patches/remove-fcf-protection.patch 2022-02-16 18:56:31.000000000 +0200 @@ -0,0 +1,42 @@ +Description: <short summary of the patch> + TODO: Put a short summary on the line above and replace this paragraph + with a longer explanation of this change. Complete the meta-information + with other relevant fields (see below for details). To make it easier, the + information below has been extracted from the changelog. Adjust it or drop + it. + . + sudo (1.9.9-1.1) UNRELEASED; urgency=medium + . + * Non-maintainer upload. +Author: Martin-Éric Racine <martin-eric.rac...@iki.fi> + +--- +The information above should follow the Patch Tagging Guidelines, please +checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here +are templates for supplementary fields that you might want to add: + +Origin: <vendor|upstream|other>, <url of original patch> +Bug: <url in upstream bugtracker> +Bug-Debian: https://bugs.debian.org/<bugnumber> +Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber> +Forwarded: <no|not-needed|url proving that it has been forwarded> +Reviewed-By: <name and email of someone who approved the patch> +Last-Update: 2022-02-16 + +--- sudo-1.9.9.orig/configure.ac ++++ sudo-1.9.9/configure.ac +@@ -4860,10 +4860,10 @@ if test "$enable_hardening" != "no"; the + AX_APPEND_FLAG([-fstack-clash-protection], [SSP_CFLAGS]) + AX_APPEND_FLAG([-Wc,-fstack-clash-protection], [SSP_LDFLAGS]) + ]) +- AX_CHECK_LINK_FLAG([-fcf-protection], [ +- AX_APPEND_FLAG([-fcf-protection], [SSP_CFLAGS]) +- AX_APPEND_FLAG([-Wc,-fcf-protection], [SSP_LDFLAGS]) +- ]) ++dnl AX_CHECK_LINK_FLAG([-fcf-protection], [ ++dnl AX_APPEND_FLAG([-fcf-protection], [SSP_CFLAGS]) ++dnl AX_APPEND_FLAG([-Wc,-fcf-protection], [SSP_LDFLAGS]) ++dnl ]) + AX_CHECK_LINK_FLAG([-Wl,-z,relro], [AX_APPEND_FLAG([-Wl,-z,relro], [LDFLAGS])]) + AX_CHECK_LINK_FLAG([-Wl,-z,now], [AX_APPEND_FLAG([-Wl,-z,now], [LDFLAGS])]) + AX_CHECK_LINK_FLAG([-Wl,-z,noexecstack], [AX_APPEND_FLAG([-Wl,-z,noexecstack], [LDFLAGS])]) diff -Nru sudo-1.9.9/debian/patches/series sudo-1.9.9/debian/patches/series --- sudo-1.9.9/debian/patches/series 2022-01-31 21:19:55.000000000 +0200 +++ sudo-1.9.9/debian/patches/series 2022-02-16 18:56:31.000000000 +0200 @@ -1,3 +1,4 @@ paths-in-samples.diff Whitelist-DPKG_COLORS-environment-variable.diff sudo-ldap-docs +remove-fcf-protection.patch Martin-Éric