From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] uclibc: add option to specify config fragments
Date: Sat, 21 Mar 2015 00:22:06 +0100 [thread overview]
Message-ID: <20150320232206.GI3979@free.fr> (raw)
In-Reply-To: <1424003638-21689-4-git-send-email-bos@je-eigen-domein.nl>
Floris, All,
On 2015-02-15 13:33 +0100, Floris Bos spake thusly:
> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
> ---
> package/uclibc/Config.in | 6 ++++++
> package/uclibc/uclibc.mk | 1 +
> 2 files changed, 7 insertions(+)
>
> diff --git a/package/uclibc/Config.in b/package/uclibc/Config.in
> index aa99a6f..1be9195 100644
> --- a/package/uclibc/Config.in
> +++ b/package/uclibc/Config.in
> @@ -53,6 +53,12 @@ config BR2_UCLIBC_CONFIG
> See also docs/README in this package.
> If unsure, use the default.
>
> +config BR2_UCLIBC_CONFIG_FRAGMENT_FILES
> + string "Additional uClibc configuration fragment files"
> + help
> + A space-seperated list of configuration fragment files,
separated Well... you know the tune, now. ;-)
Otherwise, OK:
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> + that will be merged to the main uClibc configuration file.
> +
> config BR2_TOOLCHAIN_BUILDROOT_LARGEFILE
> bool "Enable large file (files > 2 GB) support"
> select BR2_LARGEFILE
> diff --git a/package/uclibc/uclibc.mk b/package/uclibc/uclibc.mk
> index 40e6c6c..9d73b39 100644
> --- a/package/uclibc/uclibc.mk
> +++ b/package/uclibc/uclibc.mk
> @@ -38,6 +38,7 @@ UCLIBC_CONFIG_FILE = $(call qstrip,$(BR2_UCLIBC_CONFIG))
> endif
>
> UCLIBC_KCONFIG_FILE = $(UCLIBC_CONFIG_FILE)
> +UCLIBC_KCONFIG_FRAGMENT_FILES = $(call qstrip,$(BR2_UCLIBC_CONFIG_FRAGMENT_FILES))
>
> UCLIBC_KCONFIG_OPTS = \
> $(UCLIBC_MAKE_FLAGS) \
> --
> 1.9.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-03-20 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 12:33 [Buildroot] [PATCH 1/5] kconfig-package: add support for config fragments Floris Bos
2015-02-15 12:33 ` [Buildroot] [PATCH 2/5] linux: add option to specify " Floris Bos
2015-03-20 23:15 ` Yann E. MORIN
2015-02-15 12:33 ` [Buildroot] [PATCH 3/5] busybox: " Floris Bos
2015-03-20 23:20 ` Yann E. MORIN
2015-02-15 12:33 ` [Buildroot] [PATCH 4/5] uclibc: " Floris Bos
2015-03-20 23:22 ` Yann E. MORIN [this message]
2015-02-15 12:33 ` [Buildroot] [PATCH 5/5] barebox: " Floris Bos
2015-03-20 23:23 ` Yann E. MORIN
2015-03-20 23:11 ` [Buildroot] [PATCH 1/5] kconfig-package: add support for " Yann E. MORIN
2015-03-21 14:57 ` Arnout Vandecappelle
2015-03-23 8:09 ` Jeremy Rosen
2015-03-23 18:31 ` Yann E. MORIN
2015-03-23 21:41 ` Arnout Vandecappelle
2015-03-20 23:14 ` 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=20150320232206.GI3979@free.fr \
--to=yann.morin.1998@free.fr \
--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