From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Abdelrahman Youssef <abdelrahmanyossef12@gmail.com>
Subject: Re: [PATCH master] sandbox: lds: fix relocation in read-only section warning
Date: Tue, 15 Oct 2024 08:55:45 +0200 [thread overview]
Message-ID: <172897534587.994906.6894445005837864849.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241014113540.2817987-1-a.fatoum@pengutronix.de>
On Mon, 14 Oct 2024 13:35:40 +0200, Ahmad Fatoum wrote:
> To address an "ELF has a LOAD segment with RWX permissions" warning
> during the sandbox build, the RO_DATA_SECTION was marked READONLY.
>
> At least with Debian GCC 12.2.0-14, this just brought us a different
> warning:
>
> /usr/bin/ld: common/memory.o: warning: relocation in read-only section `.initcall.9'
> /usr/bin/ld: warning: creating DT_TEXTREL in a PIE
>
> [...]
Applied, thanks!
[1/1] sandbox: lds: fix relocation in read-only section warning
https://git.pengutronix.de/cgit/barebox/commit/?id=9833da898934 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-10-15 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 11:35 Ahmad Fatoum
2024-10-15 6:55 ` Sascha Hauer [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=172897534587.994906.6894445005837864849.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=abdelrahmanyossef12@gmail.com \
--cc=barebox@lists.infradead.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