Re: dkms: Build with an alternative like compiler rather than gcc

2018-07-09 Thread Sedat Dilek
gt; iucul...@debian.org; pkg-dkms-ma...@lists.alioth.debian.org; debian- >> ker...@lists.debian.org >> Subject: Re: dkms: Build with an alternative like compiler rather than gcc >> >> On Mon, Jul 9, 2018 at 4:37 PM, wrote: >> >> -Original Message- >> >> From

RE: dkms: Build with an alternative like compiler rather than gcc

2018-07-09 Thread Mario.Limonciello
.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 cor

RE: dkms: Build with an alternative like compiler rather than gcc

2018-07-09 Thread Mario.Limonciello
r...@lists.debian.org > Subject: Re: dkms: Build with an alternative like compiler rather than gcc > > On Mon, Jul 9, 2018 at 4:37 PM, wrote: > >> -Original Message- > >> From: Petter Reinholdtsen [mailto:p...@hungry.com] > >> Sent: Monday, July 9, 2

Re: dkms: Build with an alternative like compiler rather than gcc

2018-07-09 Thread Sedat Dilek
culano >> 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 >> > /

Re: dkms: Build with an alternative like compiler rather than gcc

2018-07-09 Thread Sedat Dilek
On Mon, Jul 9, 2018 at 4:31 PM, Petter Reinholdtsen wrote: > > [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

Re: dkms: Build with an alternative like compiler rather than gcc

2018-07-09 Thread Petter Reinholdtsen
[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 nee