On Mon, Jul 9, 2018 at 4:37 PM, <mario.limoncie...@dell.com> wrote: >> -----Original Message----- >> From: Petter Reinholdtsen [mailto:p...@hungry.com] >> Sent: Monday, July 9, 2018 9:32 AM >> To: sedat.di...@gmail.com; David Paleino; Aron Xu; Limonciello, Mario; >> Giuseppe >> Iuculano >> Cc: Dynamic Kernel Modules Support Team; debian-kernel@lists.debian.org >> Subject: Re: dkms: Build with an alternative like compiler rather than gcc >> >> >> [Sedat Dilek] >> > As a workaround I have symlinked my mycompiler wrapper-script to >> > /usr/bin/gcc. That works. >> > >> > What is the recommended way to do this correctly? >> >> Perhaps you should use dpkg-divert to ensure your replaced gcc is not >> lost in a future package upgrade? >> >> The DKMS team in Debian need active members. I'm not one of them. :( >> >> -- > > I think this is an upstream problem not at all specific to Debian's > implementation. > I would recommend to bring this discussion upstream to get it fixed there. > > I believe DKMS unsets CC before starting build, but maybe that's wrong to do > in this instance. >
Personally, I do not think it is an upstream problem. Unsetting CC before DKMS starts the build would explain the behaviour/handling. - sed@ -
