> Op 22 sep. 2014, om 14:12 heeft Koen Kooi het volgende
> geschreven:
>
> The configure override was too restrictive, it needed both 'arm' and 'neon'
> to trigger, which breaks on aarch64. Since TUNE_FEATURES is the only
> qualifier that matters, drop the 'arm' override.
>
> Buildtested for
On 2014?11?04? 01:44, Burton, Ross wrote:
On 3 November 2014 17:38, Mark Hatle wrote:
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
On 3 November 2014 17:38, Mark Hatle wrote:
> 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
On 11/3/14, 9:24 AM, Koen Kooi wrote:
Op 3 nov. 2014, om 13:10 heeft Richard Purdie
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 het
volgende geschreven:
On 3 November 2014 11:27, Koen Kooi wrote:
Last night I
On 3 November 2014 17:13, Koen Kooi wrote:
> Most likely not because we already have meta-aarch64 for the toolchain and
> kernel support. But aside from that, the past few *years* it wasn't a
> problem to get aarch64 related patches merged into OE-core, so why is there
> suddenly such a problem n
> Op 3 nov. 2014, om 17:08 heeft Burton, Ross het
> volgende geschreven:
>
>
> On 3 November 2014 15:24, Koen Kooi wrote:
> 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.
>
> Remember that 1.7 was
On Mon, 2014-11-03 at 16:24 +0100, Koen Kooi wrote:
> Op 3 nov. 2014, om 13:10 heeft Richard Purdie
> 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 het
> >>> volgende geschreven:
> >>>
> >>>
> >>> On 3 Nov
On 3 November 2014 15:24, Koen Kooi wrote:
> 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.
Remember that 1.7 was frozen solid for several weeks of that month, so no
it wouldn't have been merged in th
Op 3 nov. 2014, om 13:10 heeft Richard Purdie
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 het
>>> volgende geschreven:
>>>
>>>
>>> On 3 November 2014 11:27, Koen Kooi wrote:
Last night I was looking at
On Mon, 2014-11-03 at 13:06 +0100, Koen Kooi wrote:
> > Op 3 nov. 2014, om 12:30 heeft Burton, Ross het
> > volgende geschreven:
> >
> >
> > On 3 November 2014 11:27, Koen Kooi wrote:
> > > Last night I was looking at my "post-1.7" tag and the number of aarch64
> > > patches there. Kai, did
> Op 3 nov. 2014, om 12:30 heeft Burton, Ross het
> volgende geschreven:
>
>
> On 3 November 2014 11:27, Koen Kooi 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 aar
On 3 November 2014 11:27, Koen Kooi 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
> Op 3 nov. 2014, om 11:25 heeft Burton, Ross het
> volgende geschreven:
>
> On 3 November 2014 09:57, Koen Kooi wrote:
> ping
>
> 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 aa
On 3 November 2014 09:57, Koen Kooi wrote:
> ping
>
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?
Ross
--
ping
> Op 22 sep. 2014, om 14:12 heeft Koen Kooi het volgende
> geschreven:
>
> The configure override was too restrictive, it needed both 'arm' and 'neon'
> to trigger, which breaks on aarch64. Since TUNE_FEATURES is the only
> qualifier that matters, drop the 'arm' override.
>
> Buildteste
The configure override was too restrictive, it needed both 'arm' and 'neon' to
trigger, which breaks on aarch64. Since TUNE_FEATURES is the only qualifier
that matters, drop the 'arm' override.
Buildtested for 'genericarmv8' and 'qemux86' machines.
Signed-off-by: Koen Kooi
---
meta/recipes-mu
16 matches
Mail list logo
