Your message dated Fri, 23 Jan 2026 16:34:36 +0000
with message-id <[email protected]>
and subject line Bug#1119557: fixed in simh 3.8.1-6.3
has caused the Debian Bug report #1119557,
regarding simh: please build using the default build flags
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.)
--
1119557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119557
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: simh
Version: 3.8.1-6.2
User: [email protected]
Usertags: hardening-buildflags
simh is not currently using the default build flags set by dpkg-buildflags(1).
The default flags are chosen for multiple reasons including security,
performance, reproducibility, adherence to standards, and error handling.
Please make sure that simh builds using the default build flags. blhc(1p)
and hardening-check(1) can be used to confirm that the issue is fixed.
In the general case, packages honoring CFLAGS, LDFLAGS, and other
similar environment variables get the default build flags for free
without the need for any work on the maintainer side. In the case of
simh, the flags are either ignored or overridden.
The most common reasons for this are:
Hand-written Makefiles
----------------------
Some upstream Makefiles either override the values of variables such as
CFLAGS and similar or do not use them at all. See:
https://wiki.debian.org/HardeningWalkthrough#Handwritten_Makefiles
Misconfigured build systems
---------------------------
If the upstream code uses autotools, CMake, or other popular build
systems, it usually requires no further modifications. If might however
be that some variables are hardcoded in some way.
In this CMake snippet, the value of CXXFLAGS is overwritten with "-O2":
set(CMAKE_CXX_FLAGS "-O2")
If the intention is to append to CXXFLAGS, one should use the following
instead:
set(CMAKE_CXX_FLAGS "-O2 ${CMAKE_CXX_FLAGS}")
See #655870 for a similar autotools example.
Very old debhelper usage
------------------------
Packages not using dh(1), or those using a debhelper compatibility level
less than 9, need to manually include /usr/share/dpkg/buildflags.mk in
order for the dpkg-buildflags variables to be set:
https://wiki.debian.org/Hardening#dpkg-buildflags
Flags hardcoded in debian/rules (either voluntarily or not)
-----------------------------------------------------------
Some packages voluntarily hardcode the values of CFLAGS and friends in
debian/rules, ignoring the defaults set by dpkg-buildflags(1).
Others attempt to append to the variables, but end up accidentally
overriding the defaults:
#!/usr/bin/make -f
export CFLAGS += -pipe -fPIC -Wall
%:
dh $@
Debhelper only sets CFLAGS if it is not set yet. In the example above,
when dh is invoked the value of CFLAGS is "-pipe -fPIC -Wall", hence the
hardened defaults are not used. The right way to append to CFLAGS is
using DEB_CFLAGS_MAINT_APPEND instead, as documented in
dpkg-buildflags(1).
For a detailed analysis of this issue, see:
https://people.debian.org/~ema/nocflags_paper.pdf (eprint: hal-05334704)
--- End Message ---
--- Begin Message ---
Source: simh
Source-Version: 3.8.1-6.3
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
simh, 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.
Andreas Tille <[email protected]> (supplier of updated simh 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: Tue, 13 Jan 2026 16:45:50 +0100
Source: simh
Architecture: source
Version: 3.8.1-6.3
Distribution: unstable
Urgency: medium
Maintainer: Andreas Bombe <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1075511 1119557
Changes:
simh (3.8.1-6.3) unstable; urgency=medium
.
* Non-maintainer upload.
* Maintain package in Debian team on Salsa
* Fix build with gcc-14
Closes: #1075511
* Enable build using the default build flags
Closes: #1119557
* Secure URI in Homepage
* d/watch:
- version=5
- Add comments about non-free versions
* debhelper-compat=13
* cme fix dpkg-control
Checksums-Sha1:
538195920b1605d5f8b886ed08c25cfae3adafb6 1831 simh_3.8.1-6.3.dsc
137012a7bb709c11374b289c3f33a47c459207cb 27872 simh_3.8.1-6.3.debian.tar.xz
4f27d47dc87ba293e7317fb8e37d19ea843e7b1a 6173 simh_3.8.1-6.3_amd64.buildinfo
Checksums-Sha256:
0542e9cb68217af9e7dcdc180b9d315965e770d1521215830726f23ac27422a4 1831
simh_3.8.1-6.3.dsc
87ddd2a7f58c136134f998837f59d3c0635189ef6d5bf6322daad4f4ad3ee60a 27872
simh_3.8.1-6.3.debian.tar.xz
97adf4492a875de8b1789adf362ed1912335f188583f7c3bf72d4ca8167ea7a3 6173
simh_3.8.1-6.3_amd64.buildinfo
Files:
b9e2554a854c556b261aaebd51f8e178 1831 otherosfs optional simh_3.8.1-6.3.dsc
a618846bcdb55ab637f1743ee5351d96 27872 otherosfs optional
simh_3.8.1-6.3.debian.tar.xz
461602563a9f3c7f9e3397a1226f4259 6173 otherosfs optional
simh_3.8.1-6.3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlmajYRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHgzQ/9Er3hSz3S1yFhHmvUdqj+/Q7zEsfVS69t
IFeeDEIEzimBOGDoNcL/5MmIiKXiEAGvE0ucFmH69E68SZrTOKhlNjIa4uSHDtC3
Oriyt0VVLKQISYW42T3ORT4aJfY/L5ZcRRhljlRhGcxDBbjpOtQSCawlp57y2+WI
zQR7AARiPmIs4ULcXg48l4Dk41H3YvtZNzBG+PpTlzBMp5QeUTN/zHlvB1VpI9iX
GU4Urpe0u1CKGxDb/2mJ38QGKTBjNsU053yvTm9iEUxg1BDu1/5DDrWbm9hiNKV7
s+u+AiLb1HjXkWFzp8hL9YgrK+UHzVtRg9rr/L53NMWIj1QinuY0KqnrO5eVBA5Q
rvxNvSkz7xwQXHUV+kVe0bBD6vlG45Mw56RayzKcRjmgGo5HAIY3J2T3D/ND2ojS
3s1if3qsmZ8TWCn5urQ6Xey5EXpnjBJzlnzkh3kE9LMeXz4tKFqB1ZiQOhe2m9X2
6tRo3L/UEMXTH14dZXfiv5sS1F0miAWUOcsH9QDM9XH3deQ6jdyqTigmUdJdnhzK
fi49a1JlqNdwT8ZrlA8hyHukbp7O6Qnhx68KwsyhIvH3InHTBbOqbgChBp9so7RX
q5raI85Wabk97iZ0HMnL40dzycT9SsEmCRLN5o4k5+fh42g9aBWKjSdK1keuXF4y
9t205euG0H4=
=SPN3
-----END PGP SIGNATURE-----
pgp_XyIHQEZ1M.pgp
Description: PGP signature
--- End Message ---
