From mboxrd@z Thu Jan 1 00:00:00 1970 From: kernelrocks@gmail.com (Aleix Roca Nonell) Date: Wed, 7 Nov 2018 16:00:01 +0100 Subject: Unsupported relocation type: R_X86_64_PLT32 In-Reply-To: References: <20181103125439.GA2327@rocks.localdomain> <20181103131653.GB2327@rocks.localdomain> <20181107071814.GA3947@rocks> Message-ID: <20181107150001.GD3947@rocks> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Wed, Nov 07, 2018 at 04:32:36PM +0530, Shyam Saini wrote: > Hi Aleix, > > > (reminder just in case the email was missed!) > > When you post queries/bug reports then you should always Cc > maintainers and subsystem specific > mailing lists. > > You can can find maintainers and mailings lists by: > $ cd /path to your kernel source/ > $ ./scripts/get_maintainer.pl /path to your wireless driver file Hi Shyam, Sorry, I think I have not made myself clear enough. The error that doesn't let me sleep at night, > "Unsupported relocation type: R_X86_64_PLT32" it is not related at all with my wireless driver. This error pops up when compiling a Linux Kernel 4.14 from Linus tree with gcc-{8,7,5,4.9}. The reason of why I'm compiling a linux kernel 4.14 is to identify a commit which introduced a possible regression in my wireless driver. To provide some more context, I'm adding the full compile report in the following links: Linux 4.14 (+ patches [2,3]) build with gcc-8.2.1 https://drive.google.com/open?id=1tg0iR3dirhW4MhU_3RXcNyvmiJ-j6nBy Linux 4.14 vanilla build with gcc-4.9.4 https://drive.google.com/open?id=1YJIpVc5VA1xpblQQxHSzrWhTArl5lTKQ I have already spent too many hours in this detail, so any hint is welcomed :) Thank you! > [1] - https://lore.kernel.org/patchwork/patch/892780/ > [2] - https://lore.kernel.org/patchwork/patch/868613/ > [3] - https://lore.kernel.org/patchwork/patch/934722/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gKPJR-0002Ut-4d for kernelnewbies@kernelnewbies.org; Wed, 07 Nov 2018 10:00:09 -0500 Received: by mail-wr1-x433.google.com with SMTP id z13-v6so15362916wrs.3 for ; Wed, 07 Nov 2018 07:00:08 -0800 (PST) Date: Wed, 7 Nov 2018 16:00:01 +0100 From: Aleix Roca Nonell To: Shyam Saini Subject: Re: Unsupported relocation type: R_X86_64_PLT32 Message-ID: <20181107150001.GD3947@rocks> References: <20181103125439.GA2327@rocks.localdomain> <20181103131653.GB2327@rocks.localdomain> <20181107071814.GA3947@rocks> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: Kernelnewbies List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org Message-ID: <20181107150001.In8pCVkmVPE4-WUImmKwlvfbillJol-VGFLnMDjxepM@z> On Wed, Nov 07, 2018 at 04:32:36PM +0530, Shyam Saini wrote: > Hi Aleix, > > > (reminder just in case the email was missed!) > > When you post queries/bug reports then you should always Cc > maintainers and subsystem specific > mailing lists. > > You can can find maintainers and mailings lists by: > $ cd /path to your kernel source/ > $ ./scripts/get_maintainer.pl /path to your wireless driver file Hi Shyam, Sorry, I think I have not made myself clear enough. The error that doesn't let me sleep at night, > "Unsupported relocation type: R_X86_64_PLT32" it is not related at all with my wireless driver. This error pops up when compiling a Linux Kernel 4.14 from Linus tree with gcc-{8,7,5,4.9}. The reason of why I'm compiling a linux kernel 4.14 is to identify a commit which introduced a possible regression in my wireless driver. To provide some more context, I'm adding the full compile report in the following links: Linux 4.14 (+ patches [2,3]) build with gcc-8.2.1 https://drive.google.com/open?id=1tg0iR3dirhW4MhU_3RXcNyvmiJ-j6nBy Linux 4.14 vanilla build with gcc-4.9.4 https://drive.google.com/open?id=1YJIpVc5VA1xpblQQxHSzrWhTArl5lTKQ I have already spent too many hours in this detail, so any hint is welcomed :) Thank you! > [1] - https://lore.kernel.org/patchwork/patch/892780/ > [2] - https://lore.kernel.org/patchwork/patch/868613/ > [3] - https://lore.kernel.org/patchwork/patch/934722/ _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies