From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.14
Date: Mon, 30 Aug 2021 14:28:39 +0300 [thread overview]
Message-ID: <CAHp75VeSOMu+xvgv81BVc8R4U9MPB=50hgQHTULyTUKO6+Rh9A@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Ve_zQctbiOkJbeL6T=5FOukGbL99kcgpLdL3Zf8DfFdDA@mail.gmail.com>
On Mon, Aug 30, 2021 at 12:39 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Mon, Aug 30, 2021 at 1:20 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> Haven't investigated so far, but all 32-bit builds for x86 on Debian unstable
> gcc (Debian 10.2.1-6) 10.2.1 20210110
> fail for me with
> FATAL: modpost: section header offset=11258999068426292 in file
> 'vmlinux.o' is bigger than filesize=509598908
>
> (hex value is 28000000000034)
>
> Replacing
> #if KERNEL_ELFCLASS == ELFCLASS32
> with
> #if 1
>
> in scripts/mod/modpost.h fixes it to me.
>
> As said, I haven't done any work to find the root cause, so JFYI.
>
> P.S. Yes, I did a completely clean build and tried different kernel
> configurations including just default i386_defconfig in the release,
> the same error. x86_64 builds are good.
Okay, I think I found it. I have had ccache with a quite bit pile of
cache files in between, After cleaning it it seems everything went
fine.
Sorry for the noise.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-08-30 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 22:19 Linux 5.14 Linus Torvalds
2021-08-30 9:11 ` Sudip Mukherjee
2021-08-30 15:17 ` Linus Torvalds
2021-09-12 19:29 ` Sudip Mukherjee
2021-08-30 9:39 ` Andy Shevchenko
2021-08-30 11:28 ` Andy Shevchenko [this message]
2021-08-30 20:12 ` Guenter Roeck
2021-08-30 20:15 ` Linus Torvalds
2021-08-30 21:28 ` Peter Zijlstra
2021-08-31 11:04 ` Heiko Carstens
2021-08-30 20:32 ` Thomas Gleixner
2021-08-30 23:57 ` Thomas Gleixner
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='CAHp75VeSOMu+xvgv81BVc8R4U9MPB=50hgQHTULyTUKO6+Rh9A@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).