From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/janet: needs MMU
Date: Mon, 27 Nov 2023 22:28:22 +0100 [thread overview]
Message-ID: <20231127212822.1060094-1-fontaine.fabrice@gmail.com> (raw)
janet unconditionally uses fork since version 1.32.0 and
https://github.com/janet-lang/janet/commit/4b8c1ac2d2d5c13d7c8592fd6d94b34a6a8b3549
resulting in the following build failure since bump to version 1.32.1 in
commit c87abf01a9153a2b2fe6c046fa83c86db92d79a7:
janet.c:(.text+0x19bbc): undefined reference to `fork'
Fixes:
- http://autobuild.buildroot.org/results/f0771fc6c9905d3a6d60ce245df585b3c6096f7f
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/janet/Config.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/janet/Config.in b/package/janet/Config.in
index 7b78c14bf4..bb4bf462aa 100644
--- a/package/janet/Config.in
+++ b/package/janet/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_JANET
bool "janet"
+ depends on BR2_USE_MMU # fork()
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # C11/stdatomic.h
help
Janet is a functional and imperative programming language.
@@ -11,4 +12,5 @@ config BR2_PACKAGE_JANET
https://janet-lang.org/
comment "janet needs a toolchain w/ gcc >= 4.9"
+ depends on BR2_USE_MMU
depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
--
2.42.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-11-27 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 21:28 Fabrice Fontaine [this message]
2023-11-28 16:12 ` [Buildroot] [PATCH 1/1] package/janet: needs MMU Yann E. MORIN
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=20231127212822.1060094-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.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 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.