From: Max Filippov <jcmvbkbc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 00/10] xtensa: add -mtext-section-literals to xtensa ABI
Date: Sun, 30 Mar 2014 21:57:44 +0400 [thread overview]
Message-ID: <1396202274-5109-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hi Thomas,
this series is the second part of fixes for building huge sources, like
wireshark or mplayer: adding trampolines support to binutils allows
assembling of such files, but with literals placed into separate section
build fails at the linking step.
First patch allows building uclibc with -mtext-section-literals, it is
posted to the uclibc list, but not reviewed/checked in yet.
Second patch adds -mtext-section-literals flag to xtensa ABI.
Remaining patches revert -mtext-section-literals additions to individual
packages.
Changes v2 -> v3:
- drop patch 3 and revert individual commits that added
-mtext-section-literals flag instead
Changes v1 -> v2:
- add comment to XTENSA_ABI variable explaining -mtext-section-literals usage
- remove -mtext-section-literals from individual package *.mk's
Max Filippov (10):
uclibc: add missing .literal_position directives
Makefile.in: add -mtext-section-literals to xtensa ABI
Revert "civetweb: fix build for xtensa"
Revert "ffmpeg: fix build for xtensa"
Revert "gst-ffmpeg: fix build for xtensa"
Revert "gst1-libav: fix build for xtensa"
Revert "lmbench: fix build for xtensa"
Revert "php: fix build for xtensa"
Revert "sqlcipher: fix build for xtensa"
Revert "xtensa: sqlite requires special compiler option"
package/Makefile.in | 11 +++-
package/civetweb/civetweb.mk | 3 --
package/ffmpeg/ffmpeg.mk | 8 ---
package/gstreamer/gst-ffmpeg/gst-ffmpeg.mk | 8 ---
package/gstreamer1/gst1-libav/gst1-libav.mk | 8 ---
package/lmbench/lmbench.mk | 4 --
package/php/php.mk | 4 --
package/sqlcipher/sqlcipher.mk | 4 --
package/sqlite/sqlite.mk | 4 --
...-add-missing-.literal_position-directives.patch | 62 ++++++++++++++++++++++
10 files changed, 72 insertions(+), 44 deletions(-)
create mode 100644 package/uclibc/7bf35c8b7d4a1f97174eb49f47f33946b282114c/uclibc-0001-xtensa-add-missing-.literal_position-directives.patch
--
1.8.1.4
next reply other threads:[~2014-03-30 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 17:57 Max Filippov [this message]
2014-03-30 17:57 ` [Buildroot] [PATCH v3 01/10] uclibc: add missing .literal_position directives Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 02/10] Makefile.in: add -mtext-section-literals to xtensa ABI Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 03/10] Revert "civetweb: fix build for xtensa" Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 04/10] Revert "ffmpeg: " Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 05/10] Revert "gst-ffmpeg: " Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 06/10] Revert "gst1-libav: " Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 07/10] Revert "lmbench: " Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 08/10] Revert "php: " Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 09/10] Revert "sqlcipher: " Max Filippov
2014-03-30 17:57 ` [Buildroot] [PATCH v3 10/10] Revert "xtensa: sqlite requires special compiler option" Max Filippov
2014-03-31 3:26 ` [Buildroot] [PATCH v3 00/10] xtensa: add -mtext-section-literals to xtensa ABI Baruch Siach
2014-04-03 19:39 ` 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=1396202274-5109-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.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