From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] RISC-V Build fixes
Date: Fri, 16 Mar 2018 20:40:23 -0700 [thread overview]
Message-ID: <cover.1521257828.git.raj.khem@gmail.com> (raw)
These packages were failing to build for qemuriscv64 world build
Some fixes are common, some are backports and some are already
submitted to respective upstream
The following changes since commit c94271d87d16323f920891344642f76dfb3c994f:
buildperf: measure the size of core-image-sato rootfs (2018-03-16 03:42:03 -0700)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/riscv64-fixes-3
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=kraj/riscv64-fixes-3
Khem Raj (5):
gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty
mtd-utils: Explicitly add pthread options to cflags
x264: Use updated gnu-config artifacts
python-numpy: Fix build for riscv64
dpkg: Backport riscv support
.../0001-arch-Add-support-for-riscv64-CPU.patch | 54 ++++++++
.../dpkg/dpkg/glibc2.5-sync_file_range.patch | 21 +++-
meta/recipes-devtools/dpkg/dpkg_1.18.24.bb | 1 +
meta/recipes-devtools/gcc/gcc-7.3.inc | 2 +-
meta/recipes-devtools/mtd/mtd-utils_git.bb | 2 +
.../files/0001-npy_cpu-Add-riscv-support.patch | 28 +++++
.../python-numpy/files/riscv64/_numpyconfig.h | 32 +++++
.../python-numpy/files/riscv64/config.h | 139 +++++++++++++++++++++
.../recipes-devtools/python-numpy/python-numpy.inc | 5 +
meta/recipes-multimedia/x264/x264_git.bb | 2 +
10 files changed, 280 insertions(+), 6 deletions(-)
create mode 100644 meta/recipes-devtools/dpkg/dpkg/0001-arch-Add-support-for-riscv64-CPU.patch
create mode 100644 meta/recipes-devtools/python-numpy/files/0001-npy_cpu-Add-riscv-support.patch
create mode 100644 meta/recipes-devtools/python-numpy/files/riscv64/_numpyconfig.h
create mode 100644 meta/recipes-devtools/python-numpy/files/riscv64/config.h
--
2.16.2
next reply other threads:[~2018-03-17 3:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 3:40 Khem Raj [this message]
2018-03-17 3:40 ` [PATCH 1/5] gcc: Do not use --with-linker-hash-style if LINKER_HASH_STYLE is empty Khem Raj
2018-03-17 3:40 ` [PATCH 2/5] mtd-utils: Explicitly add pthread options to cflags Khem Raj
2018-03-17 3:40 ` [PATCH 3/5] x264: Use updated gnu-config artifacts Khem Raj
2018-03-19 11:36 ` Burton, Ross
2018-03-19 15:32 ` Khem Raj
2018-03-19 16:54 ` Khem Raj
2018-03-19 17:23 ` Burton, Ross
2018-03-19 17:48 ` Khem Raj
2018-03-19 18:38 ` Burton, Ross
2018-03-17 3:40 ` [PATCH 4/5] python-numpy: Fix build for riscv64 Khem Raj
2018-03-17 3:40 ` [PATCH 5/5] dpkg: Backport riscv support Khem Raj
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=cover.1521257828.git.raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.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