From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix build failure of openjade using newer host
Date: Fri, 08 Jun 2012 11:33:44 +0100 [thread overview]
Message-ID: <1339151624.27075.0.camel@ted> (raw)
In-Reply-To: <cover.1338658338.git.otavio@ossystems.com.br>
On Sat, 2012-06-02 at 14:34 -0300, Otavio Salvador wrote:
> This has been catch when building denzil on a Debian sid host; the fix
> and build failure are documented on the patch. Please evaluate this
> patch for inclusion on denzil 1.2.1 release as this will be catch by
> users later.
>
> The following changes since commit e3113827810e98eb1b012f0b280fb917199704c1:
>
> webkit-gtk: Use glib as unicode backend to avoid browser crash (2012-05-30 17:37:58 +0100)
>
> are available in the git repository at:
> git://github.com/OSSystems/oe-core master
> https://github.com/OSSystems/oe-core/tree/HEAD
>
> Otavio Salvador (1):
> openjade: autoreconf to fix building on newer host systems
Why can't we run autoreconf instead of having the huge patch? This might
be the right answer but I'd like to understand the problem here a bit
more...
Cheers,
Richard
next prev parent reply other threads:[~2012-06-08 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 17:34 [PATCH 0/1] Fix build failure of openjade using newer host Otavio Salvador
2012-06-02 17:34 ` [PATCH 1/1] openjade: autoreconf to fix building on newer host systems Otavio Salvador
2012-06-11 17:34 ` Flanagan, Elizabeth
2012-06-12 0:23 ` Scott Garman
2012-06-12 13:14 ` Richard Purdie
2012-06-08 10:33 ` Richard Purdie [this message]
2012-06-08 11:52 ` [PATCH 0/1] Fix build failure of openjade using newer host Otavio Salvador
2012-06-12 13:13 ` Richard Purdie
2012-06-12 13:16 ` Otavio Salvador
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=1339151624.27075.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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