Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Max Krummenacher <max.oss.09@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-java][PATCH 6/7] adding a README.nonworking
Date: Mon, 16 Feb 2015 22:55:33 +0100	[thread overview]
Message-ID: <1424123733-16696-7-git-send-email-max.oss.09@gmail.com> (raw)
In-Reply-To: <1424123733-16696-1-git-send-email-max.oss.09@gmail.com>

While testing commit 'java-library: inherit allarch' I found some recipes
throwing errors in do_compile.
Document this in README.nonworking.

Signed-off-by: Max Krummenacher <max.oss.09@gmail.com>
---
 README.nonworking | 6 ++++++
 1 file changed, 6 insertions(+)
 create mode 100644 README.nonworking

diff --git a/README.nonworking b/README.nonworking
new file mode 100644
index 0000000..11ecaeb
--- /dev/null
+++ b/README.nonworking
@@ -0,0 +1,6 @@
+At least the following recipes are currently not working:
+
+The recipes jaxme and xom currently don't build with compiler errors.
+
+jaxen, dom4j, commons-jxpath, jdom, commons-configuration depend directly
+or indirectly on jaxme and/or xom and thus are unbildable.
-- 
1.9.3



  parent reply	other threads:[~2015-02-16 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 21:55 [meta-java][PATCH 0/7] Allow build for multiple ARCH in the same builddir Max Krummenacher
2015-02-16 21:55 ` [meta-java][PATCH 1/7] cleanup whitespace in tasks Max Krummenacher
2015-02-16 21:55 ` [meta-java][PATCH 2/7] licence: add missing LIC_FILES_CHKSUM Max Krummenacher
2015-02-16 21:55 ` [meta-java][PATCH 3/7] rxtx: use autotools-brokensep Max Krummenacher
2015-02-16 21:55 ` [meta-java][PATCH 4/7] java-library: inherit allarch Max Krummenacher
2015-02-16 21:55 ` [meta-java][PATCH 5/7] antlr: fix override for native build Max Krummenacher
2015-02-16 21:55 ` Max Krummenacher [this message]
2015-02-16 23:13 ` [meta-java][PATCH 0/7] Allow build for multiple ARCH in the same builddir Otavio Salvador
2015-02-17  8:38   ` Max Krummenacher

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=1424123733-16696-7-git-send-email-max.oss.09@gmail.com \
    --to=max.oss.09@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox