ping.
Regards,
Jagadeesh
From: Krishnanjanappa, Jagadeesh
Sent: Wednesday, April 15, 2015 1:53 PM
To: openembedded-core@lists.openembedded.org
Cc: Krishnanjanappa, Jagadeesh
Subject: [OE-core][PATCH] qt4-embedded: add checking for AArch64 ilp32
From
ping, Is it going to be merged into fido branch?
Regards,
Jagadeesh
From: Krishnanjanappa, Jagadeesh
Sent: Tuesday, April 14, 2015 3:08 PM
To: openembedded-core@lists.openembedded.org
Cc: Krishnanjanappa, Jagadeesh
Subject: [OE-core][PATCH] ghostscript
From: "Krishnanjanappa, Jagadeesh"
1. Cross-compiling qt4-embedded and qt4-x11-free applications for AArch64 ilp32
(both big and little endian) fails with below error,
(snip)
In file included from
../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.h:31:0,
From: "Krishnanjanappa, Jagadeesh"
ghostscript application fails to fetch objarch.h file while building for armeb.
The fetch failure is due to absence of this file in the default set of
directories that the OpenEmbedded build system searches (i.e FILESPATH)
for patches and files.
arander
Sent: Wednesday, April 8, 2015 7:13 PM
To: Krishnanjanappa, Jagadeesh
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] dpkg: add triplet entry to fix build error for
armeb
* Krishnanjanappa, Jagadeesh
[150408 15:33]:
> 2. Added INC_PR to PR to have an up
From: "Krishnanjanappa, Jagadeesh"
Cross-compling dpkg application for armeb fails with below error
during configure task,
(snip)
configure:23141: checking dpkg cpu type
configure:23148: result: armeb
configure:23150: WARNING: armeb not found in cputable
configure:23162: che
From: "Krishnanjanappa, Jagadeesh"
1. Cross-compling dpkg application for armeb fails with below error
during configure task,
(snip)
configure:23141: checking dpkg cpu type
configure:23148: result: armeb
configure:23150: WARNING: armeb not found in cputable
From: "Krishnanjanappa, Jagadeesh"
Building both 32-bit and 64-bit binaries in valgrind at a time would
lead to following QA issue as below,
(snip)
ERROR: QA Issue: Architecture did not match (62 to 3) on
${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgr
n behalf of Mark Hatle
Sent: Friday, April 3, 2015 8:42 PM
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] valgrind: Add INSANE_SKIP of arch for valgrind
and valgrind-dbg
On 4/3/15 9:57 AM, Krishnanjanappa, Jagadeesh wrote:
>> what is the point of packaging files f
use/13.2/x86_64/valgrind-3.10.0-1.1.x86_64.html
Regards,
Jagadeesh
From: Khem Raj
Sent: Friday, April 3, 2015 8:28 AM
To: Krishnanjanappa, Jagadeesh
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] valgrind: Add INSANE_SKIP of ar
From: "Krishnanjanappa, Jagadeesh"
If a complier supports generating 32-bit and 64-bit binaries, then
while building valgrind we have two sets of binaries (32-bit and 64-bit)
being generated.
Example: With compiler supporting generation of both 32-bit and 64-bit
binaries, and buildin
ping
Regards,
Jagadeesh
From: Krishnanjanappa, Jagadeesh
Sent: Thursday, March 26, 2015 9:09 PM
To: openembedded-core@lists.openembedded.org
Cc: Krishnanjanappa, Jagadeesh
Subject: [OE-core][PATCH v2] libart-lgpl: add art_config.h for
armeb/aarch64be
From: "Krishnanjanappa, Jagadeesh"
The preprocessor macro values present in art_config.h
differ for individual architectures, basically libart-lgpl recipe will
pick up correct art_config.h file based on
ART_CONFIG = "${HOST_ARCH}/art_config.h"
and thereby having correct
Hi Naresh,
>
>Detail description what does the patch will do ???
The patch adds art_config.h files for
armeb/aarch64be/aarch64be_32 target architectures.
The preprocessor macro values present in art_config.h
differ for individual architectures, basically libart-lgpl recipe will
pick up correct ar
14 matches
Mail list logo
