Bug#1081197: marked as done (linux: please Build-Depends on 'gcc' or on 'build-essential' rather than 'gcc-13')
Your message dated Mon, 9 Sep 2024 16:53:23 +0200
with message-id <20240909145323.6qy3gze7ajopm6mh@shell.thinkmo.de>
and subject line Re: Bug#1081197: linux: please Build-Depends on 'gcc' or on 'build-essential' rather than 'gcc-13'
has caused the Debian Bug report #1081197,
regarding linux: please Build-Depends on 'gcc' or on 'build-essential' rather than 'gcc-13'
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 owner@bugs.debian.org
immediately.)
--
1081197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081197
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
src:linux currently has an explicit Build-Depends on gcc-13. This defeats the whole point of building against whatever 'build-essential' pulls in for the target Debian release, and it results in several GCC suites getting unnecessarily installed. It would instead be desirable for src:linux to Build-Depends on either the generic 'gcc' or on 'build-essential' for its compiler requirements.
Martin-Éric
- -- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 6.10.6-686-pae (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmbetwAACgkQrh+Cd8S0
17ZdqA/8DC4Wz/FgWWvfeHSI6h5BNzr3UjxgeZsoOGDc2JlvcpVRAEWnIiq0QJdj
tyhJGOcevKD8btAtGjxPbzXEQOavQNB66BBW1fY/9/cky+L3MZarpYIJqRbf63SG
blU+Gfn0kNbE/EwryP+i7wRfEs9yUzECb2pyGJKccycsmqbZm4M9M1wdZk72fV3s
cWQ/Jo+s4MnEHgidLesijLZkP/EPD4iT3znONVWhGkDa6A/B/P2yDywvNajyHrRV
N4FT6mAS4HWVhegnX5yJN2/ndT9EH5QDq0zbUZLpzz2R7Z6L0RVNPHBxKgR+IruL
yNjpoM7+ggFsRTzMDW4LvpQjWaoTgQVJstnbCPpZwWwFAib0RjKIYfZzJuxw75rk
aIj7Sg1fjj3uf8Tx8NG6aeICdK1JuUY7pN3l2mSk4k3SdG9sdtYODkYC3ee5qWbc
pPC41R4uBrPpq1mWDaci+FYihaZAcK40oZHHZYwsPiSncuYIWrgjmxzi/4iaJUiv
ic7L8FHktwph79IHtosQR1KErKmiyAOKFU74/8H8DypmcIWc+gS5MziO4oiyWJmC
Bw+7I+Fuo90vSgwe35+d4f5BtXFJqVRaG5YEQNt/bcOQUDUJftDuDn0kpOxe8Y98
MYXsn3JvE9aQucbfNLHBuEIPDe6FkifLHeDDib7FPeQumMxh4qI=
=rkLN
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Mon, Sep 09, 2024 at 03:26:08PM +0300, Martin-Éric Racine wrote:
> ma 9. syysk. 2024 klo 13.50 Bastian Blank (waldi@debian.org) kirjoitti:
> >
> > On Mon, Sep 09, 2024 at 11:51:17AM +0300, Martin-Éric Racine wrote:
> > > src:linux currently has an explicit Build-Depends on gcc-13. This defeats the whole point of building against whatever 'build-essential' pulls in for the target Debian release, and it results in several GCC suites getting unnecessarily installed. It would instead be desirable for src:linux to Build-Depends on either the generic 'gcc' or on 'build-essential' for its compiler requirements.
> > And how will that work if src:linux uses gcc-13 to build?
> Is there any compelling reason for src:linux to hardcode the GCC
> version as an explicit dependency?
Yes, linux uses a hardcoded version of gcc to build. This also means
that it must depend on this version.
Almost every large gcc upgrade either breaks building or running of the
kernel. So it usually takes another round or two of gcc and/or linux
fixes to actually get something running out of it.
Bastian
--
If some day we are defeated, well, war has its fortunes, good and bad.
-- Commander Kor, "Errand of Mercy", stardate 3201.7
--- End Message ---
Reply to: