From: kernelrocks@gmail.com (Aleix Roca Nonell)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unsupported relocation type: R_X86_64_PLT32
Date: Wed, 7 Nov 2018 16:00:01 +0100 [thread overview]
Message-ID: <20181107150001.GD3947@rocks> (raw)
In-Reply-To: <CAOfkYf6c9bUqsSeB2xXYBLLZD6Ln-WLwdq5t+_f_ZR4W+fsOJw@mail.gmail.com>
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/
WARNING: multiple messages have this Message-ID (diff)
From: Aleix Roca Nonell <kernelrocks@gmail.com>
To: Shyam Saini <mayhs11saini@gmail.com>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Unsupported relocation type: R_X86_64_PLT32
Date: Wed, 7 Nov 2018 16:00:01 +0100 [thread overview]
Message-ID: <20181107150001.GD3947@rocks> (raw)
Message-ID: <20181107150001.In8pCVkmVPE4-WUImmKwlvfbillJol-VGFLnMDjxepM@z> (raw)
In-Reply-To: <CAOfkYf6c9bUqsSeB2xXYBLLZD6Ln-WLwdq5t+_f_ZR4W+fsOJw@mail.gmail.com>
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
next prev parent reply other threads:[~2018-11-07 15:00 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
2018-11-07 11:02 ` Shyam Saini
2018-11-07 15:00 ` Aleix Roca Nonell [this message]
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=20181107150001.GD3947@rocks \
--to=kernelrocks@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.