From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Matt Weber <matthew.weber@collins.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/paxtest: disable on microblaze
Date: Tue, 21 Jun 2022 20:36:25 +0200 [thread overview]
Message-ID: <20220621183625.1395189-1-fontaine.fabrice@gmail.com> (raw)
Disable paxtest on microblaze to avoid the following build failure:
shlibtest.c:9:1: error: requested alignment '65536' exceeds object file maximum 32768
9 | char shbss[PAGE_SIZE_MAX] __pagealigned;
| ^~~~
Updating second patch to set PAGE_SIZE_MAX to 32768 will raise another
build failure:
/tmp/cccMSYDr.s: Assembler messages:
/tmp/cccMSYDr.s: Error: PC relative branch to label buf which is not in the instruction space
Fixes:
- http://autobuild.buildroot.org/results/aba489143b4017617f67c1012bba1f4687708380
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/paxtest/Config.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/paxtest/Config.in b/package/paxtest/Config.in
index 1e09820ba3..565c45cc19 100644
--- a/package/paxtest/Config.in
+++ b/package/paxtest/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_PAXTEST
bool "paxtest"
+ depends on !BR2_microblaze
# No UCLIBC or MUSL because __NO_A_OUT_SUPPORT
depends on BR2_TOOLCHAIN_USES_GLIBC
help
@@ -8,4 +9,5 @@ config BR2_PACKAGE_PAXTEST
http://pax.grsecurity.net/docs
comment "paxtest needs a glibc toolchain"
+ depends on !BR2_microblaze
depends on !BR2_TOOLCHAIN_USES_GLIBC
--
2.35.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-06-21 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 18:36 Fabrice Fontaine [this message]
2022-06-25 6:40 ` [Buildroot] [PATCH 1/1] package/paxtest: disable on microblaze Peter Korsgaard
2022-07-22 6:16 ` Peter Korsgaard
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=20220621183625.1395189-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.org \
--cc=matthew.weber@collins.com \
/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.