From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch: drop now useless support for FDPIC
Date: Mon, 21 May 2018 22:22:48 +0200 [thread overview]
Message-ID: <20180521202248.GE3453@scaer> (raw)
In-Reply-To: <20180521215840.3ca959f5@windsurf>
Thomas, All,
On 2018-05-21 21:58 +0200, Thomas Petazzoni spake thusly:
> On Mon, 21 May 2018 18:17:06 +0200, Yann E. MORIN wrote:
> > Now that we dropped support for blackfin, we no longer have any
> > architecture that supports FDPIC, so BR2_ARCH_HAS_FDPIC_SUPPORT
> > is never selected, so we can't select BR2_BINFMT_FDPIC.
> >
> > Drop all of that now.
> >
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
>
> When I dropped Blackfin support, I wondered about dropping FDPIC
> support. But I know people are working on FDPIC support on ARM, so I
> wasn't sure it was useful to drop it now, and re-add it later on.
Oh, well, I was just "Eh, this is dead code, it's gonna birot. Better
burry it now sit does not stink too much yet..." ;-)
But we can always git-revert that code later when/if FDPIC gets
resurected for another arch...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-05-21 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 16:17 [Buildroot] [PATCH] arch: drop now useless support for FDPIC Yann E. MORIN
2018-05-21 16:33 ` Baruch Siach
2018-05-21 19:56 ` Waldemar Brodkorb
2018-05-21 19:58 ` Thomas Petazzoni
2018-05-21 20:22 ` Yann E. MORIN [this message]
2018-07-01 13:19 ` Thomas Petazzoni
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=20180521202248.GE3453@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.