Bug#818862: Similar issues with kernel 4.6 and 4.7

[Andreas Beckmann]

On 2016-08-17 00:07, Eduard Bloch wrote:
>> module-assistant build --text-mode --force --kvers-list 4.7.0-rc7-amd64 nvidia-kernel
> 
> a) minor detail, the readme does not mention --force, although it should not be required.

It's just helpful to rebuild again and again looking for your problem...

> c) I tried a similar command with 4.6.0-1-amd64 (Sid kernel) and it did NOT work. Now

I just had a good burger for dinner and it DID work.
But it still didn't tell me the command you used.

Nevertheless, I managed to come up with a command that reproduces your
failure:

    m-a build -t -O -k /usr/src/linux-headers-4.6.0-1-amd64 -f nvidia


So coming back to your initial question:

On 2016-08-16 20:02, Eduard Bloch wrote:
> I have no idea how you manage to build the current modules even for Sid.

We use -l, not -k.
And let the buildsystem figure out the details from /lib/modules

I don't think there is an easy way to make the -k option work for the
split Debian header packages (e.g. -common and -amd64) with the nvidia
kernel module (and their conftest.sh script). But it seems to work for
the locally built kernel (no split headers) I have residing in my module
testbuild chroot.

But I doubt that this is a problem, unless you want to build against
not-installed (i.e. no /lib/modules/$KVERS/{build,source} symlinks) but
split (separated -common and e.g. -amd64) headers.

If it is installed, just use -l


Andreas

PS: Setting only SYSSRC was an error which made us maintain our own
conftest.h for about 10 years since the upstream conftest.sh didn't work
with the split Debian header packages. Because we never told it about
SYSOUT as well.