From: Ben Wolsieffer <ben.wolsieffer@hefring.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/4] Revert "arch: drop now useless support for FDPIC"
Date: Wed, 3 Aug 2022 17:04:30 -0400 [thread overview]
Message-ID: <Yuri3sT/jSnhKBSs@hefring> (raw)
In-Reply-To: <20220803001203.3b341222@windsurf>
On Wed, Aug 03, 2022 at 12:12:03AM +0200, Thomas Petazzoni wrote:
> Hello Ben,
>
> On Tue, 2 Aug 2022 16:21:39 -0400
> Ben Wolsieffer <ben.wolsieffer@hefring.com> wrote:
>
> > @@ -418,6 +421,7 @@ endif
> > choice
> > prompt "Target Binary Format"
> > default BR2_BINFMT_ELF if BR2_USE_MMU
> > + default BR2_BINFMT_FDPIC if BR2_ARCH_HAS_FDPIC_SUPPORT
>
> This default means that existing defconfigs for ARM noMMU, which
> currently use FLAT binaries will "automatically" switch to FDPIC.
>
I didn't look too closely at this revert before, but yes, it probably
doesn't make sense to enable it by default when adding support for FDPIC
to an existing architecture.
> On another topic, I am wondering what happens with external toolchains?
> For example at https://toolchains.bootlin.com/releases_armv7m.html we
> have ARMv7-M toolchains that produce FLAT binaries. So probably it
> means that the toolchain-external-bootlin package needs to be amended
> to only offer the existing ARMv7-M toolchain when FLAT binaries are
> selected.
>
> I haven't really thought of all the implications, but to me it seems
> like the case of external toolchains should be considered, to see what
> is the impact of the FDPIC support.
The fact that FDPIC requires a certain toolchain target unfortunately
means that the existing prebuilt toolchains can't support it. Perhaps I
should add a BR2_TOOLCHAIN_HAS_FDPIC_SUPPORT option?
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-03 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 20:21 [Buildroot] [PATCH v2 0/4] Add support for FDPIC binaries on ARM Ben Wolsieffer
2022-08-02 20:21 ` [Buildroot] [PATCH v2 1/4] Revert "arch: drop now useless support for FDPIC" Ben Wolsieffer
2022-08-02 22:12 ` Thomas Petazzoni via buildroot
2022-08-03 21:04 ` Ben Wolsieffer [this message]
2022-08-02 20:21 ` [Buildroot] [PATCH v2 2/4] arch/arm: add support for FDPIC Ben Wolsieffer
2022-08-02 22:13 ` Thomas Petazzoni via buildroot
2022-08-03 20:54 ` Ben Wolsieffer
2022-08-02 20:21 ` [Buildroot] [PATCH v2 3/4] boot/uboot: pass -mno-fdpic if FDPIC is enabled Ben Wolsieffer
2022-08-02 22:15 ` Thomas Petazzoni via buildroot
2022-08-03 21:07 ` Ben Wolsieffer
2022-08-02 20:21 ` [Buildroot] [PATCH v2 4/4] linux: " Ben Wolsieffer
2022-08-02 22:08 ` [Buildroot] [PATCH v2 0/4] Add support for FDPIC binaries on ARM Thomas Petazzoni via buildroot
2022-08-03 20:52 ` Ben Wolsieffer
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=Yuri3sT/jSnhKBSs@hefring \
--to=ben.wolsieffer@hefring.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.