From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: luca.ceresoli@bootlin.com, michal.simek@amd.com,
Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v2 2/2] board/versal: fix atf build failure
Date: Tue, 1 Aug 2023 23:26:04 +0200 [thread overview]
Message-ID: <20230801232604.61fcdd16@windsurf> (raw)
In-Reply-To: <20230731154739.1371164-2-neal.frager@amd.com>
Hello Neal,
On Mon, 31 Jul 2023 16:47:39 +0100
Neal Frager via buildroot <buildroot@buildroot.org> wrote:
> Binutils 2.39 now warns when a segment has RXW permissions:
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ba951afb99912da01a6e8434126b8fac7aa75107
>
> This causes the following build error:
> aarch64-buildroot-linux-gnu-ld: bl31.elf has a LOAD segment with RWX
> permissions.
>
> This patch applies the upstream boot/arm-trusted-firmware/v2.6 patch already
> included with buildroot to solve the problem.
>
> Fixes: https://developer.trustedfirmware.org/T996
Same comment as for PATCH 1/2, so I changed to:
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/4749556395 (versal_vck190)
when applying. Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-01 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 15:47 [Buildroot] [PATCH v2 1/2] board/zynqmp: fix atf build failure Neal Frager via buildroot
2023-07-31 15:47 ` [Buildroot] [PATCH v2 2/2] board/versal: " Neal Frager via buildroot
2023-08-01 21:26 ` Thomas Petazzoni via buildroot [this message]
2023-08-01 21:25 ` [Buildroot] [PATCH v2 1/2] board/zynqmp: " Thomas Petazzoni via buildroot
2023-08-02 4:06 ` Frager, Neal via buildroot
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=20230801232604.61fcdd16@windsurf \
--to=buildroot@buildroot.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.com \
/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.