Build problems

Build problems

[Paolo Cremonese]

Hi all.
I'm new in Openembedded.
I'm trying to build an image ( bitbake opie-image), and I get errors.
In the following the output of bitbake:

Can anyone help me?

Thanks in advance,
Paolo



NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it
to increase performance.
NOTE: Handling BitBake files: \ (6411/6411) [100 %]
NOTE: Parsing finished. 6140 cached, 0 parsed, 271 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200901271107: started

OE Build Configuration:
BB_VERSION        = "1.8.13"
METADATA_BRANCH   = "org.openembedded.dev"
METADATA_REVISION = "a41bdd6cda499d2629ce2a156348620b7ab7afc4"
TARGET_ARCH       = "i686"
TARGET_OS         = "linux"
MACHINE           = "i686-generic"
DISTRO            = "minimal"
DISTRO_VERSION    = ".dev-snapshot-20090127"
TARGET_FPU        = ""

NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for virtual/i686-linux-binutils
(binutils-cross, external-toolchain);
NOTE: consider defining PREFERRED_PROVIDER_virtual/i686-linux-binutils
NOTE: multiple providers are available for virtual/libqte2
(qte-mt-static, qte, qte-mt);
NOTE: consider defining PREFERRED_PROVIDER_virtual/libqte2
NOTE: multiple providers are available for
virtual/i686-linux-libc-initial (glibc-initial, eglibc-initial);
NOTE: consider defining
PREFERRED_PROVIDER_virtual/i686-linux-libc-initial
NOTE: multiple providers are available for gconf (gconf, gconf-dbus);
NOTE: consider defining PREFERRED_PROVIDER_gconf
NOTE: multiple providers are available for avahi (avahi, avahi-python);
NOTE: consider defining PREFERRED_PROVIDER_avahi
NOTE: multiple providers are available for virtual/db (db3, db);
NOTE: consider defining PREFERRED_PROVIDER_virtual/db
NOTE: multiple providers are available for virtual/db-native
(db3-native, db-native);
NOTE: consider defining PREFERRED_PROVIDER_virtual/db-native
NOTE: multiple providers are available for gtk+ (gtk+, gtk
+-fastscaling);
NOTE: consider defining PREFERRED_PROVIDER_gtk+
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 60 of 2525 (ID:
1007, /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-native_0.22.bb, do_setscene)
NOTE: package pkgconfig-native-0.22: started
NOTE: package pkgconfig-native-0.22-r7: task do_setscene: started
NOTE: package pkgconfig-native-0.22-r7: task do_setscene: completed
NOTE: package pkgconfig-native-0.22: completed
NOTE: Running task 61 of 2525 (ID:
1008, /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-native_0.22.bb, do_fetch)
NOTE: package pkgconfig-native-0.22: started
NOTE: package pkgconfig-native-0.22-r7: task do_fetch: started
NOTE: fetch
http://pkgconfig.freedesktop.org/releases/pkg-config-0.22.tar.gz
--11:09:10--
http://pkgconfig.freedesktop.org/releases/pkg-config-0.22.tar.gz
           => `/home/paolo/sources/pkg-config-0.22.tar.gz'
Resolving pkgconfig.freedesktop.org... 131.252.210.176
Connecting to pkgconfig.freedesktop.org|131.252.210.176|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,006,425 (983K) [application/x-gzip]

100%[====================================>] 1,006,425    206.02K/s
ETA 00:00

11:09:16 (181.24 KB/s) - `/home/paolo/sources/pkg-config-0.22.tar.gz'
saved [1006425/1006425]

NOTE: package pkgconfig-native-0.22-r7: task do_fetch: completed
NOTE: package pkgconfig-native-0.22: completed
NOTE: Running task 62 of 2525 (ID:
1009, /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-native_0.22.bb, do_unpack)
NOTE: package pkgconfig-native-0.22: started
NOTE: package pkgconfig-native-0.22-r7: task do_unpack: started
NOTE: Unpacking /home/paolo/sources/pkg-config-0.22.tar.gz
to /home/paolo/oe/stuff/build/tmp/work/i686-linux/pkgconfig-native-0.22-r7/
NOTE:
Unpacking /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-0.22/glibconfig-sysdefs.h to /home/paolo/oe/stuff/build/tmp/work/i686-linux/pkgconfig-native-0.22-r7/
NOTE: package pkgconfig-native-0.22-r7: task do_unpack: completed
NOTE: package pkgconfig-native-0.22: completed
NOTE: Running task 64 of 2525 (ID:
1131, /home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb, do_configure)
NOTE: package libtool-cross-1.5.10: started
NOTE: package libtool-cross-1.5.10-r10: task do_configure: started
ERROR: function do_configure failed
ERROR: log data follows
(/home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/temp/log.do_configure.7933)
| automake (GNU automake) 1.9.3
| Written by Tom Tromey <tromey@redhat.com>.
| 
| Copyright 2004 Free Software Foundation, Inc.
| This is free software; see the source for copying conditions.  There
is NO
| warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
| AUTOV is 1.9
| NOTE: Executing autoreconf --verbose --install --force
--exclude=libtoolize
-I /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ -I/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 -I /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal
-I /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ -I /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 -I /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal --force
| autoreconf: configure.ac: tracing
| autoreconf: configure.ac: adding subdirectory libltdl to autoreconf
| autoreconf: Entering directory `libltdl'
| autoreconf:
running: /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/bin/autoconf --include=/home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal --force --warnings=cross
| autoreconf:
running: /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/bin/autoheader --include=/home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal --force --warnings=cross
| autoreconf: running: automake --foreign --add-missing --copy
--force-missing --warnings=cross
| automake: unknown warning category `cross'
| autoreconf: running: gnu-configize
| autoreconf: Leaving directory `libltdl'
| autoreconf: configure.ac: not using Autoheader
| automake: unknown warning category `cross'
| autoreconf: Leaving directory `.'
| NOTE:
Running /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/configure 		    --build=i686-linux 		    --host=i686-linux 		    --target=i686-linux 		    --prefix=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr 		    --exec_prefix=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr 		    --bindir=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/bin 		    --sbindir=/usr/sbin 		    --libexecdir=/usr/libexec 		    --datadir=/usr/share 		    --sysconfdir=/etc 		    --sharedstatedir=/usr/com 		    --localstatedir=/var 		    --libdir=/usr/lib 		    --includedir=/usr/include 		    --oldincludedir=/usr/include 		    --infodir=/usr/share/info 		    --mandir=/usr/share/man 			 		    ...
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/endian-little
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common-linux
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common-glibc
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/ix86-common
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common
| checking for a BSD-compatible install... /usr/bin/install -c
| checking whether build environment is sane... yes
| checking for gawk... gawk
| checking whether make sets $(MAKE)... yes
| checking for i686-linux-gcc... ccache i686-linux-gcc -march=pentiumpro
| checking for C compiler default output file name...
| configure: error: C compiler cannot create executables
| See `config.log' for more details.
| FATAL: oe_runconf failed
NOTE: Task
failed: /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/temp/log.do_configure.7933
NOTE: package libtool-cross-1.5.10-r10: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package libtool-cross-1.5.10: failed
ERROR: Build
of /home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb do_configure failed
ERROR: Task 1131
(/home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb, do_configure) failed
NOTE: Tasks Summary: Attempted 63 tasks of which 60 didn't need to be
rerun and 1 failed.
ERROR:
'/home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb' failed
NOTE: build 200901271107: completed
paolo@ubuntu2:~/oe/stuff/build$ 

Re: Build problems

[Charlton, John]

You might try the angstrom-2008.1 DISTRO with the org.openembedded.dev branch Or angstrom-2007.1 with the org.openembedded.stable branch.  I have built oe for the "i686-generic" MACHINE with the angstrom-2007.1 with some problems but the Angstrom distro seems to define all of the things you need to do the build.

--John

-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Paolo Cremonese
Sent: Tuesday, January 27, 2009 7:26 AM
To: openembedded-devel@lists.openembedded.org
Subject: [oe] Build problems

Hi all.
I'm new in Openembedded.
I'm trying to build an image ( bitbake opie-image), and I get errors.
In the following the output of bitbake:

Can anyone help me?

Thanks in advance,
Paolo



NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it to increase performance.
NOTE: Handling BitBake files: \ (6411/6411) [100 %]
NOTE: Parsing finished. 6140 cached, 0 parsed, 271 skipped, 0 masked.
NOTE: Cache is clean, not saving.
NOTE: build 200901271107: started

OE Build Configuration:
BB_VERSION        = "1.8.13"
METADATA_BRANCH   = "org.openembedded.dev"
METADATA_REVISION = "a41bdd6cda499d2629ce2a156348620b7ab7afc4"
TARGET_ARCH       = "i686"
TARGET_OS         = "linux"
MACHINE           = "i686-generic"
DISTRO            = "minimal"
DISTRO_VERSION    = ".dev-snapshot-20090127"
TARGET_FPU        = ""

NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for virtual/i686-linux-binutils (binutils-cross, external-toolchain);
NOTE: consider defining PREFERRED_PROVIDER_virtual/i686-linux-binutils
NOTE: multiple providers are available for virtual/libqte2 (qte-mt-static, qte, qte-mt);
NOTE: consider defining PREFERRED_PROVIDER_virtual/libqte2
NOTE: multiple providers are available for virtual/i686-linux-libc-initial (glibc-initial, eglibc-initial);
NOTE: consider defining
PREFERRED_PROVIDER_virtual/i686-linux-libc-initial
NOTE: multiple providers are available for gconf (gconf, gconf-dbus);
NOTE: consider defining PREFERRED_PROVIDER_gconf
NOTE: multiple providers are available for avahi (avahi, avahi-python);
NOTE: consider defining PREFERRED_PROVIDER_avahi
NOTE: multiple providers are available for virtual/db (db3, db);
NOTE: consider defining PREFERRED_PROVIDER_virtual/db
NOTE: multiple providers are available for virtual/db-native (db3-native, db-native);
NOTE: consider defining PREFERRED_PROVIDER_virtual/db-native
NOTE: multiple providers are available for gtk+ (gtk+, gtk
+-fastscaling);
NOTE: consider defining PREFERRED_PROVIDER_gtk+
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 60 of 2525 (ID:
1007, /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-native_0.22.bb, do_setscene)
NOTE: package pkgconfig-native-0.22: started
NOTE: package pkgconfig-native-0.22-r7: task do_setscene: started
NOTE: package pkgconfig-native-0.22-r7: task do_setscene: completed
NOTE: package pkgconfig-native-0.22: completed
NOTE: Running task 61 of 2525 (ID:
1008, /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-native_0.22.bb, do_fetch)
NOTE: package pkgconfig-native-0.22: started
NOTE: package pkgconfig-native-0.22-r7: task do_fetch: started
NOTE: fetch
http://pkgconfig.freedesktop.org/releases/pkg-config-0.22.tar.gz
--11:09:10--
http://pkgconfig.freedesktop.org/releases/pkg-config-0.22.tar.gz
           => `/home/paolo/sources/pkg-config-0.22.tar.gz'
Resolving pkgconfig.freedesktop.org... 131.252.210.176 Connecting to pkgconfig.freedesktop.org|131.252.210.176|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,006,425 (983K) [application/x-gzip]

100%[====================================>] 1,006,425    206.02K/s
ETA 00:00

11:09:16 (181.24 KB/s) - `/home/paolo/sources/pkg-config-0.22.tar.gz'
saved [1006425/1006425]

NOTE: package pkgconfig-native-0.22-r7: task do_fetch: completed
NOTE: package pkgconfig-native-0.22: completed
NOTE: Running task 62 of 2525 (ID:
1009, /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-native_0.22.bb, do_unpack)
NOTE: package pkgconfig-native-0.22: started
NOTE: package pkgconfig-native-0.22-r7: task do_unpack: started
NOTE: Unpacking /home/paolo/sources/pkg-config-0.22.tar.gz
to /home/paolo/oe/stuff/build/tmp/work/i686-linux/pkgconfig-native-0.22-r7/
NOTE:
Unpacking /home/paolo/oe/stuff/openembedded/packages/pkgconfig/pkgconfig-0.22/glibconfig-sysdefs.h to /home/paolo/oe/stuff/build/tmp/work/i686-linux/pkgconfig-native-0.22-r7/
NOTE: package pkgconfig-native-0.22-r7: task do_unpack: completed
NOTE: package pkgconfig-native-0.22: completed
NOTE: Running task 64 of 2525 (ID:
1131, /home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb, do_configure)
NOTE: package libtool-cross-1.5.10: started
NOTE: package libtool-cross-1.5.10-r10: task do_configure: started
ERROR: function do_configure failed
ERROR: log data follows
(/home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/temp/log.do_configure.7933)
| automake (GNU automake) 1.9.3
| Written by Tom Tromey <tromey@redhat.com>.
| 
| Copyright 2004 Free Software Foundation, Inc.
| This is free software; see the source for copying conditions.  There
is NO
| warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
| AUTOV is 1.9
| NOTE: Executing autoreconf --verbose --install --force
--exclude=libtoolize
-I /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ -I/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 -I /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal
| autoreconf: Entering directory `.'
| autoreconf: configure.ac: not using Gettext
| autoreconf: running: aclocal
-I /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ -I /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 -I /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal --force
| autoreconf: configure.ac: tracing
| autoreconf: configure.ac: adding subdirectory libltdl to autoreconf
| autoreconf: Entering directory `libltdl'
| autoreconf:
running: /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/bin/autoconf --include=/home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal --force --warnings=cross
| autoreconf:
running: /home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/bin/autoheader --include=/home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/ --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal-1.9 --include=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/share/aclocal --force --warnings=cross
| autoreconf: running: automake --foreign --add-missing --copy
--force-missing --warnings=cross
| automake: unknown warning category `cross'
| autoreconf: running: gnu-configize
| autoreconf: Leaving directory `libltdl'
| autoreconf: configure.ac: not using Autoheader
| automake: unknown warning category `cross'
| autoreconf: Leaving directory `.'
| NOTE:
Running /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/libtool-1.5.10/configure 		    --build=i686-linux 		    --host=i686-linux 		    --target=i686-linux 		    --prefix=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr 		    --exec_prefix=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr 		    --bindir=/home/paolo/oe/stuff/build/tmp/staging/i686-linux/usr/bin 		    --sbindir=/usr/sbin 		    --libexecdir=/usr/libexec 		    --datadir=/usr/share 		    --sysconfdir=/etc 		    --sharedstatedir=/usr/com 		    --localstatedir=/var 		    --libdir=/usr/lib 		    --includedir=/usr/include 		    --oldincludedir=/usr/include 		    --infodir=/usr/share/info 		    --mandir=/usr/share/man 			 		    ...
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/endian-little
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common-linux
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common-glibc
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/ix86-common
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common
| configure: loading site
script /home/paolo/oe/stuff/openembedded/site/common
| checking for a BSD-compatible install... /usr/bin/install -c checking 
| whether build environment is sane... yes checking for gawk... gawk 
| checking whether make sets $(MAKE)... yes checking for 
| i686-linux-gcc... ccache i686-linux-gcc -march=pentiumpro checking for 
| C compiler default output file name...
| configure: error: C compiler cannot create executables See 
| `config.log' for more details.
| FATAL: oe_runconf failed
NOTE: Task
failed: /home/paolo/oe/stuff/build/tmp/work/i686-linux/libtool-cross-1.5.10-r10/temp/log.do_configure.7933
NOTE: package libtool-cross-1.5.10-r10: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package libtool-cross-1.5.10: failed
ERROR: Build
of /home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb do_configure failed
ERROR: Task 1131
(/home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb, do_configure) failed
NOTE: Tasks Summary: Attempted 63 tasks of which 60 didn't need to be rerun and 1 failed.
ERROR:
'/home/paolo/oe/stuff/openembedded/packages/libtool/libtool-cross_1.5.10.bb' failed
NOTE: build 200901271107: completed
paolo@ubuntu2:~/oe/stuff/build$ 




_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Marco Cavallini]

Paolo Cremonese ha scritto:
> Hi all.
> I'm new in Openembedded.
> I'm trying to build an image ( bitbake opie-image), and I get errors.
> In the following the output of bitbake:
> 
> Can anyone help me?
> 
> Thanks in advance,
> Paolo
> 
> 
> 
> NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it
> to increase performance.
> NOTE: Handling BitBake files: \ (6411/6411) [100 %]
> NOTE: Parsing finished. 6140 cached, 0 parsed, 271 skipped, 0 masked.
> NOTE: Cache is clean, not saving.
> NOTE: build 200901271107: started
> 
> OE Build Configuration:
> BB_VERSION        = "1.8.13"
> METADATA_BRANCH   = "org.openembedded.dev"
> METADATA_REVISION = "a41bdd6cda499d2629ce2a156348620b7ab7afc4"
> TARGET_ARCH       = "i686"
> TARGET_OS         = "linux"
> MACHINE           = "i686-generic"
> DISTRO            = "minimal"
> DISTRO_VERSION    = ".dev-snapshot-20090127"
> TARGET_FPU        = ""

It might be worth trying with "bitbake minimal-image" to start with,
just to see if basic system works.
I just built an i586-generic angstrom-2008.1 DISTRO with the
org.openembedded.dev branch and it works.

Ciao
--
Marco Cavallini | KOAN sas | Bergamo - Italia
 embedded and real-time software engineering
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
      http://www.KoanSoftware.com

Re: Build problems

[Paolo Cremonese]

OK, I have built the image wihout errors, thank you.

Now, what I have to do to create a bootable compact flash with the
image?

Thanks in advance,
Paolo


On mar, 2009-01-27 at 14:35 +0100, Marco Cavallini wrote:
> Paolo Cremonese ha scritto:
> > Hi all.
> > I'm new in Openembedded.
> > I'm trying to build an image ( bitbake opie-image), and I get errors.
> > In the following the output of bitbake:
> > 
> > Can anyone help me?
> > 
> > Thanks in advance,
> > Paolo
> > 
> > 
> > 
> > NOTE: Psyco JIT Compiler (http://psyco.sf.net) not available. Install it
> > to increase performance.
> > NOTE: Handling BitBake files: \ (6411/6411) [100 %]
> > NOTE: Parsing finished. 6140 cached, 0 parsed, 271 skipped, 0 masked.
> > NOTE: Cache is clean, not saving.
> > NOTE: build 200901271107: started
> > 
> > OE Build Configuration:
> > BB_VERSION        = "1.8.13"
> > METADATA_BRANCH   = "org.openembedded.dev"
> > METADATA_REVISION = "a41bdd6cda499d2629ce2a156348620b7ab7afc4"
> > TARGET_ARCH       = "i686"
> > TARGET_OS         = "linux"
> > MACHINE           = "i686-generic"
> > DISTRO            = "minimal"
> > DISTRO_VERSION    = ".dev-snapshot-20090127"
> > TARGET_FPU        = ""
> 
> It might be worth trying with "bitbake minimal-image" to start with,
> just to see if basic system works.
> I just built an i586-generic angstrom-2008.1 DISTRO with the
> org.openembedded.dev branch and it works.
> 
> Ciao
> --
> Marco Cavallini | KOAN sas | Bergamo - Italia
>  embedded and real-time software engineering
> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
>       http://www.KoanSoftware.com
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Marco Cavallini]

Paolo Cremonese ha scritto:
> OK, I have built the image wihout errors, thank you.
> 
> Now, what I have to do to create a bootable compact flash with the
> image?
> 
> Thanks in advance,
> Paolo

Paolo,
I'm just working on a system like your, but with i486.

1. prtition your CF
2. format CF ext3
3. load (untar) yourimage.tar into CF
4. install bootloader (GRUB)[1]

[1] GRUB build in OE is broken at the moment, I'm patching it ;-)

Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
--
Marco Cavallini | KOAN sas | Bergamo - Italia
 embedded and real-time software engineering
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
      http://www.KoanSoftware.com

Re: Build problems

[Elena of Valhalla]

On Wed, Jan 28, 2009 at 10:49 AM, Paolo Cremonese <pisa.t@teledata-i.com> wrote:
> Now, what I have to do to create a bootable compact flash with the
> image?

What image format did you build? I've found that the easier way to
create a bootable compact flash would be to build the .tar image,
format the CF as ext(2|3), extract the contents of the tarball in the
mounted CF and then install extlinux on it

-- 
Elena ``of Valhalla''

email: elena.valhalla@gmail.com

Re: Build problems

[Paolo Cremonese]

OK, I done all but GRUB.

My CF is connected through an USB adapter, and is seen as /dev/sdb

I can navigate into the filesystem.

I try to install GRUB using

sudo grub-install /dev/sdb

but the answer is

/dev/sdb does not have any corresponding BIOS drive.

Do I have necessarly to connect the CF using an IDE port?

Thanks in advance.

Ciao,
Paolo


On mer, 2009-01-28 at 11:03 +0100, Marco Cavallini wrote:
> Paolo Cremonese ha scritto:
> > OK, I have built the image wihout errors, thank you.
> > 
> > Now, what I have to do to create a bootable compact flash with the
> > image?
> > 
> > Thanks in advance,
> > Paolo
> 
> Paolo,
> I'm just working on a system like your, but with i486.
> 
> 1. prtition your CF
> 2. format CF ext3
> 3. load (untar) yourimage.tar into CF
> 4. install bootloader (GRUB)[1]
> 
> [1] GRUB build in OE is broken at the moment, I'm patching it ;-)
> 
> Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
> --
> Marco Cavallini | KOAN sas | Bergamo - Italia
>  embedded and real-time software engineering
> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
>       http://www.KoanSoftware.com
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Yuri Bushmelev]

Hello!

> I try to install GRUB using
>
> sudo grub-install /dev/sdb
>
> but the answer is
>
> /dev/sdb does not have any corresponding BIOS drive.

Try with --recheck-devices or something like (look at grub-install --help).

-- 
Yuri Bushmelev

Re: Build problems

[Marco Cavallini]

> On mer, 2009-01-28 at 11:03 +0100, Marco Cavallini wrote:
>> Paolo Cremonese ha scritto:
>>> OK, I have built the image wihout errors, thank you.
>>>
>>> Now, what I have to do to create a bootable compact flash with the
>>> image?
>>>
>>> Thanks in advance,
>>> Paolo
>> Paolo,
>> I'm just working on a system like your, but with i486.
>>
>> 1. prtition your CF
>> 2. format CF ext3
>> 3. load (untar) yourimage.tar into CF
>> 4. install bootloader (GRUB)[1]
>>
>> [1] GRUB build in OE is broken at the moment, I'm patching it ;-)
>>

GRUB patch is ready and should be pushed soon by hrw.

Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
--
Marco Cavallini | KOAN sas | Bergamo - Italia
 embedded and real-time software engineering
   Atmel third party certified consultant
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
      http://www.KoanSoftware.com

Re: Build problems

[Paolo Cremonese]

Fine, waiting for GRUB patch. (what is "hrw" ?)

My target has not hard disk, only CF.
To run the image, do I need a RAMFS ?
And in this case, I have to add it to the GRUB "menu.lst" ?


title		Test Minimalist Image Angstrom
root		(hd0,0)
kernel		/boot/bzImage-2.6.21
initrd		/boot/initrd.img root=/dev/ram0 rw init=/linuxrc



Ciao,
Paolo

On ven, 2009-01-30 at 17:33 +0100, Marco Cavallini wrote:
> > On mer, 2009-01-28 at 11:03 +0100, Marco Cavallini wrote:
> >> Paolo Cremonese ha scritto:
> >>> OK, I have built the image wihout errors, thank you.
> >>>
> >>> Now, what I have to do to create a bootable compact flash with the
> >>> image?
> >>>
> >>> Thanks in advance,
> >>> Paolo
> >> Paolo,
> >> I'm just working on a system like your, but with i486.
> >>
> >> 1. prtition your CF
> >> 2. format CF ext3
> >> 3. load (untar) yourimage.tar into CF
> >> 4. install bootloader (GRUB)[1]
> >>
> >> [1] GRUB build in OE is broken at the moment, I'm patching it ;-)
> >>
> 
> GRUB patch is ready and should be pushed soon by hrw.
> 
> Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
> --
> Marco Cavallini | KOAN sas | Bergamo - Italia
>  embedded and real-time software engineering
>    Atmel third party certified consultant
> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
>       http://www.KoanSoftware.com
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Ihar Hrachyshka]

On Mon, Feb 2, 2009 at 4:57 PM, Paolo Cremonese <pisa.t@teledata-i.com> wrote:
> (what is "hrw" ?)
hrw is Marcin Juszkiewicz :D

Re: Build problems

[Marco Cavallini]

Paolo Cremonese ha scritto:
> Fine, waiting for GRUB patch. (what is "hrw" ?)
> 
> My target has not hard disk, only CF.
> To run the image, do I need a RAMFS ?
> And in this case, I have to add it to the GRUB "menu.lst" ?

Paolo,
hrw is Marcin Juszkiewicz, an OE developer and mantainer.
GRUB patch was pushed this morning and is ready for use into git mainstream.

Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
--
Marco Cavallini | KOAN sas | Bergamo - Italia
 embedded and real-time software engineering
   Atmel third party certified consultant
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
      http://www.KoanSoftware.com

Re: Build problems

[Philip Balister]

[-- Attachment #1: Type: text/plain, Size: 255 bytes --]

Ihar Hrachyshka wrote:
> On Mon, Feb 2, 2009 at 4:57 PM, Paolo Cremonese <pisa.t@teledata-i.com> wrote:
>> (what is "hrw" ?)
> hrw is Marcin Juszkiewicz :D

See also:

http://marcin.juszkiewicz.com.pl/2007/04/26/how-to-pronounce-haerwu/

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

Re: Build problems

[Paolo Cremonese]

Sorry, don't know...

Now the image works !

Then I try to build a gpe-image, but i get an error at the last step.

Thanks in advance,

Paolo



| /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: ignoring invalid character `\001' in script
| /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: syntax error in VERSION script
| collect2: ld returned 1 exit status
| make[4]: *** [libgdk_pixbuf-2.0.la] Error 1
| make[4]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2'
| make: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task
failed: /home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/temp/log.do_compile.22403
NOTE: package gtk+-2.14.2-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package gtk+-2.14.2: failed
ERROR: Build of /home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
+_2.14.2.bb do_compile failed
ERROR: Task 951 (/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
+_2.14.2.bb, do_compile) failed
NOTE: Tasks Summary: Attempted 1003 tasks of which 788 didn't need to be
rerun and 1 failed.
ERROR: '/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk+_2.14.2.bb'
failed
NOTE: build 200902040809: completed






On lun, 2009-02-02 at 17:13 +0100, Marco Cavallini wrote:
> Paolo Cremonese ha scritto:
> > Fine, waiting for GRUB patch. (what is "hrw" ?)
> > 
> > My target has not hard disk, only CF.
> > To run the image, do I need a RAMFS ?
> > And in this case, I have to add it to the GRUB "menu.lst" ?
> 
> Paolo,
> hrw is Marcin Juszkiewicz, an OE developer and mantainer.
> GRUB patch was pushed this morning and is ready for use into git mainstream.
> 
> Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
> --
> Marco Cavallini | KOAN sas | Bergamo - Italia
>  embedded and real-time software engineering
>    Atmel third party certified consultant
> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
>       http://www.KoanSoftware.com
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Koen Kooi]

On 04-02-09 10:27, Paolo Cremonese wrote:
> Sorry, don't know...
>
> Now the image works !
>
> Then I try to build a gpe-image, but i get an error at the last step.

Don't use dash as /bin/sh, use bash and rebuild libtool-cross and gtk+

regards,

Koen

>
> Thanks in advance,
>
> Paolo
>
>
>
> | /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: ignoring invalid character `\001' in script
> | /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: syntax error in VERSION script
> | collect2: ld returned 1 exit status
> | make[4]: *** [libgdk_pixbuf-2.0.la] Error 1
> | make[4]: Leaving directory
> `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> +-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
> | make[3]: *** [all-recursive] Error 1
> | make[3]: Leaving directory
> `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> +-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
> | make[2]: *** [all] Error 2
> | make[2]: Leaving directory
> `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> +-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory
> `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> +-2.14.2-r1/gtk+-2.14.2'
> | make: *** [all] Error 2
> | FATAL: oe_runmake failed
> NOTE: Task
> failed: /home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> +-2.14.2-r1/temp/log.do_compile.22403
> NOTE: package gtk+-2.14.2-r1: task do_compile: failed
> ERROR: TaskFailed event exception, aborting
> NOTE: package gtk+-2.14.2: failed
> ERROR: Build of /home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
> +_2.14.2.bb do_compile failed
> ERROR: Task 951 (/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
> +_2.14.2.bb, do_compile) failed
> NOTE: Tasks Summary: Attempted 1003 tasks of which 788 didn't need to be
> rerun and 1 failed.
> ERROR: '/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk+_2.14.2.bb'
> failed
> NOTE: build 200902040809: completed
>
>
>
>
>
>
> On lun, 2009-02-02 at 17:13 +0100, Marco Cavallini wrote:
>> Paolo Cremonese ha scritto:
>>> Fine, waiting for GRUB patch. (what is "hrw" ?)
>>>
>>> My target has not hard disk, only CF.
>>> To run the image, do I need a RAMFS ?
>>> And in this case, I have to add it to the GRUB "menu.lst" ?
>> Paolo,
>> hrw is Marcin Juszkiewicz, an OE developer and mantainer.
>> GRUB patch was pushed this morning and is ready for use into git mainstream.
>>
>> Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
>> --
>> Marco Cavallini | KOAN sas | Bergamo - Italia
>>   embedded and real-time software engineering
>>     Atmel third party certified consultant
>> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
>>        http://www.KoanSoftware.com
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Paolo Cremonese]

OK, changed DASH to BASH.
Compiled libtool-cross OK.

compiling gtk+ (bitbake gtk+), fails.

Regards,
Paolo


NOTE: package libxft-2.1.13: completed
NOTE: Running task 1114 of 1553 (ID:
7, /home/paolo/oe/stuff/openembedded/packages/gtk+/gtk+_2.14.2.bb,
do_compile)
NOTE: package gtk+-2.14.2: started
NOTE: package gtk+-2.14.2-r1: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows
(/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/temp/log.do_compile.15854)
| NOTE: make
| make  all-recursive
| make[1]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2'
| Making all in po
| make[2]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/po'
| make[2]: Nothing to be done for `all'.
| make[2]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/po'
| Making all in po-properties
| make[2]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/po-properties'
| make[2]: Nothing to be done for `all'.
| make[2]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/po-properties'
| Making all in gdk-pixbuf
| make[2]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make  all-recursive
| make[3]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| Making all in pixops
| make[4]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf/pixops'
| make[4]: Nothing to be done for `all'.
| make[4]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf/pixops'
| make[4]: Entering directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| /bin/bash ../i586-angstrom-linux-libtool --tag=CC   --mode=link ccache
i586-angstrom-linux-gcc -march=pentium  -DGDK_PIXBUF_DISABLE_DEPRECATED
-isystem/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -Wall  -version-info 1400:2:1400 -export-symbols-regex "^[^_].*"   -L/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib -Wl,-rpath-link,/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib -Wl,-O1 -Wl,--hash-style=gnu -o libgdk_pixbuf-2.0.la -rpath /usr/lib gdk-pixbuf.lo gdk-pixbuf-animation.lo gdk-pixbuf-data.lo gdk-pixbuf-io.lo gdk-pixbuf-loader.lo gdk-pixbuf-scale.lo gdk-pixbuf-simple-anim.lo gdk-pixbuf-scaled-anim.lo gdk-pixbuf-util.lo gdk-pixdata.lo gdk-pixbuf-enum-types.lo pixops/libpixops.la  -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lm
| i586-angstrom-linux-libtool: link: rm
-fr  .libs/libgdk_pixbuf-2.0.exp .libs/libgdk_pixbuf-2.0.ver
| i586-angstrom-linux-libtool:
link: /home/paolo/oe/stuff/build/tmp/cross/i586/bin/i586-angstrom-linux-nm -B  .libs/gdk-pixbuf.o .libs/gdk-pixbuf-animation.o .libs/gdk-pixbuf-data.o .libs/gdk-pixbuf-io.o .libs/gdk-pixbuf-loader.o .libs/gdk-pixbuf-scale.o .libs/gdk-pixbuf-simple-anim.o .libs/gdk-pixbuf-scaled-anim.o .libs/gdk-pixbuf-util.o .libs/gdk-pixdata.o .libs/gdk-pixbuf-enum-types.o   pixops/.libs/libpixops.a | sed -n -e 's/^.*[	 ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[	 ][	 ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\x01 \x02 \x02/p' | /bin/sed 's/.* //' | sort | uniq > .libs/libgdk_pixbuf-2.0.exp
| i586-angstrom-linux-libtool: link: /bin/grep -E -e "^[^_].*"
".libs/libgdk_pixbuf-2.0.exp" > ".libs/libgdk_pixbuf-2.0.expT"
| i586-angstrom-linux-libtool: link: mv -f
".libs/libgdk_pixbuf-2.0.expT" ".libs/libgdk_pixbuf-2.0.exp"
| i586-angstrom-linux-libtool: link: echo "{ global:"
> .libs/libgdk_pixbuf-2.0.ver
| i586-angstrom-linux-libtool: link:  cat .libs/libgdk_pixbuf-2.0.exp |
sed -e "s/\(.*\)/\x01;/" >> .libs/libgdk_pixbuf-2.0.ver
| i586-angstrom-linux-libtool: link:  echo "local: *; };"
>> .libs/libgdk_pixbuf-2.0.ver
| i586-angstrom-linux-libtool: link:  ccache i586-angstrom-linux-gcc
-march=pentium
-shared  .libs/gdk-pixbuf.o .libs/gdk-pixbuf-animation.o .libs/gdk-pixbuf-data.o .libs/gdk-pixbuf-io.o .libs/gdk-pixbuf-loader.o .libs/gdk-pixbuf-scale.o .libs/gdk-pixbuf-simple-anim.o .libs/gdk-pixbuf-scaled-anim.o .libs/gdk-pixbuf-util.o .libs/gdk-pixdata.o .libs/gdk-pixbuf-enum-types.o  -Wl,--whole-archive pixops/.libs/libpixops.a -Wl,--no-whole-archive  -Wl,-rpath -Wl,/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib -L/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib/.libs -L/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib /home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib/libgio-2.0.so /home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib/libgobject-2.0.so /home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib/libgmodule-2.0.so -ldl /home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib/libglib-2.0.so -lm  -march=pentium -Wl,-rpath-link -Wl,/home/paolo/oe/stuff/build/tmp/staging/i586-angstrom-linux/usr/lib -Wl,-O1 -Wl,--hash-style=gnu   -Wl,-soname -Wl,libgdk_pixbuf-2.0.so.0 -Wl,-version-script -Wl,.libs/libgdk_pixbuf-2.0.ver -o .libs/libgdk_pixbuf-2.0.so.0.1400.2
| /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: ignoring invalid character `\001' in script
| /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: syntax error in VERSION script
| collect2: ld returned 1 exit status
| make[4]: *** [libgdk_pixbuf-2.0.la] Error 1
| make[4]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory
`/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/gtk+-2.14.2'
| make: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task
failed: /home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
+-2.14.2-r1/temp/log.do_compile.15854
NOTE: package gtk+-2.14.2-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package gtk+-2.14.2: failed
ERROR: Build of /home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
+_2.14.2.bb do_compile failed
ERROR: Task 7 (/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
+_2.14.2.bb, do_compile) failed
NOTE: Tasks Summary: Attempted 1113 tasks of which 972 didn't need to be
rerun and 1 failed.
ERROR: '/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk+_2.14.2.bb'
failed
NOTE: build 200902041611: completed


On mer, 2009-02-04 at 12:29 +0100, Koen Kooi wrote:
> On 04-02-09 10:27, Paolo Cremonese wrote:
> > Sorry, don't know...
> >
> > Now the image works !
> >
> > Then I try to build a gpe-image, but i get an error at the last step.
> 
> Don't use dash as /bin/sh, use bash and rebuild libtool-cross and gtk+
> 
> regards,
> 
> Koen
> 
> >
> > Thanks in advance,
> >
> > Paolo
> >
> >
> >
> > | /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: ignoring invalid character `\001' in script
> > | /home/paolo/oe/stuff/build/tmp/cross/i586/lib/gcc/i586-angstrom-linux/4.2.4/../../../../i586-angstrom-linux/bin/ld:.libs/libgdk_pixbuf-2.0.ver:2: syntax error in VERSION script
> > | collect2: ld returned 1 exit status
> > | make[4]: *** [libgdk_pixbuf-2.0.la] Error 1
> > | make[4]: Leaving directory
> > `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> > +-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
> > | make[3]: *** [all-recursive] Error 1
> > | make[3]: Leaving directory
> > `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> > +-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
> > | make[2]: *** [all] Error 2
> > | make[2]: Leaving directory
> > `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> > +-2.14.2-r1/gtk+-2.14.2/gdk-pixbuf'
> > | make[1]: *** [all-recursive] Error 1
> > | make[1]: Leaving directory
> > `/home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> > +-2.14.2-r1/gtk+-2.14.2'
> > | make: *** [all] Error 2
> > | FATAL: oe_runmake failed
> > NOTE: Task
> > failed: /home/paolo/oe/stuff/build/tmp/work/i586-angstrom-linux/gtk
> > +-2.14.2-r1/temp/log.do_compile.22403
> > NOTE: package gtk+-2.14.2-r1: task do_compile: failed
> > ERROR: TaskFailed event exception, aborting
> > NOTE: package gtk+-2.14.2: failed
> > ERROR: Build of /home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
> > +_2.14.2.bb do_compile failed
> > ERROR: Task 951 (/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk
> > +_2.14.2.bb, do_compile) failed
> > NOTE: Tasks Summary: Attempted 1003 tasks of which 788 didn't need to be
> > rerun and 1 failed.
> > ERROR: '/home/paolo/oe/stuff/openembedded/packages/gtk+/gtk+_2.14.2.bb'
> > failed
> > NOTE: build 200902040809: completed
> >
> >
> >
> >
> >
> >
> > On lun, 2009-02-02 at 17:13 +0100, Marco Cavallini wrote:
> >> Paolo Cremonese ha scritto:
> >>> Fine, waiting for GRUB patch. (what is "hrw" ?)
> >>>
> >>> My target has not hard disk, only CF.
> >>> To run the image, do I need a RAMFS ?
> >>> And in this case, I have to add it to the GRUB "menu.lst" ?
> >> Paolo,
> >> hrw is Marcin Juszkiewicz, an OE developer and mantainer.
> >> GRUB patch was pushed this morning and is ready for use into git mainstream.
> >>
> >> Cordiali Saluti / Kindest Regards / mit freundlichen Grüssen
> >> --
> >> Marco Cavallini | KOAN sas | Bergamo - Italia
> >>   embedded and real-time software engineering
> >>     Atmel third party certified consultant
> >> Phone:+39-035-255.235 - Fax:+39-178-22.39.748
> >>        http://www.KoanSoftware.com
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: Build problems

[Marcin Juszkiewicz]

On Wednesday 04 of February 2009 16:48:53 Paolo Cremonese wrote:
> OK, changed DASH to BASH.
> Compiled libtool-cross OK.
>
> compiling gtk+ (bitbake gtk+), fails.

"bitbake -crebuild gtk+" is needed because gtk+ configure was done with 
dash.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz

build problems

[Justin Ferguson]

Hi,

So I have been attempting to build xen from source for a bit longer
than I care to admit. I'm trying very hard to stay within the realm of
supported/non-experimental which seems to vastly limit my options.
That is to say the 2.6.27 patch from novell is listed as
unsupported/undeveloped/experimental and the paravirtualization stuff
in 2.6.3x kernels is listed as experimental as well. This basically
leaves the 2.6.18 option available to me.

Trying to get it built has been a bit of a process, if you use the
tarball that pulls down from kernel.org (instead of mercurial), there
is a number of issues that made me finally move on to the mercurial
sources (ketchup breaks due to a bad regexp, there are compile time
errors in the kernel source [i.e. forgot to include limits.h], et
cetera). The mercurial version compiles cleanly, but then I run into a
run-time problem.

On boot it informs me that I need to use bzImage v2.08 instead of
v2.04. After some digging around, what it looks like to me is that xen
at some point was brought up to use v2.08 of the boot protocol and
this was never backported to the 2.6.18.8 kernel (v2.05 was released
in 2.6.20). This of course won't work (is there absolutely no one
actually using the default and supported option?). So I elected to use
the vmlinux/zImage version and I get the 'error: no multiboot header'
from grub (for both multiboot & linux directives). I get this for the
kernel that pulls down from mercurial and the tarball on the website.

My problems as best as I can tell appear to be a few things:

- Grub has changed and I *think* this relates back to why I can't seem
to boot the vmlinux image

- Xen 3.4.2 cannot boot a bzImage of the supported dom0 kernel


So this leaves me with the question, how exactly am I supposed to use
your product with?

Re: build problems

[Keir Fraser]

On 29/12/2009 06:24, "Justin Ferguson" <jnferguson@gmail.com> wrote:

> On boot it informs me that I need to use bzImage v2.08 instead of
> v2.04. After some digging around, what it looks like to me is that xen
> at some point was brought up to use v2.08 of the boot protocol and
> this was never backported to the 2.6.18.8 kernel (v2.05 was released
> in 2.6.20). This of course won't work (is there absolutely no one
> actually using the default and supported option?). So I elected to use
> the vmlinux/zImage version and I get the 'error: no multiboot header'
> from grub (for both multiboot & linux directives). I get this for the
> kernel that pulls down from mercurial and the tarball on the website.

I think you are setting up the bootloader incorrectly. What bootloader are
you using? If GRUB, you need a config entry like:
title XEN
  root (hd0,1)
  kernel /boot/xen.gz
  module /boot/vmlinuz-xen <kernel params>
  module /boot/initrd-xen

You get the idea. The main message here is that *Xen* is the kernel, not
Linux dom0. Linux kernel is specified as the first module; initrd as the
second module (if you have an initrd).

You can most assuredly use a 2.6.18 bzImage for dom0 -- Xen knows what to do
with it. Your problem in all cases is I think that you tried to boot dom0
kernel directly, without loading Xen as the kernel from grub's p.o.v.

This type of of question should go to the xen-users list, by the way.

 -- Keir

Re: build problems

[Ian Campbell]

On Tue, 2009-12-29 at 09:11 +0000, Keir Fraser wrote:
> 
> You can most assuredly use a 2.6.18 bzImage for dom0 -- Xen knows what
> to do with it. 

Unless someone backported the v2.08 bzImage format extensions (which I
don't think is the case) then you cannot boot a 2.6.18 bzImage under
Xen, that support relies on newer fields in the header. IIRC those
patches went into 2.6.27 upstream, although e.g. Debian backported them
to their 2.6.26 kernel.

For 2.6.18 I think you still need to use the old compressed-ELF style
kernels.

Ian.

Re: build problems

[Justin Ferguson]

>> You can most assuredly use a 2.6.18 bzImage for dom0 -- Xen knows what
>> to do with it.
>
> Unless someone backported the v2.08 bzImage format extensions (which I
> don't think is the case) then you cannot boot a 2.6.18 bzImage under
> Xen, that support relies on newer fields in the header. IIRC those
> patches went into 2.6.27 upstream, although e.g. Debian backported them
> to their 2.6.26 kernel.
>
> For 2.6.18 I think you still need to use the old compressed-ELF style
> kernels.

Which, may be a problem with my grub config-- but i dont think it is,
I can't seem to get grub 2 to boot the resultant vmlinux/zImage, it
just likes to tell me its missing the magic number-- which I'm
guessing, and my knowledge gets hazy here, is a result of it not being
a multiboot compatible image?

Re: build problems

[Ian Campbell]

On Tue, 2009-12-29 at 10:10 +0000, Justin Ferguson wrote: 
> >> You can most assuredly use a 2.6.18 bzImage for dom0 -- Xen knows what
> >> to do with it.
> >
> > Unless someone backported the v2.08 bzImage format extensions (which I
> > don't think is the case) then you cannot boot a 2.6.18 bzImage under
> > Xen, that support relies on newer fields in the header. IIRC those
> > patches went into 2.6.27 upstream, although e.g. Debian backported them
> > to their 2.6.26 kernel.
> >
> > For 2.6.18 I think you still need to use the old compressed-ELF style
> > kernels.
> 
> Which, may be a problem with my grub config-- but i dont think it is,
> I can't seem to get grub 2 to boot the resultant vmlinux/zImage, it
> just likes to tell me its missing the magic number-- which I'm
> guessing, and my knowledge gets hazy here, is a result of it not being
> a multiboot compatible image?

The kernel you use must be the toplevel vmlinux ELF file, optionally
stripped and optionally gzip compressed. This is not the same as a
zImage which is a format similar to to bzImage but not able to cope with
such large images (it is effectively obsolete).

I think there is a target in the 2.6.18-xen tree which will perform this
strip and compress step for you but I don't recall what it is, it might
be the "vmlinuz" target although note that people often rename whatever
image they have built to that name so if you find one lying around it
isn't necessarily in any particular format.

A correct 2.6.18-xen kernel should respond to the file command like
this: (I happened to have a 2.6.26-xen image hanging around, the output
should be the same for 2.6.18-xen) 
        $ file /boot/vmlinuz-2.6.26-2-xen-amd64 
        /boot/vmlinuz-2.6.26-2-xen-amd64: gzip compressed data, from Unix, last modified: Thu Aug 20 01:36:37 2009, max compression
        $ zcat /boot/vmlinuz-2.6.26-2-xen-amd64 | file -
        zcat /boot/vmlinuz-2.6.26-2-xen-amd64 | file -
        /dev/stdin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped

32 bit kernels will be similar.

The grub examples Keir gave are correct, you just need to be careful
about the kernel image you use. 

If you need to post again please include the exact grub config file you
are using and the precise error messages rather than paraphrasing. 

Ian.

Re: build problems

[Justin Ferguson]

I apologize in advance as my terminology on the various linux kernel
compression formats is not the best (up until today I thought bzImage
was just a bzip'd copy of the elf image, and the documentation here
uses a lot of conflicting terminology)-- I am not positive if it is
zImage or what format it is (other than I know it is not bzImage),
but:

jf@theory:/boot$ file vmlinux ; zcat vmlinuz | file -
vmlinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, stripped
/dev/stdin: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
statically linked, stripped

(I changed both file names to make them easy to type with tab
completion as ive been doing a lot of rebooting as of late)

> The kernel you use must be the toplevel vmlinux ELF file, optionally
> stripped and optionally gzip compressed. This is not the same as a
> zImage which is a format similar to to bzImage but not able to cope with
> such large images (it is effectively obsolete).

When I attempt to boot either of these kernels from the command line,
I get the (presumably grub due to the lack of verbosity) invalid magic
error.  Where I am unclear on grub is whether I am supposed to be
using 'multiboot' or 'linux' as the operand (to replace 'kernel'), the
bzimage i needed multiboot, but none of the images ive created have
contained a (findable) multiboot header (per mbchk),

That said I may be making things unnecessarily stupid on myself by
using some new-fangled version of grub (that shipped with the distro).
Regardless of whether I am doing something wrong with grub, one of the
resulting images should boot, however all are returning the magic
error.

> I think there is a target in the 2.6.18-xen tree which will perform this
> strip and compress step for you but I don't recall what it is, it might
> be the "vmlinuz" target although note that people often rename whatever
> image they have built to that name so if you find one lying around it
> isn't necessarily in any particular format.

Well a make kernels leaves you with the top level image necessary (or
other ones in the arch directories). A full make world/make install
installs a bzImage. The implication here of course is that the default
image installed from a make install is the bzImage that cannot
possibly work. (v2.04-v2.08 thing)

> If you need to post again please include the exact grub config file you
> are using and the precise error messages rather than paraphrasing.

So, the grub.cfg I have at the moment contains the entry from the last
make world/make install, since then I've attempted to boot the top
level images on the command line as described. To satify you're
request, the relevant entry is as follows:

menuentry "xen" {
        multiboot /boot/xen-3.4.gz dom0_mem=512M
        module /boot/vmlinuz-2.6.18-xen root=/dev/sda5 ro
        module /boot/initrd-2.6-xen.img
}

I'm not attempting to clutter the dev list with user list type things,
but I'm fairly certain there is a bug here.

justin

Re: build problems

[Ian Campbell]

On Tue, 2009-12-29 at 12:29 +0000, Justin Ferguson wrote:
> That said I may be making things unnecessarily stupid on myself by
> using some new-fangled version of grub (that shipped with the distro).

Have you tried using the distro supplied Xen and kernel packages?

> > I think there is a target in the 2.6.18-xen tree which will perform this
> > strip and compress step for you but I don't recall what it is, it might
> > be the "vmlinuz" target although note that people often rename whatever
> > image they have built to that name so if you find one lying around it
> > isn't necessarily in any particular format.
> 
> Well a make kernels leaves you with the top level image necessary (or
> other ones in the arch directories). A full make world/make install
> installs a bzImage. The implication here of course is that the default
> image installed from a make install is the bzImage that cannot
> possibly work. (v2.04-v2.08 thing)

If you do "make world KERNELS=linux-2.6-xen" it will build a 2.6.18-xen
kernel and do the correct thing by not using bzImage. I guess you are
using the default which I think is equivalent to KERNELS=linux-2.6-pvops
and assumes bzImage support is new enough, if you just drop in some
other kernel than the one it would clone itself it may not work.

> > If you need to post again please include the exact grub config file you
> > are using and the precise error messages rather than paraphrasing.
> 
> So, the grub.cfg I have at the moment contains the entry from the last
> make world/make install, since then I've attempted to boot the top
> level images on the command line as described. To satify you're
> request, the relevant entry is as follows:
> 
> menuentry "xen" {
>         multiboot /boot/xen-3.4.gz dom0_mem=512M
>         module /boot/vmlinuz-2.6.18-xen root=/dev/sda5 ro
>         module /boot/initrd-2.6-xen.img
> }

IIRC grub2 (which is what you appear to be using) strips the image name
itself, while grub1/legacy did not. I think you need a placeholder
command line argument to work around this, perhaps a "." , e.g.
"multiboot /boot/xen-3.4.gz . dom0_mem" and "module /boot/vmlinuz-... .
root=etc..."

I've not used grub2 myself though and I'm not sure if this relates the
the magic error you refer too.

> I'm not attempting to clutter the dev list with user list type things,
> but I'm fairly certain there is a bug here.

I'm pretty certain it is a configuration error, which might translate to
a bug in the docs or something like that. You will likely find more
people who have been through this on the users list.

Ian.

Re: build problems

[Justin Ferguson]

> IIRC grub2 (which is what you appear to be using) strips the image name
> itself, while grub1/legacy did not. I think you need a placeholder
> command line argument to work around this, perhaps a "." , e.g.
> "multiboot /boot/xen-3.4.gz . dom0_mem" and "module /boot/vmlinuz-... .
> root=etc..."
>
> I've not used grub2 myself though and I'm not sure if this relates the
> the magic error you refer too.

grub2 is a first for me as well, and for anyone who might stumble upon
this thread with this problem-- this was the fix. It must be an issue
where the structure used doesn't match the data and the magic member
ends up pointing to the wrong spot (or something similar).

Build problems

[Ananth, Rajesh]

[-- Attachment #1: Type: text/plain, Size: 3969 bytes --]

Hi,


I am new to the OpenBmc development, and as a first step I am trying to build the "bitbake obmc-phosphor-image" for the s2600wf platform. I have followed the instructions as per the OpenBmc git page.



I could see that the build is not validated for Ubuntu-24.04 and it fails with some network related errors. I don't have any firewall restrictions. For a starter like me, what would be the ideal base Kernel/distribution to get started with?




My build environment is:
====================
Linux bld-ub24s-openbmc 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux



Output from the bitbake:

=======================
WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |########################################################################################################| Time: 0:00:02
Loaded 4747 entries from dependency cache.
Parsing recipes: 100% |######################################################################################################| Time: 0:00:00
Parsing of 2864 .bb files complete (2863 cached, 1 parsed). 4748 targets, 673 skipped, 0 masked, 0 errors.
WARNING: No bb files in default matched BBFILE_PATTERN_s2600wf ''
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "2.9.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-24.04"
TARGET_SYS           = "arm-openbmc-linux-gnueabi"
MACHINE              = "s2600wf"
DISTRO               = "openbmc-phosphor"
DISTRO_VERSION       = "nodistro.0"
TUNE_FEATURES        = "arm thumb arm1176jzs"
TARGET_FPU           = "soft"
meta
meta-oe
meta-networking
meta-python
meta-phosphor
meta-aspeed
meta-intel-openbmc
meta-s2600wf         = "master:ecb9886523248ce726b2a452d12a48234d126fc5"

Sstate summary: Wanted 2809 Local 0 Mirrors 0 Missed 2809 Current 2 (0% match, 0% complete)#######################           | ETA:  0:00:00
Initialising tasks: 100% |###################################################################################################| Time: 0:00:04
NOTE: Executing Tasks
ERROR: PermissionError: [Errno 1] Operation not permitted

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/rajesh/openbmc/poky/bitbake/bin/bitbake-worker", line 278, in child
    bb.utils.disable_network(uid, gid)
  File "/home/rajesh/openbmc/poky/bitbake/lib/bb/utils.py", line 1696, in disable_network
    with open("/proc/self/uid_map", "w") as f:
PermissionError: [Errno 1] Operation not permitted

ERROR: PermissionError: [Errno 1] Operation not permitted

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/rajesh/openbmc/poky/bitbake/bin/bitbake-worker", line 278, in child
    bb.utils.disable_network(uid, gid)
  File "/home/rajesh/openbmc/poky/bitbake/lib/bb/utils.py", line 1696, in disable_network
    with open("/proc/self/uid_map", "w") as f:
PermissionError: [Errno 1] Operation not permitted

ERROR: Task (/home/rajesh/openbmc/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_prepare_recipe_sysroot) failed with exit code '1'
ERROR: Task (/home/rajesh/openbmc/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_unpack) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5 tasks of which 3 didn't need to be rerun and 2 failed.

Summary: 2 tasks failed:
  /home/rajesh/openbmc/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_prepare_recipe_sysroot
  /home/rajesh/openbmc/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_unpack
Summary: There were 2 WARNING messages.
Summary: There were 2 ERROR messages, returning a non-zero exit code.





[-- Attachment #2: Type: text/html, Size: 18015 bytes --]

Re: Build problems

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

On Mon, Jun 03, 2024 at 11:34:52PM +0000, Ananth, Rajesh wrote:
> WARNING: Host distribution "ubuntu-24.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.

> Traceback (most recent call last):
>   File "/home/rajesh/openbmc/poky/bitbake/bin/bitbake-worker", line 278, in child
>     bb.utils.disable_network(uid, gid)
>   File "/home/rajesh/openbmc/poky/bitbake/lib/bb/utils.py", line 1696, in disable_network
>     with open("/proc/self/uid_map", "w") as f:
> PermissionError: [Errno 1] Operation not permitted
> 
> ERROR: PermissionError: [Errno 1] Operation not permitted

This is a compatibility problem between bitbake and Ubuntu 24.04 which is
not yet resolved.  They are discussing this upstream already.

https://lists.yoctoproject.org/g/docs/topic/106220010#msg5234

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]