Your message dated Thu, 16 Jan 2025 14:09:43 -0700
with message-id <[email protected]>
and subject line Pam 1.7.0 has an entirely different build system
has caused the Debian Bug report #1057729,
regarding pam FTCBFS: passes host flags to build compiler
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1057729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057729
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pam
Version: 1.3.1-1
Severity: important
Justification: bootstrap set
User: [email protected]
Usertags: ftcbfs
X-Debbugs-Cc: Andreas Henriksson <[email protected]>

Hi,

since we now enabled PAC/BTI flags, distinguishing build flags and host
flags has become important. pam already does this, but about four years
ago Andreas added a fix-autoreconf.patch that breaks this distinction.

In essence, I think Andreas meant to ensure that CFLAGS passed by a user
are not discarded but passed to actual build invocations and that's what
his patch does in effect.

Cross compilation poses the opposite requirement: Flags passed via
CFLAGS must not propagate to some of the compiler invocations, because
the compiler may be unable to understand them as is the case with e.g.
-mbranch-protection=standard.

I note that in a native build, configure.ac already sets
BUILD_CFLAGS=${CFLAGS}, so this assignment should be harmless for native
builds. If it really was, Andreas probably wouldn't have patched it, so
rather than simply reverting the patch, we should understand the problem
he was trying to solve and I quite obviously miss something important.

Can I leave this up to you? To verify the cross build failure, please
use amd64 or arm64 as host architecture. These are the only ones with
architecture-specific compiler flags.

Helmut

--- End Message ---
--- Begin Message ---
source: pam
source-version: 1.7.0-1

Pam now uses a fairly stock meson build system; it looks like meson
tries to support cross-builds, so pam cross building will probably work
about as well as most meson projects.
Anyway, the autoconf/automake patch at the root of this bug is
definitely gone: all remnants of autoconf/automake are gone from pam.

If you still see cross-build failures, please let me know, probably
under a new bug.

--Sam

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to