From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/23] support/config-fragments/autobuild: remove Blackfin configuration
Date: Thu, 5 Apr 2018 22:38:23 +0200 [thread overview]
Message-ID: <20180405223823.37e9e07a@windsurf> (raw)
In-Reply-To: <20180405202933.GB22364@scaer>
Hello,
On Thu, 5 Apr 2018 22:29:33 +0200, Yann E. MORIN wrote:
> > -# Test a noMMU toolchain with dynamic library support
> > -support/config-fragments/autobuild/br-bfin-full.config,x86_64
>
> Do we plan on adding back another noMMU target with dynamic library
> support instead of that one?
We don't have any other noMMU target that supports dynamic library
support currently. FDPIC support on ARM is being worked on upstream,
but I don't think it's ready yet.
Otherwise, there is FDPIC support for SH2, but we don't have support
for this either.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-05 20:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 19:50 [Buildroot] [PATCH 00/23] Remove Blackfin architecture Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 01/23] support/config-fragments/autobuild: remove Blackfin configuration Thomas Petazzoni
2018-04-05 20:29 ` Yann E. MORIN
2018-04-05 20:38 ` Thomas Petazzoni [this message]
2018-04-05 20:47 ` Yann E. MORIN
2018-04-05 19:50 ` [Buildroot] [PATCH 02/23] configs/gdb_bfin_bf512: remove defconfig Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 03/23] arch: remove Blackfin architecture Thomas Petazzoni
2018-04-05 20:39 ` Yann E. MORIN
2018-04-05 19:50 ` [Buildroot] [PATCH 04/23] arch: drop BR2_BINFMT_FLAT_SEP_DATA support Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 05/23] boot/uboot: remove Blackfin related code Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 06/23] linux: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 07/23] toolchain, gcc, gdb, binutils, uclibc: remove Blackfin code Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 08/23] gcc: remove Blackfin patches Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 09/23] binutils: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 10/23] package: remove Blackfin related code Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 11/23] cairo: remove Blackfin related patch Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 12/23] ffmpeg: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 13/23] gdb: remove Blackfin patch Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 14/23] gdb/7.10: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 15/23] graphite2: remove Blackfin related patch Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 16/23] icu: remove Blackfin patch Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 17/23] libselinux: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 18/23] libpng: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 19/23] libsemanage: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 20/23] libsepol: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 21/23] p7zip: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 22/23] wayland: " Thomas Petazzoni
2018-04-05 19:50 ` [Buildroot] [PATCH 23/23] php: " 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=20180405223823.37e9e07a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox