Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libpng 1.6.13: fix build for aarch64
Date: Mon, 3 Nov 2014 11:38:02 -0600	[thread overview]
Message-ID: <5457BD7A.9020806@windriver.com> (raw)
In-Reply-To: <9D7813D1-1BDC-4B46-BE6D-CF05049314E5@linaro.org>

On 11/3/14, 9:24 AM, Koen Kooi wrote:
>
> Op 3 nov. 2014, om 13:10 heeft Richard Purdie <richard.purdie@linuxfoundation.org> het volgende geschreven:
>
>> On Mon, 2014-11-03 at 13:06 +0100, Koen Kooi wrote:
>>>> Op 3 nov. 2014, om 12:30 heeft Burton, Ross <ross.burton@intel.com> het volgende geschreven:
>>>>
>>>>
>>>> On 3 November 2014 11:27, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>>>> Last night I was looking at my "post-1.7" tag and the number of aarch64 patches there.   Kai, did you continue work on that staging branch for all of the aarch64 patches that were being posted?
>>>>
>>>> What does that have to do with this patch?
>>>>
>>>> Kai was collecting patches that were sent to oe-core, and this may have been one of them.
>>>
>>> Is this some new requirement for OE-core patches?
>>
>> Its someone being helpful and trying to consolidate a topic branch and
>> test things before it gets merged.
>>
>> So its not a new requirement but it is helpful and appreciated.
>
> It's been over a month and libpng is still broken, so I refuse to classify this new process as 'helpful' or as 'appreciated' at this point.
>
> If this continues can the person doing such a branch reply to patches intended for it saying they will or won't be queued? And please run the patches without such a reply through the regular process. That would be both helpful and appreciated.

We've been attempting to aggregate what we (WR) can in:

  http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=kangkai/qemuarm64

But as it's unofficial and we're simply trying to keep the patches we know of 
together..  you'll have to be patient.  The first order of business is getting a 
functional qemuarm64.. it's MOSTLY there, but we're having toolchain issues and 
other things that are simply higher priority for us.

As for libpng, we have a different version of the patch in that branch...  it 
was enough to get around the problem in question, but may not be the correct fix.

--Mark

> --
> Koen Kooi
> Builds and Baselines | Release Manager
> Linaro.org | Open source software for ARM SoCs
>
>
>



  parent reply	other threads:[~2014-11-03 17:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 12:12 [PATCH] libpng 1.6.13: fix build for aarch64 Koen Kooi
2014-11-03  9:57 ` Koen Kooi
2014-11-03 10:25   ` Burton, Ross
2014-11-03 11:27     ` Koen Kooi
2014-11-03 11:30       ` Burton, Ross
2014-11-03 12:06         ` Koen Kooi
2014-11-03 12:10           ` Richard Purdie
2014-11-03 15:24             ` Koen Kooi
2014-11-03 16:08               ` Burton, Ross
2014-11-03 17:13                 ` Koen Kooi
2014-11-03 17:33                   ` Burton, Ross
2014-11-03 16:08               ` Richard Purdie
2014-11-03 17:38               ` Mark Hatle [this message]
2014-11-03 17:44                 ` Burton, Ross
2014-11-04  2:30                   ` Kang Kai
2014-12-12  8:42 ` Koen Kooi

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=5457BD7A.9020806@windriver.com \
    --to=mark.hatle@windriver.com \
    --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