From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: failure building cacaoh-native
Date: Fri, 22 Oct 2010 08:42:39 +0200 [thread overview]
Message-ID: <20101022064239.GB3527@jama> (raw)
In-Reply-To: <4CC13039.4020002@nedap.com>
On Fri, Oct 22, 2010 at 08:33:29AM +0200, Jaap de Jong wrote:
> The same applies for cacaoh-openjdk-native.inc and probably also for
> cacaoh-cldc-native_0.98.bb
> Patch will be:
Can you send it as proper patch? Also please for previous cacaoh-native
patch.
http://wiki.openembedded.net/index.php/How_to_submit_a_patch_for_dummies
BTW: are you using libtool-2.4 or old libtool-2.2.6b? Because I
see this only since using libtool-2.4 and someone should check that this
patch wont break build for people using 2.2.6b.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-10-22 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 13:59 failure building cacaoh-native Jaap de Jong
2010-10-22 6:33 ` Jaap de Jong
2010-10-22 6:42 ` Martin Jansa [this message]
2010-10-22 8:11 ` Jaap de Jong
2010-10-22 20:45 ` Khem Raj
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=20101022064239.GB3527@jama \
--to=martin.jansa@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