From: Arvind Sankar <nivedita@alum.mit.edu>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.9-rc7
Date: Sat, 3 Oct 2020 11:18:03 -0400 [thread overview]
Message-ID: <20201003151803.GA614088@rani.riverdale.lan> (raw)
In-Reply-To: <CAEJqkgiq5ss9S4edHGb5x+YjhODF1HqBW-5qjHA8=AFnhX2tSQ@mail.gmail.com>
On Sat, Oct 03, 2020 at 04:23:15PM +0200, Gabriel C wrote:
> Am Mo., 28. Sept. 2020 um 00:00 Uhr schrieb Linus Torvalds
> <torvalds@linux-foundation.org>:
> Hello,
>
> > Shortlog appended, but what I really hope you all will do is to give
> > it a nice good testing. One extra week or rc kernels will help, but
> > only if people actually try this out.
> >
> > So.. Please?
>
> I'm a bit late testing, but the first thing I noticed is this warning:
>
> ld: arch/x86/boot/compressed/head_64.o: warning: relocation in
> read-only section `.head.text'
> ld: warning: creating DT_TEXTREL in a PIE
>
> The compiler is gcc 9.2.1 20200215, with default PIE enabled, ld version 2.35.1.
> The config used is the 64bit defconfig.
>
> Best Regards,
>
> Gabriel C.
You can ignore the warning for now, it is harmless: it's always been
there, but binutils-2.35 has enabled the warning by default. There are
patches in tip that should make this go away for v5.10.
Thanks.
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=ld/NEWS;hb=refs/tags/binutils-2_35_1
* Add a configure option, --enable-textrel-check=[no|yes|warning|error],
to decide what ELF linker should do by default with DT_TEXTREL in an
executable or shared library. Default to yes for Linux/x86 targets.
prev parent reply other threads:[~2020-10-03 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 21:56 Linus Torvalds
2020-09-28 3:17 ` ..and it built and boots without a fuss! " Bhaskar Chowdhury
2020-10-03 14:23 ` Gabriel C
2020-10-03 15:18 ` Arvind Sankar [this message]
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=20201003151803.GA614088@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--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
all inboxes | Powered by JetHome®