[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#771339: marked as done (linux: linux-headers 3.16 Makefile contains VERSION=2 PATCHLEVEL=6)

Your message dated Tue, 27 Apr 2021 02:05:20 +0200
with message-id <358a8fb55b21526f8615887b08756285f48a69ce.camel@decadent.org.uk>
and subject line Re: Bug#771339: linux: linux-headers 3.16 Makefile contains VERSION=2 PATCHLEVEL=6
has caused the Debian Bug report #771339,
regarding linux: linux-headers 3.16 Makefile contains VERSION=2 PATCHLEVEL=6
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.)


-- 
771339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771339
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux
Version: 3.16.7-2
Severity: normal

Dear Maintainer,

I was trying to build the loop-aes-source modules and kept having odd
errors about loop.h-3.x not existing, while for some reason the loop.h-2.6
was there.  Of course the build was for a 3.16 kernel and hence wanted
the 3.x file.

Turns out the loop-aes code looks at the linux-headers Makefile for the
VERSION, PATCHLEVEL and SUBVERSION, and use that to determine the kernel
version it is compiling for.

I finally noticed that we have:
/usr/src/linux-headers-3.16.0-4-amd64/Makefile:VERSION = 2
/usr/src/linux-headers-3.16.0-4-amd64/Makefile:PATCHLEVEL = 6
/usr/src/linux-headers-3.16.0-4-common/Makefile:VERSION = 3
/usr/src/linux-headers-3.16.0-4-common/Makefile:PATCHLEVEL = 16
/usr/src/linux-headers-3.16.0-4-common/Makefile:SUBLEVEL = 7

There is no SUBLEVEL in /usr/src/linux-headers-3.16.0-4-amd64/Makefile
which perhaps there should be if it is trying to provide the version
info that the kernel Makefile is known to contain.

The Makefile in the linux package for some reason has debian/rules.real
do this:

        @echo 'VERSION = 2' > $(DIR)/Makefile
        @echo 'PATCHLEVEL = 6' >> $(DIR)/Makefile

That would seem to be incorrect.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Version: 5.3~rc5-1~exp1

On Sun, 2021-04-25 at 21:27 +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Tue, Jun 11, 2019 at 09:41:25PM +0100, Ben Hutchings wrote:
> > On Tue, 2019-06-11 at 17:01 +0200, Fab Stz wrote:
> > > Source: linux
> > > Version: 4.9.0 or 4.19... probably any
> > > Followup-For: Bug #771339
> > > 
> > > Dear Maintainer,
> > > 
> > > This bug still exists in linux 4.9 and 4.19 (stretch, stretch-
> > > backports and
> > > also buster)
> > > 
> > > Like the first reporter, I tried compiling the amdgpu driver
> > > provided by AMD
> > > (through DKMS) and it is searching for the kernel version in that
> > > file.
> > > 
> > > As a workaroung in the meantime, I manually set VERSION to 4 and
> > > PATCHLEVEL to
> > > 19 in /usr/src/linux-headers-4.9.0-9-amd64/Makefile
> > > or the equivalent for 4.19
> > 
> > They should be using "make kernelversion" instead of looking for
> > variable assignments the Makefile.
> > 
> > This is not even a Debian-specific problem any more.  Looking for
> > variable assignments in the Makefile will break whenever the kernel is
> > built out-of-tree (since Linux 4.20).
> 
> So should we close this bugreport?

Yes, I'm closing this with the version that removed the nonsense
version numbers.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
                               A fail-safe circuit will destroy others.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: