From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] poco: disable for or1k, not supported
Date: Thu, 23 Feb 2017 19:32:21 +0100 [thread overview]
Message-ID: <20170223183221.GC12810@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170223182152.GA14039@waldemar-brodkorb.de>
Hi,
drop this, haven't seen Baruch's patch :/
Note to myself, first check mailinglist, then start looking into
autobuild errors ;)
best regards
Waldemar
Waldemar Brodkorb wrote,
> Fixes:
> http://autobuild.buildroot.net/results/5b3fd6d4a7bdefadba89fdb53de4ba786f4df9e2
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> package/poco/Config.in | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/poco/Config.in b/package/poco/Config.in
> index dfdc8d1..b3b247f 100644
> --- a/package/poco/Config.in
> +++ b/package/poco/Config.in
> @@ -5,7 +5,7 @@ config BR2_PACKAGE_POCO
> depends on BR2_TOOLCHAIN_HAS_THREADS
> depends on !BR2_STATIC_LIBS # dlopen()
> depends on !(BR2_arc || BR2_bfin || BR2_microblaze || BR2_mipsel \
> - || BR2_xtensa)
> + || BR2_or1k || BR2_xtensa)
> select BR2_PACKAGE_ZLIB
> select BR2_PACKAGE_PCRE
> help
> @@ -65,4 +65,4 @@ comment "poco needs a toolchain w/ wchar, threads, C++, dynamic library"
> depends on !BR2_USE_WCHAR || !BR2_INSTALL_LIBSTDCPP \
> || !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
> depends on !(BR2_arc || BR2_bfin || BR2_microblaze || BR2_mipsel \
> - || BR2_xtensa)
> + || BR2_or1k || BR2_xtensa)
> --
> 2.1.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
prev parent reply other threads:[~2017-02-23 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 18:21 [Buildroot] [PATCH] poco: disable for or1k, not supported Waldemar Brodkorb
2017-02-23 18:32 ` Waldemar Brodkorb [this message]
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=20170223183221.GC12810@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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