Using the host objdump can lead to errors like:
objdump: library.so.1.0.0: File format is ambiguous
objdump: Matching formats: elf32-littlearm elf32-littlearm-symbian
elf32-littlearm-vxworks
with certain configurations of binutils.
Signed-off-by: James Limbouris
---
meta/classes
ccessfully... I had a look at module.bbclass,
and it sets CC, LD, and AR manually, rather than setting CROSS_COMPILE, for
reasons I don't yet understand.
So I'm not too sure how to go about fixing this. Anyone know why there are
special kernel suffixes etc on these tools?
Rega
ng a non-zero exit code.
Perhaps we should be using cp -f, or discarding the result?
Regards,
James Limbouris
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Hi,
I need to have multiple kernels built for a particular piece of hardware, to be
packaged within several different images. I understand that in oe-core, there
is a single kernel provider, and the kernel it builds is staged into the
machine sysroot so that external kernel modules can be built
Signed-off-by: James Limbouris
---
.../gtk+/gtk+-2.24.8/configure-nm.patch|4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-gnome/gtk+/gtk+-2.24.8/configure-nm.patch
b/meta/recipes-gnome/gtk+/gtk+-2.24.8/configure-nm.patch
index 5aeef50
Signed-off-by: James Limbouris
---
.../gdk-pixbuf-2.24.0/configure_nm.patch | 21
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.0.bb |3 +-
2 files changed, 23 insertions(+), 1 deletions(-)
create mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf-2.24.0
> -Original Message-
> From: Paul Menzel [mailto:paulepan...@users.sourceforge.net]
> Sent: Tuesday, 6 March 2012 5:45 PM
> To: openembedded-core@lists.openembedded.org
> Cc: James Limbouris
> Subject: Re: [OE-core] [PATCH v2] gdk-pixbuf: Pick up ${NM} from the
> e
Signed-off-by: James Limbouris
---
.../gdk-pixbuf-2.24.0/configure_nm.patch | 18 ++
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.0.bb |3 ++-
2 files changed, 20 insertions(+), 1 deletions(-)
create mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf-2.24.0
> -Original Message-
> From: Saul Wold [mailto:s...@linux.intel.com]
> Sent: Tuesday, 6 March 2012 5:24 AM
> To: Patches and discussions about the oe-core layer
> Cc: James Limbouris
> Subject: Re: [OE-core] [PATCH] mtd-utils: clean up old files
>
> On 02/27/2012 1
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Khem Raj
> Sent: Friday, 2 March 2012 3:56 PM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [PATCH] gdk-p
[OE-core] [PATCH] gdk-pixbuf: Pick up ${NM} from the
> environment.
>
> On (02/03/12 03:07), James Limbouris wrote:
> > > -Original Message-
> > > From: openembedded-core-boun...@lists.openembedded.org
> > > [mailto:openembedded-core-boun...@lists.o
[OE-core] [PATCH] gdk-pixbuf: Pick up ${NM} from the
> environment.
>
> On 02/27/2012 11:36 PM, James Limbouris wrote:
> > Signed-off-by: James Limbouris
> > ---
> > .../gdk-pixbuf-2.24.0/configure_nm.patch | 19
> +++
> > meta/recipe
Without 64 bit shell tests, the timestamp comparison in initscripts'
bootmisc.sh throws 'out of range' errors.
With CONFIG_FEATURE_DATE_COMPAT, date reads the MMddhhmm string as
hhmmMMdd when setting the time from the timestamp in bootmisc.sh.
Signed-off-by: James Limbo
Also, CONFIG_FEATURE_DATE_COMPAT=y has to be removed - it mungs the
MMddhhmm string into hhmmMMdd !
> -Original Message-
> From: James Limbouris
> Sent: Wednesday, 29 February 2012 1:32 PM
> To: Patches and discussions about the oe-core layer
> Subject: RE: [
Hi,
I think we need to add BUSYBOX_CONFIG_FEATURE_TEST_64 to the busybox defconfig
after this patch.
On my build (which had neither BUSYBOX_CONFIG_FEATURE_TEST_64 nor
BUSYBOX_CONFIG_EXPR_MATH_SUPPORT_64) I was getting 'out of range' errors.
Regards
James Limbouris
> -Ori
If a machine loses power while building the volatiles cache, it will
continue to operate with an incomplete set of volatiles. Fix this by
updating atomically.
Signed-off-by: James Limbouris
---
.../initscripts-1.0/populate-volatile.sh | 10 ++
meta/recipes-core/initscripts
Signed-off-by: James Limbouris
---
.../gdk-pixbuf-2.24.0/configure_nm.patch | 19 +++
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.0.bb |3 ++-
2 files changed, 21 insertions(+), 1 deletions(-)
create mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf-2.24.0
Signed-off-by: James Limbouris
---
.../add-exclusion-to-mkfs-jffs2-git-2.patch| 103 ---
.../add-exclusion-to-mkfs-jffs2-git.patch | 136
.../mtd/mtd-utils/fix-ignoreerrors-git.patch | 28
.../mtd/mtd-utils/remove-ubi.patch
If ranlib, ar, or cc are not supplied to make, it attempts to use ${CROSS}xxx.
Since ${CROSS} is not set, host ranlib may run, producing an unusable .a file
on some platforms.
Signed-off-by: James Limbouris
---
meta/recipes-devtools/mtd/mtd-utils_1.4.9.bb |4 ++--
1 files changed, 2
> -Original Message-
> From: James Limbouris [mailto:ja...@digitalmatter.com.au]
> Sent: Tuesday, 10 January 2012 4:38 PM
> To: Openembedded-core@lists.openembedded.org
> Cc: James Limbouris
> Subject: [PATCH] ghostscript: build cups filters
>
> Cups filters are no
config
script gives out paths pointing to the sysroot, so some of the paths needed to
be adjusted in the Makefile.
Signed-off-by: James Limbouris
---
.../ghostscript/ghostscript_9.04.bb| 29 ---
1 files changed, 24 insertions(+), 5 deletions(-)
diff --git a/meta
Subject: Re: [OE-core] [PATCH 3/3] gcc-configure-sdk: Point sysroot to correct
> location
>
> On Fri, 2011-10-21 at 05:23 +, James Limbouris wrote:
> > > -Original Message-
> > > From: openembedded-core-boun...@lists.openembedded.org
> > > [mailto:op
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Matthew McClintock
> Sent: Thursday, 27 October 2011 11:07 AM
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [RFC] Fi
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> James Limbouris
> Sent: Wednesday, 26 October 2011 9:35 AM
> To: openembedded-core@lists.openembedded.org
> Subje
is sufficient. I'd expect
that this would cause dbus to add itself to the sdk sysroot's passwd (which
previously didn't exist?). Seems harmless enough... I'm giving it a try now,
but any advice or opinions would be appreciated.
Regards,
James Limbouris
__
e: [OE-core] [PATCH 3/3] gcc-configure-sdk: Point sysroot to correct
> location
>
> On Thu, Oct 20, 2011 at 10:12 PM, James Limbouris
> wrote:
> >> -Original Message-
> >> From: openembedded-core-boun...@lists.openembedded.org
> >> [mailto:open
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: Friday, 21 October 2011 1:03 PM
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 3/3] gcc-confi
and it seems gcc-cross-canadian-arm
is also misconfiguring.
The relevant configure flags from my config log are:
--with-local-prefix=/usr/local/rica-eglibc-i686-armv5te/sysroots/arm-rica-linux-gnueabi/usr
and
--with-sysroot=/usr/local/rica-eglibc-i686-armv5te/sysroots/arm-rica-linux-gnueabi
I thin
toolchain should be looking at 'armv5te-rica-linux-gnueabi', as the names
have changed.
I'm not yet acquainted with the darker arts of toolchain generation. Can anyone
help with this?
Regards,
James Limbouris
___
Openembedded-core m
qt4-embedded-conf contains an environment setup script for profile.d.
It has been packaged seperately to allow for its exclusion, but this is
only practical if it is added to RRECOMMENDS, rather than RDEPENDS.
Signed-off-by: James Limbouris
---
meta/recipes-qt/qt4/qt4-embedded.inc |4
ayer
> Subject: Re: [OE-core] Problem building gcc-cross-initial with latest linaro
> patches.
>
> On Sun, Oct 2, 2011 at 9:46 PM, James Limbouris
> wrote:
> > | xterm Xt error: Can't open display:
> > | xterm: DISPLAY is not set
> > | ERROR: Error executing a p
ta oe needed to be adjusted too
>>
>> Regards,
>> James Limbouris
Thanks Khem, I must have missed it earlier.
James
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
hy the manual patch resolution isn't working - does it work for
other people?
When I try to apply the patch manually, I get the following hunk failure in
gcc/combine.c:
***
*** 5629,5635
{
/* Try to simplify the expression further. */
rtx tor
Re: [OE-core] Problem with new image-prelink
>
> On 9/13/11 8:33 PM, James Limbouris wrote:
> >> -Original Message-
> >> From: openembedded-core-boun...@lists.openembedded.org
> >> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Mark Hatle
> Sent: Wednesday, 14 September 2011 8:52 AM
> To: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] Problem wi
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Mark Hatle
> Sent: Monday, 12 September 2011 10:50 PM
> To: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] Problem with
ngs or errors. (Easiest way is to search for "prelink". There
> should be two hits, one that says "Size before prelinking: ..." and one that
> says "Size after prelinking: ..." between that would be any prelinker
> messages.)
>
> --Mark
>
>
..
I think the gettimeofday() before the crash is the end of the loading process.
None of the other binaries on the system are doing this - even demos from
qt4-embedded-demos. The only salient feature of this particular binary is
its large resource section, weighing it in at 1.4 MB.
I'm
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Anders Darander
> Sent: Monday, 5 September 2011 3:05 PM
> To: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [RESEND]
Hi,
I was trying to take advantage of the new x11 DISTRO_FEATURE and
ran into some trouble with the dbus package. When building with meta-oe,
gconf depends on dbus-x11, and just about everything depends on gconf.
So when I disable x11, I can only build my images with 'bitbake -I dbus-x11'.
As it
>
> Worse, I don't think bitbake.conf is guaranteed to be in the same spot in
> every layers.conf, so different layers will parse with different environments.
>
Sorry, that last line is wrong. Bitbake.conf always parses last.
James
___
Openembedded-c
On Wed, 10 August 2011 8:06 PM, Richard Purdie wrote:
> On Wed, 2011-08-10 at 02:06 +0000, James Limbouris wrote:
> > On Wednesday, 10 August 2011 9:55 AM, Mark Hatle wrote:
> > > On 8/9/11 7:32 PM, Scott Garman wrote:
> > > > On 08/08/2011 07:04 PM, James Limbou
On Wednesday, 10 August 2011 9:55 AM, Mark Hatle wrote:
> On 8/9/11 7:32 PM, Scott Garman wrote:
> > On 08/08/2011 07:04 PM, James Limbouris wrote:
> >> The pseudo executable sets the PSEUDO_LOCALSTATEDIR environment
> >> variable to point to a sysroot location. During
On Tuesday, 9 August 2011 10:33 AM, Khem Raj wrote:
> On 08/08/2011 06:52 PM, James Limbouris wrote:
> > On Tuesday, 9 August 2011 9:40 AM, Khem Raj wrote:
> >> On Mon, Aug 8, 2011 at 6:33 PM, James Limbouris
> >> wrote:
> >>> On Tue Aug 9 01:25:55 CEST 20
problem.
Signed-off-by: James Limbouris
---
meta/conf/bitbake.conf |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 6f0b42c..9a9ab53 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -557,7 +557,7 @@ SRCPV
On Tuesday, 9 August 2011 9:40 AM, Khem Raj wrote:
> On Mon, Aug 8, 2011 at 6:33 PM, James Limbouris
> wrote:
> > On Tue Aug 9 01:25:55 CEST 2011, Richard Purdie wrote:
> >>On Mon, 2011-08-08 at 05:02 +, James Limbouris wrote:
> >>> Hi,
> >>>
>
On Tue Aug 9 01:25:55 CEST 2011, Richard Purdie wrote:
>On Mon, 2011-08-08 at 05:02 +0000, James Limbouris wrote:
>> Hi,
>>
>> In oe-core, with Angstrom 2010.x, generating an sdk with:
>>
>> bitbake meta-toolchain-qte
>>
>> is giving me a toolchai
libgcc :4.5-r39.1+svnr176640
libgcc-nativesdk :4.6.1+svnr175454-r3
:4.5-r39.1+svnr176640
Regards
James Limbouris
___
Openembedded-core mailing list
Openembedded-core@li
On Fri Aug 5 05:20:19, James Limbouris wrote:
On Wed Aug 3 05:57:55, James Limbouris wrote:
On Tue Aug 2 16:40:09, Mark Hatle wrote:
On 8/2/11 5:11 AM, Richard Purdie wrote:
On Tue, 2011-08-02 at 07:28 +, James Limbouris wrote:
Hi,
I've just switched to oe-core from -dev, an
On Wed Aug 3 05:57:55, James Limbouris wrote:
> On Tue Aug 2 16:40:09, Mark Hatle wrote:
>>On 8/2/11 5:11 AM, Richard Purdie wrote:
>>> On Tue, 2011-08-02 at 07:28 +0000, James Limbouris wrote:
>>>> Hi,
>>>>
>>>> I've just switched to oe-c
On Tue Aug 2 16:40:09, Mark Hatle wrote:
>On 8/2/11 5:11 AM, Richard Purdie wrote:
>> On Tue, 2011-08-02 at 07:28 +0000, James Limbouris wrote:
>>> Hi,
>>>
>>> I've just switched to oe-core from -dev, and I'm finding that my root
>>> imag
der in the work folder after do_rm_work, but it is not there if I do
a bitbake -c build image-xxx.
Regards
James Limbouris
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listin
52 matches
Mail list logo
