From: Wolfram Sang <wsa@the-dreams.de>
To: ptxdist@pengutronix.de
Cc: Wolfram Sang <wsa@the-dreams.de>
Subject: [ptxdist] [PATCH] platform: toolchain: mention that version for libc is mandatory
Date: Sat, 7 Nov 2015 15:34:01 +0100 [thread overview]
Message-ID: <1446906841-11119-1-git-send-email-wsa@the-dreams.de> (raw)
If it is not defined, build breaks:
---------------------------
target: glibc.targetinstall
---------------------------
ptxdist: error: ptxd_make_xpkg_init: please define <PKG>_VERSION
or:
----------------------------
target: uclibc.targetinstall
----------------------------
ptxdist: error: ptxd_make_xpkg_init: please define <PKG>_VERSION
I am not the first one to experience this:
https://www.mail-archive.com/oselas@community.pengutronix.de/msg02033.html
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
---
platforms/toolchain.in | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/platforms/toolchain.in b/platforms/toolchain.in
index 2807bc7..3f0b2bb 100644
--- a/platforms/toolchain.in
+++ b/platforms/toolchain.in
@@ -49,9 +49,7 @@ config GLIBC_VERSION
prompt "check for specific glibc version"
default "2.18"
help
- Specify the glibc version this BSP shall be built with. This information
- is used to guess the toolchain path if you use "ptxdist toolchain"
- without an argument.
+ Mandatory: Specify the glibc version this BSP shall be built with.
endif
if LIBC_UCLIBC
@@ -60,9 +58,7 @@ config UCLIBC_VERSION
prompt "check for specific uClibc version"
default "0.9.33.2"
help
- Specify the uClibc version this BSP shall be built with. This information
- is used to guess the toolchain path if you use "ptxdist toolchain"
- without an argument.
+ Mandatory: Specify the uClibc version this BSP shall be built with.
endif
config GNU_TARGET
--
2.1.4
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2015-11-07 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1446906841-11119-1-git-send-email-wsa@the-dreams.de \
--to=wsa@the-dreams.de \
--cc=ptxdist@pengutronix.de \
/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