Your message dated Wed, 04 Mar 2026 18:48:38 +0000
with message-id <[email protected]>
and subject line Bug#1106653: fixed in libpam-radius-auth 3.0.0-2
has caused the Debian Bug report #1106653,
regarding libpam-radius-auth FTCBFS: uses the build architecture 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.)


-- 
1106653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106653
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam-radius-auth
Version: 3.0.0-1
Tags: patch upstream
User: [email protected]
Usertags: ftcbfs

libpam-radius-auth fails to cross build from source, because it uses the
build architecture compiler in src/Makefile. The configure script
correctly propagates the selected compiler to Make.inc where it is
picked up by the top level Makefile, but then it never makes it to
src/Makefile. A simple mechanism to fix that is exporting the relevant
variables. I'm attaching a patch for your convenience.

Helmut
--- libpam-radius-auth-3.0.0.orig/Makefile
+++ libpam-radius-auth-3.0.0/Makefile
@@ -22,6 +22,11 @@
 endif
 endif
 
+# export for src/Makefile
+export CC
+export CFLAGS
+export CPPFLAGS
+
 VERSION = $(shell cat VERSION)
 
 ######################################################################

--- End Message ---
--- Begin Message ---
Source: libpam-radius-auth
Source-Version: 3.0.0-2
Done: Christoph Goehre <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libpam-radius-auth, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Goehre <[email protected]> (supplier of updated libpam-radius-auth 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 04 Mar 2026 13:04:42 +0100
Source: libpam-radius-auth
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert <[email protected]>
Changed-By: Christoph Goehre <[email protected]>
Closes: 1106653
Changes:
 libpam-radius-auth (3.0.0-2) unstable; urgency=medium
 .
   * [8544c3b] rebuild patch queue from patch-queue branch
     added patches:
     Makefile-export-more-compiler-variables-to-fix-cross-buil.patch
     (Closes: #1106653)
   * [74fd624] d/control: Increase Standards-Version to 4.7.3
Checksums-Sha1:
 001a146e8758be9fe1ad8aa719d4e7d5c0ebe361 2026 libpam-radius-auth_3.0.0-2.dsc
 f069fab8c8e8f5fc65e6e4fcba4e5acebd7e4859 9648 
libpam-radius-auth_3.0.0-2.debian.tar.xz
Checksums-Sha256:
 c0a500284fe2e9a40e70c35dad05969c288978f476308e7cb32aed00c03774a1 2026 
libpam-radius-auth_3.0.0-2.dsc
 0872cd3db7444604bae94067d5c1b7adb0f7e25b7089f69f590359725a330b83 9648 
libpam-radius-auth_3.0.0-2.debian.tar.xz
Files:
 c1e4b33eabacbdfe96d36ae742f1df61 2026 admin optional 
libpam-radius-auth_3.0.0-2.dsc
 9693eed52636529d83a2c670436b12d6 9648 admin optional 
libpam-radius-auth_3.0.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEi5SBnCVVcKN0tizNJuPIdadEIO8FAmmoezoACgkQJuPIdadE
IO845xAAqJBD0GmtqVBTd/TUEWZBScpBsf5SmUjgCBWuSGCrZRBwAniSBtW8f+dR
4y+PODV0eNABvagxYkHPC4gywBF1DK6dpxICv+GHeCKwfg5tYLnxDJrNL3u3xUkG
BRUqypKOILwToK8Hy93B+6UUj5/aQD4XsI6m5Z3Kz73N1zQdER1TSQsbToIqJF4d
qw9djTi1hIM09oVx9yzzI0HiflHI1j9rRBT73OYqquVKuw968yxR4edreibjJWAL
X4Sm5ggJdEDdLsvVjBXdVncqP/6j6pPdH9d4W0BgkmxNjUTPSLvS/HkrinvtlQt0
P9nXcSvRqKuBBpYAZnR94Lqz+IiWAltoDU1RX1NqEyMRiPxaTVA9313yKy/tUBXN
WrSFsr6+LAIN7HVxHcmorjiTyWWHf9SouEO53gFQ4OQfppCuIaihWI8zXPjdf2V+
NHUCoEx9c8kd1PiyUA/K7QduypsMP34E1FZ/Z5Oa+V8Pf2wUTQW26pwDvFl009u4
pIR08m87fUDhuVlRS4UDRykB7yeig6cMHe9HalKdcWiJj6yU7BKxtYZfKXvFxvtM
TfxcC1mwruZ+j0rw1D4qAccEbJmE+NX//cgzJcwjx0aBjptDPSxTvfUFj8Tww8+6
CLIuWma4FQsQFEeFt6tNSemTSSr+nPgZg6lj7sf7ytidPKCfI7A=
=IKXb
-----END PGP SIGNATURE-----

Attachment: pgpcaIbku8_R7.pgp
Description: PGP signature


--- End Message ---

Reply via email to