testing kernel module build in branches/304 and branches/340

[Luca Boccassi]

On Feb 28, 2016 18:53, "Andreas Beckmann" <anbe at debian.org> wrote:
>
> On 2016-02-28 15:40, Luca Boccassi wrote:
> > Remember the fix to dkms.conf I did a short while back, to unset ARCH
> > (NVIDIA expects kernel arch, but Debian tools pass ABI triplet)?
>
> I don't have ARCH set in my environment, so I never ran into these
> problems. But the build should not fail due to some spuriously set
> environment variable values (well, we won't guarantee anything for
> CC=f77 CFLAGS=-foobar, (unless you can compile the kernel with these
> settings, then building the module should work, too)). Thanks for
> fixing. You may need this for 304, too.

I'm not even sure why it's set in my environment. Maybe it's cowbuilder?
I'll try to investigate when I got time.

But yeah the driver picked a very simple and common var name, so it's not
too surprising there's a clash I guess...

> Do you have any idea about #815888, maybe same as #813312? Something
> about gdm does not start ... Both bugs lack lots of information, but I'm
> unsure what to ask for ... are these perhaps Optimus systems?

I will have a look at those reports either tomorrow or later this week.

Kind regards,
Luca Boccassi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160228/4f18826b/attachment.html>