From: mayhs11saini@gmail.com (Shyam Saini) To: kernelnewbies@lists.kernelnewbies.org Subject: Unsupported relocation type: R_X86_64_PLT32 Date: Wed, 7 Nov 2018 16:32:36 +0530 [thread overview] Message-ID: <CAOfkYf6c9bUqsSeB2xXYBLLZD6Ln-WLwdq5t+_f_ZR4W+fsOJw@mail.gmail.com> (raw) In-Reply-To: <20181107071814.GA3947@rocks> 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 Thanks a lot, Shyam > On Sat, Nov 03, 2018 at 02:16:53PM +0100, Aleix Roca Nonell wrote: > > On Sat, Nov 03, 2018 at 01:54:39PM +0100, Aleix Roca Nonell wrote: > > > Hi all! > > > > > > In my attempt to write my first useful kernel patch, I'm tracking down > > > a possibly kernel regression on my laptop's wireless driver. I'm > > > trying to use git bisect to narrow down the problem and I'm having > > > trouble compiling a Linux kernel 4.14 from Linus tree in my Arch > > > Linux. > > > > > > The error I'm getting is "Unsupported relocation type: R_X86_64_PLT32" > > > > > > I have read about gcc enabling -fPIC by default from gcc-6 so I have > > > tried compiling with gcc-{8,7,5,4.9} with and without > > > "-fno-pic -no-pic" by running > > > > > > make CC="gcc-5 -fno-pic -no-pic" > > > > > > with no luck. I was expecting those R_X86_64_PLT32 relocations not to > > > be generated with this options but there is something I have still not > > > understood. > > > > > > I have been able to compile the kernel after applying greg's stable > > > tree patch [1] (and [2,3] for gcc-8) but the kernel refuses to boot. > > > > > > Any help/comments on either the problem or the followed methodology will be > > > appreciated! > > > > > > Thank you! :D > > > > > > [1] - https://lore.kernel.org/patchwork/patch/892780/ > > > [2] - https://lore.kernel.org/patchwork/patch/868613/ > > > [3] - https://lore.kernel.org/patchwork/patch/934722/ > > > > Sorry, I meant "-fno-pie -no-pie" instead of "-fno-pic -no-pic" > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies at kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: Shyam Saini <mayhs11saini@gmail.com> To: kernelrocks@gmail.com Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org> Subject: Re: Unsupported relocation type: R_X86_64_PLT32 Date: Wed, 7 Nov 2018 16:32:36 +0530 [thread overview] Message-ID: <CAOfkYf6c9bUqsSeB2xXYBLLZD6Ln-WLwdq5t+_f_ZR4W+fsOJw@mail.gmail.com> (raw) Message-ID: <20181107110236.YuzEmnCezUfisTkFs0N52ItyCJTDxhhHipB7sgANAdE@z> (raw) In-Reply-To: <20181107071814.GA3947@rocks> 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 Thanks a lot, Shyam > On Sat, Nov 03, 2018 at 02:16:53PM +0100, Aleix Roca Nonell wrote: > > On Sat, Nov 03, 2018 at 01:54:39PM +0100, Aleix Roca Nonell wrote: > > > Hi all! > > > > > > In my attempt to write my first useful kernel patch, I'm tracking down > > > a possibly kernel regression on my laptop's wireless driver. I'm > > > trying to use git bisect to narrow down the problem and I'm having > > > trouble compiling a Linux kernel 4.14 from Linus tree in my Arch > > > Linux. > > > > > > The error I'm getting is "Unsupported relocation type: R_X86_64_PLT32" > > > > > > I have read about gcc enabling -fPIC by default from gcc-6 so I have > > > tried compiling with gcc-{8,7,5,4.9} with and without > > > "-fno-pic -no-pic" by running > > > > > > make CC="gcc-5 -fno-pic -no-pic" > > > > > > with no luck. I was expecting those R_X86_64_PLT32 relocations not to > > > be generated with this options but there is something I have still not > > > understood. > > > > > > I have been able to compile the kernel after applying greg's stable > > > tree patch [1] (and [2,3] for gcc-8) but the kernel refuses to boot. > > > > > > Any help/comments on either the problem or the followed methodology will be > > > appreciated! > > > > > > Thank you! :D > > > > > > [1] - https://lore.kernel.org/patchwork/patch/892780/ > > > [2] - https://lore.kernel.org/patchwork/patch/868613/ > > > [3] - https://lore.kernel.org/patchwork/patch/934722/ > > > > Sorry, I meant "-fno-pie -no-pie" instead of "-fno-pic -no-pic" > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-11-07 11:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-03 12:54 Unsupported relocation type: R_X86_64_PLT32 Aleix Roca Nonell 2018-11-03 12:54 ` Aleix Roca Nonell 2018-11-03 13:16 ` Aleix Roca Nonell 2018-11-03 13:16 ` Aleix Roca Nonell 2018-11-07 7:18 ` Aleix Roca Nonell 2018-11-07 7:18 ` Aleix Roca Nonell 2018-11-07 11:02 ` Shyam Saini [this message] 2018-11-07 11:02 ` Shyam Saini 2018-11-07 15:00 ` Aleix Roca Nonell 2018-11-07 15:00 ` Aleix Roca Nonell
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAOfkYf6c9bUqsSeB2xXYBLLZD6Ln-WLwdq5t+_f_ZR4W+fsOJw@mail.gmail.com \ --to=mayhs11saini@gmail.com \ --cc=kernelnewbies@lists.kernelnewbies.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).