[linux-next] build failure

[linux-next] build failure

[divya]

Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.


   drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
   drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
   drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
   drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
   make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
   make[2]: *** [drivers/net/ixgbe] Error 2
   make[2]: *** Waiting for unfinished jobs....
   make[1]: *** [drivers/net] Error 2
   make: *** [drivers] Error 2

Thanks
Divya

Re: build failure

[John Fastabend]

divya wrote:
> Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.
> 
> 
>    drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
>    drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
>    drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
>    drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
>    make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
>    make[2]: *** [drivers/net/ixgbe] Error 2
>    make[2]: *** Waiting for unfinished jobs....
>    make[1]: *** [drivers/net] Error 2
>    make: *** [drivers] Error 2
> 
> Thanks
> Divya
> 
> 

Hi Divya,

Jeff should have a fix for this in his queue already.  This is caused by 
building with CONFIG_FCOE and without CONFIG_IXGBE_DCB.

Thanks,
John.

Re: [linux-next] build failure

[John Fastabend]

divya wrote:
> Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.
> 
> 
>    drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
>    drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
>    drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
>    drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
>    make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
>    make[2]: *** [drivers/net/ixgbe] Error 2
>    make[2]: *** Waiting for unfinished jobs....
>    make[1]: *** [drivers/net] Error 2
>    make: *** [drivers] Error 2
> 
> Thanks
> Divya
> 
> 

Hi Divya,

Jeff should have a fix for this in his queue already.  This is caused by 
building with CONFIG_FCOE and without CONFIG_IXGBE_DCB.

Thanks,
John.

Re: [linux-next] build failure

[John Fastabend]

divya wrote:
> Yestersday's linux-next(2.6.35_next_20100802) build fails with the following error on both system p and x.
> 
> 
>    drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_select_queue':
>    drivers/net/ixgbe/ixgbe_main.c:6159: error: 'struct ixgbe_fcoe' has no member named 'up'
>    drivers/net/ixgbe/ixgbe_main.c: In function 'ixgbe_xmit_frame':
>    drivers/net/ixgbe/ixgbe_main.c:6221: error: 'struct ixgbe_fcoe' has no member named 'up'
>    make[3]: *** [drivers/net/ixgbe/ixgbe_main.o] Error 1
>    make[2]: *** [drivers/net/ixgbe] Error 2
>    make[2]: *** Waiting for unfinished jobs....
>    make[1]: *** [drivers/net] Error 2
>    make: *** [drivers] Error 2
> 
> Thanks
> Divya
> 
> 

Hi Divya,

Jeff should have a fix for this in his queue already.  This is caused by 
building with CONFIG_FCOE and without CONFIG_IXGBE_DCB.

Thanks,
John.

Build failure

[Andreas Müller]

Ciao,

with latest layer HEADS and build from scratch I get:

KeyError: 'getpwnam(): name not found: root'

ERROR: The stack trace of python calls that resulted in this
exception/failure was:
ERROR:   File "fixup_perms", line 227, in <module>
ERROR:
ERROR:   File "fixup_perms", line 155, in fixup_perms
ERROR:
ERROR:   File "fixup_perms", line 32, in __init__
ERROR:
ERROR:   File "fixup_perms", line 42, in _setdir
ERROR:
ERROR:   File "fixup_perms", line 66, in _procuid
ERROR:
ERROR: The code that was being executed was:
ERROR:      0223:                    each_file = os.path.join(root, f)
ERROR:      0224:                    fix_perms(each_file,
fs_perms_table[dir].fmode, fs_perms_table[dir].fuid,
fs_perms_table[dir].fgid, dir)
ERROR:      0225:
ERROR:      0226:
ERROR:  *** 0227:fixup_perms(d)
ERROR:      0228:
ERROR: [From file: 'fixup_perms', lineno: 227, function: <module>]
ERROR:      0151:    for path in target_path_vars:
ERROR:      0152:        dir = d.getVar(path, True) or ""
ERROR:      0153:        if dir == "":
ERROR:      0154:            continue
ERROR:  *** 0155:        fs_perms_table[dir] =
fs_perms_entry(bb.data.expand("%s 0755 root root false - - -" % (dir),
d))
ERROR:      0156:
ERROR:      0157:    # Now we actually load from the configuration files
ERROR:      0158:    for conf in get_fs_perms_list(d).split():
ERROR:      0159:        if os.path.exists(conf):
ERROR: [From file: 'fixup_perms', lineno: 155, function: fixup_perms]
ERROR: Function failed: fixup_perms
ERROR: Logfile of failure stored in:
/home/andreas/tmp/oe-core-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/util-macros-1_1.17-r0/temp/log.do_package.28653
ERROR: Task 4450
(/home/andreas/data/oe-core/sources/openembedded-core/meta/recipes-graphics/xorg-util/util-macros_1.17.bb,
do_package) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3985 tasks of which 397 didn't need to
be rerun and 1 failed.

The only additional information I found up to now:

* the code mentioned in error message is found in package.bbclass.
* in sysroot/etc/passwd there is a line 'root::0:0:root:/home/root:/bin/sh'

Any ideas?

Andreas

Re: Build failure

[Andreas Müller]

On Wed, Nov 14, 2012 at 10:15 AM, Andreas Müller
<schnitzeltony@googlemail.com> wrote:
> Ciao,
>
> with latest layer HEADS and build from scratch I get:
>
> KeyError: 'getpwnam(): name not found: root'
>
> ERROR: The stack trace of python calls that resulted in this
> exception/failure was:
> ERROR:   File "fixup_perms", line 227, in <module>
> ERROR:
> ERROR:   File "fixup_perms", line 155, in fixup_perms
> ERROR:
> ERROR:   File "fixup_perms", line 32, in __init__
> ERROR:
> ERROR:   File "fixup_perms", line 42, in _setdir
> ERROR:
> ERROR:   File "fixup_perms", line 66, in _procuid
> ERROR:
> ERROR: The code that was being executed was:
> ERROR:      0223:                    each_file = os.path.join(root, f)
> ERROR:      0224:                    fix_perms(each_file,
> fs_perms_table[dir].fmode, fs_perms_table[dir].fuid,
> fs_perms_table[dir].fgid, dir)
> ERROR:      0225:
> ERROR:      0226:
> ERROR:  *** 0227:fixup_perms(d)
> ERROR:      0228:
> ERROR: [From file: 'fixup_perms', lineno: 227, function: <module>]
> ERROR:      0151:    for path in target_path_vars:
> ERROR:      0152:        dir = d.getVar(path, True) or ""
> ERROR:      0153:        if dir == "":
> ERROR:      0154:            continue
> ERROR:  *** 0155:        fs_perms_table[dir] =
> fs_perms_entry(bb.data.expand("%s 0755 root root false - - -" % (dir),
> d))
> ERROR:      0156:
> ERROR:      0157:    # Now we actually load from the configuration files
> ERROR:      0158:    for conf in get_fs_perms_list(d).split():
> ERROR:      0159:        if os.path.exists(conf):
> ERROR: [From file: 'fixup_perms', lineno: 155, function: fixup_perms]
> ERROR: Function failed: fixup_perms
> ERROR: Logfile of failure stored in:
> /home/andreas/tmp/oe-core-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/util-macros-1_1.17-r0/temp/log.do_package.28653
> ERROR: Task 4450
> (/home/andreas/data/oe-core/sources/openembedded-core/meta/recipes-graphics/xorg-util/util-macros_1.17.bb,
> do_package) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 3985 tasks of which 397 didn't need to
> be rerun and 1 failed.
>
> The only additional information I found up to now:
>
> * the code mentioned in error message is found in package.bbclass.
> * in sysroot/etc/passwd there is a line 'root::0:0:root:/home/root:/bin/sh'
>
> Any ideas?
>
Additional info: After running

bitbake -ccleansstate util-macros util-macros-native

the build continues as without issues. Some missing dependency race?

Andreas

Build Failure

[Colin Minihan]

On Ubuntu 10.04 attempting to run

git clone git://linuxtv.org/media_build.git
cd media_build
./check_needs.pl
make -C linux/ download
make -C linux/ untar
make stagingconfig
make

 results in the following failure
...
  CC [M]  /home/colm/media_build/v4l/lirc_zilog.o
/home/colm/media_build/v4l/lirc_zilog.c: In function 'destroy_rx_kthread':
/home/colm/media_build/v4l/lirc_zilog.c:238: error: implicit
declaration of function 'IS_ERR_OR_NULL'
make[3]: *** [/home/colm/media_build/v4l/lirc_zilog.o] Error 1
make[2]: *** [_module_/home/colm/media_build/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.32-31-generic'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/colm/media_build/v4l'
make: *** [all] Error 2

Re: Build Failure

[Andy Walls]

On Sat, 2011-04-30 at 10:31 -0400, Colin Minihan wrote:
> On Ubuntu 10.04 attempting to run
> 
> git clone git://linuxtv.org/media_build.git
> cd media_build
> ./check_needs.pl
> make -C linux/ download
> make -C linux/ untar
> make stagingconfig
> make
> 
>  results in the following failure
> ...
>   CC [M]  /home/colm/media_build/v4l/lirc_zilog.o
> /home/colm/media_build/v4l/lirc_zilog.c: In function 'destroy_rx_kthread':
> /home/colm/media_build/v4l/lirc_zilog.c:238: error: implicit
> declaration of function 'IS_ERR_OR_NULL'

Well, IS_ERR_OR_NULL() went into the kernel in December 2009:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=603c4ba96be998a8dd7a6f9b23681c49acdf4b64

so it should be in kernel version 2.6.33 and later.

If you don't want to generate a patch for the media_build backward
compatability build system, you can probably just patch your kernel
header file or trivially hack the function it into 

	drivers/staging/lirc/lirc_zilog.c

to get past your current build error.  But I suspect you'll run into
more errors.  When I make changes to a module (like lirc_zilog.c), I
tend to use the latest kernel interfaces at the time of the changes.

If you don't need lirc_zilog.ko built, then configure the build system
to not build the module.

Regards,
Andy

> make[3]: *** [/home/colm/media_build/v4l/lirc_zilog.o] Error 1
> make[2]: *** [_module_/home/colm/media_build/v4l] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.32-31-generic'
> make[1]: *** [default] Error 2
> make[1]: Leaving directory `/home/colm/media_build/v4l'
> make: *** [all] Error 2
> --

Re: Build Failure

[Mauro Carvalho Chehab]

Em 30-04-2011 13:10, Andy Walls escreveu:
> On Sat, 2011-04-30 at 10:31 -0400, Colin Minihan wrote:
>> On Ubuntu 10.04 attempting to run
>>
>> git clone git://linuxtv.org/media_build.git
>> cd media_build
>> ./check_needs.pl
>> make -C linux/ download
>> make -C linux/ untar
>> make stagingconfig
>> make
>>
>>  results in the following failure
>> ...
>>   CC [M]  /home/colm/media_build/v4l/lirc_zilog.o
>> /home/colm/media_build/v4l/lirc_zilog.c: In function 'destroy_rx_kthread':
>> /home/colm/media_build/v4l/lirc_zilog.c:238: error: implicit
>> declaration of function 'IS_ERR_OR_NULL'
> 
> Well, IS_ERR_OR_NULL() went into the kernel in December 2009:
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=603c4ba96be998a8dd7a6f9b23681c49acdf4b64
> 
> so it should be in kernel version 2.6.33 and later.

This is defined at include/linux/err.h as:

#define IS_ERR_VALUE(x) unlikely((x) >= (unsigned long)-MAX_ERRNO)

static inline long __must_check IS_ERR_OR_NULL(const void *ptr)
{
	return !ptr || IS_ERR_VALUE((unsigned long)ptr);
}

> 
> If you don't want to generate a patch for the media_build backward
> compatability build system, you can probably just patch your kernel
> header file or trivially hack the function it into 
> 
> 	drivers/staging/lirc/lirc_zilog.c
> 
> to get past your current build error.  But I suspect you'll run into
> more errors.  When I make changes to a module (like lirc_zilog.c), I
> tend to use the latest kernel interfaces at the time of the changes.
> 
> If you don't need lirc_zilog.ko built, then configure the build system
> to not build the module.

To make it work, it is probably as simple as adding this into v4l/compat.h:

#if NEED_IS_ERR_OR_NULL
#define IS_ERR_OR_NULL(ptr) (!(ptr) || IS_ERR_VALUE((unsigned long)(ptr)))
#endif


And:

check_file_for_func("include/linux/err.h", "IS_ERR_OR_NULL", "NEED_IS_ERR_OR_NULL");

at v4l/scripts/make_config_compat.pl,

as the enclosed (not tested) patch.

Please test it and, if it wors, ping us for its inclusion at media_tree.git. Otherwise,
feel free to fix it and submit us the fix.

Thanks!
Mauro

---

Add backward support for IS_ERR_OR_NULL

Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

diff --git a/v4l/compat.h b/v4l/compat.h
index bc8d71f..9dbe54f 100644
--- a/v4l/compat.h
+++ b/v4l/compat.h
@@ -796,4 +796,8 @@ static inline int snd_ctl_enum_info(struct snd_ctl_elem_info *info, unsigned int
 #define usleep_range(min, max) msleep(min/1000)
 #endif
 
+#if NEED_IS_ERR_OR_NULL
+#define IS_ERR_OR_NULL(ptr) (!(ptr) || IS_ERR_VALUE((unsigned long)(ptr)))
+#endif
+
 #endif /*  _COMPAT_H */
diff --git a/v4l/scripts/make_config_compat.pl b/v4l/scripts/make_config_compat.pl
index a426134..01f6c30 100755
--- a/v4l/scripts/make_config_compat.pl
+++ b/v4l/scripts/make_config_compat.pl
@@ -492,6 +492,7 @@ sub check_other_dependencies()
 	check_file_for_func("include/sound/control.h", "snd_ctl_enum_info", "NEED_SND_CTL_ENUM_INFO");
 	check_file_for_func("include/linux/sysfs.h", "sysfs_attr_init", "NEED_SYSFS_ATTR_INIT");
 	check_file_for_func("include/linux/delay.h", "usleep_range", "NEED_USLEEP_RANGE");
+	check_file_for_func("include/linux/err.h", "IS_ERR_OR_NULL", "NEED_IS_ERR_OR_NULL");
 }
 
 # Do the basic rules

Re: Build Failure

[Vincent McIntyre]

On 5/1/11, Colin Minihan <colin.minihan@gmail.com> wrote:
> On Ubuntu 10.04 attempting to run
>
> git clone git://linuxtv.org/media_build.git
> cd media_build
> ./check_needs.pl
> make -C linux/ download
> make -C linux/ untar
> make stagingconfig
> make
>
>  results in the following failure
> ...

I see this too (platform details below) but only if I do the 'make
stagingconfig' step
which I don't usually need to. The patch Mauro supplied worked for me;
I just edited
the two files involved and reran 'make' at the point at which the
build had failed.
v4l/config-compat.h had the expected extra #define in it and the build
completed ok.
I haven't tested the resulting module as I don't have the relevant hardware.

Cheers
Vince

platform details:

$ cat /etc/issue
Ubuntu 10.04.2 LTS \n \l
$ uname -a
Linux ubuntu 2.6.32-31-generic #61-Ubuntu SMP Fri Apr 8 18:24:35 UTC
2011 i686 GNU/Linux
$ cat v4l/.version
VERSION=2
PATCHLEVEL:=6
SUBLEVEL:=32
KERNELRELEASE:=2.6.32-31-generic

Build failure

[Gary Thomas]

Trying to build poky-image-sato-live:
   OE Build Configuration:
   BB_VERSION        = "1.11.0"
   METADATA_BRANCH   = "master"
   METADATA_REVISION = "74783fec56d6ced1a793b36410233472e7daf445"
   TARGET_ARCH       = "i586"
   TARGET_OS         = "linux"
   MACHINE           = "qemux86"
   DISTRO            = "poky"
   DISTRO_VERSION    = "0.9+snapshot-20110124"
   TARGET_FPU        = ""

ERROR: Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
ERROR: '/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb' failed
ERROR: Logfile of failure stored in: /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954
Log data follows:
| install: cannot stat `/home/local/pc_poky/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No such file or directory
| Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
| ERROR: Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
NOTE: package poky-image-sato-live-1.0-r0: task build_boot_bin: Failed
ERROR: Task 9 (/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb, do_bootimg) failed with exit code '1'

n.b. I tried to access BugZilla to report this, but that
failed as well :-(

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Build failure

[Tom Zanussi]

On Mon, 2011-01-24 at 13:36 -0800, Gary Thomas wrote:
> Trying to build poky-image-sato-live:
>    OE Build Configuration:
>    BB_VERSION        = "1.11.0"
>    METADATA_BRANCH   = "master"
>    METADATA_REVISION = "74783fec56d6ced1a793b36410233472e7daf445"
>    TARGET_ARCH       = "i586"
>    TARGET_OS         = "linux"
>    MACHINE           = "qemux86"
>    DISTRO            = "poky"
>    DISTRO_VERSION    = "0.9+snapshot-20110124"
>    TARGET_FPU        = ""
> 
> ERROR: Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
> ERROR: '/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb' failed
> ERROR: Logfile of failure stored in: /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954
> Log data follows:
> | install: cannot stat `/home/local/pc_poky/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No such file or directory
> | Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
> | ERROR: Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
> NOTE: package poky-image-sato-live-1.0-r0: task build_boot_bin: Failed
> ERROR: Task 9 (/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb, do_bootimg) failed with exit code '1'
> 
> n.b. I tried to access BugZilla to report this, but that
> failed as well :-(
> 

The problem is this commit:

commit bc9d2fbfd4eaad0df5647dd5d07dfb9fcff80ff3
Author: Dongxiao Xu <dongxiao.xu@intel.com>
Date:   Tue Jan 18 16:17:58 2011 +0800

    staging: Use relative path in sysroot-destdir for target recipes

Dongxiao is aware of the problem and working on a fix.  In the meantime,
you could try the fix below from Dongxiao, cut and pasted from IRC, or
back up to the commit before that...

Hope that helps,

Tom

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 9d3b2bb..d1b5398 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -512,3 +512,5 @@ EXPORT_FUNCTIONS do_deploy
PACKAGES =+ "perf"
FILES_perf = "${bindir}/* \
${libexecdir}"
+
+do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR}/${MACHINE}${HOST_VENDOR}-${HOST_OS}/"

Re: Build failure

[Gary Thomas]

On 01/24/2011 02:52 PM, Tom Zanussi wrote:
> On Mon, 2011-01-24 at 13:36 -0800, Gary Thomas wrote:
>> Trying to build poky-image-sato-live:
>>     OE Build Configuration:
>>     BB_VERSION        = "1.11.0"
>>     METADATA_BRANCH   = "master"
>>     METADATA_REVISION = "74783fec56d6ced1a793b36410233472e7daf445"
>>     TARGET_ARCH       = "i586"
>>     TARGET_OS         = "linux"
>>     MACHINE           = "qemux86"
>>     DISTRO            = "poky"
>>     DISTRO_VERSION    = "0.9+snapshot-20110124"
>>     TARGET_FPU        = ""
>>
>> ERROR: Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
>> ERROR: '/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb' failed
>> ERROR: Logfile of failure stored in: /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954
>> Log data follows:
>> | install: cannot stat `/home/local/pc_poky/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No such file or directory
>> | Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
>> | ERROR: Function 'build_boot_bin' failed (see /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/temp/log.do_bootimg.10954 for further information)
>> NOTE: package poky-image-sato-live-1.0-r0: task build_boot_bin: Failed
>> ERROR: Task 9 (/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb, do_bootimg) failed with exit code '1'
>>
>> n.b. I tried to access BugZilla to report this, but that
>> failed as well :-(
>>
>
> The problem is this commit:
>
> commit bc9d2fbfd4eaad0df5647dd5d07dfb9fcff80ff3
> Author: Dongxiao Xu<dongxiao.xu@intel.com>
> Date:   Tue Jan 18 16:17:58 2011 +0800
>
>      staging: Use relative path in sysroot-destdir for target recipes
>
> Dongxiao is aware of the problem and working on a fix.  In the meantime,
> you could try the fix below from Dongxiao, cut and pasted from IRC, or
> back up to the commit before that...
>
> Hope that helps,
>
> Tom
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 9d3b2bb..d1b5398 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -512,3 +512,5 @@ EXPORT_FUNCTIONS do_deploy
> PACKAGES =+ "perf"
> FILES_perf = "${bindir}/* \
> ${libexecdir}"
> +
> +do_populate_sysroot[sstate-outputdirs] = "${STAGING_DIR}/${MACHINE}${HOST_VENDOR}-${HOST_OS}/"

Yes, this helped, but I did have to run 'bitbake virtual/kernel -c clean'
before it made any difference.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Build failure

[Tian, Kevin]

> From: Gary Thomas
> Sent: Tuesday, January 25, 2011 7:06 AM
> 
> On 01/24/2011 02:52 PM, Tom Zanussi wrote:
> > On Mon, 2011-01-24 at 13:36 -0800, Gary Thomas wrote:
> >> Trying to build poky-image-sato-live:
> >>     OE Build Configuration:
> >>     BB_VERSION        = "1.11.0"
> >>     METADATA_BRANCH   = "master"
> >>     METADATA_REVISION =
> "74783fec56d6ced1a793b36410233472e7daf445"
> >>     TARGET_ARCH       = "i586"
> >>     TARGET_OS         = "linux"
> >>     MACHINE           = "qemux86"
> >>     DISTRO            = "poky"
> >>     DISTRO_VERSION    = "0.9+snapshot-20110124"
> >>     TARGET_FPU        = ""
> >>
> >> ERROR: Function 'build_boot_bin' failed (see
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954 for further information)
> >> ERROR:
> '/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb' failed
> >> ERROR: Logfile of failure stored in:
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954
> >> Log data follows:
> >> | install: cannot stat
> `/home/local/pc_poky/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No
> such file or directory
> >> | Function 'build_boot_bin' failed (see
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954 for further information)
> >> | ERROR: Function 'build_boot_bin' failed (see
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954 for further information)
> >> NOTE: package poky-image-sato-live-1.0-r0: task build_boot_bin: Failed
> >> ERROR: Task 9
> (/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb,
> do_bootimg) failed with exit code '1'
> >>
> >> n.b. I tried to access BugZilla to report this, but that
> >> failed as well :-(
> >>
> >
> > The problem is this commit:
> >
> > commit bc9d2fbfd4eaad0df5647dd5d07dfb9fcff80ff3
> > Author: Dongxiao Xu<dongxiao.xu@intel.com>
> > Date:   Tue Jan 18 16:17:58 2011 +0800
> >
> >      staging: Use relative path in sysroot-destdir for target recipes
> >
> > Dongxiao is aware of the problem and working on a fix.  In the meantime,
> > you could try the fix below from Dongxiao, cut and pasted from IRC, or
> > back up to the commit before that...
> >
> > Hope that helps,
> >
> > Tom
> >
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index 9d3b2bb..d1b5398 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -512,3 +512,5 @@ EXPORT_FUNCTIONS do_deploy
> > PACKAGES =+ "perf"
> > FILES_perf = "${bindir}/* \
> > ${libexecdir}"
> > +
> > +do_populate_sysroot[sstate-outputdirs] =
> "${STAGING_DIR}/${MACHINE}${HOST_VENDOR}-${HOST_OS}/"
> 
> Yes, this helped, but I did have to run 'bitbake virtual/kernel -c clean'
> before it made any difference.
> 
> Thanks

PR needs to be bumped in this case, which however reminds me one confusing area
I didn't think about before.

How do we handle the class changes which are inherited by many recipes? Generally
we need bump PRs once the output of a recipe gets changed, but it looks class file
is usually ignored.

Is there any easy way to have all recipes inheriting same class file bumping their PRs,
or has to be done by manual check?

Thanks
Kevin

Re: Build failure

[Richard Purdie]

On Tue, 2011-01-25 at 08:00 +0800, Tian, Kevin wrote:
> PR needs to be bumped in this case, which however reminds me one confusing area
> I didn't think about before.
> 
> How do we handle the class changes which are inherited by many recipes? Generally
> we need bump PRs once the output of a recipe gets changed, but it looks class file
> is usually ignored.
> 
> Is there any easy way to have all recipes inheriting same class file bumping their PRs,
> or has to be done by manual check?

This is a problem and its one I'm thinking we address with the sstate
checksums being part of the stamps ultimately.

Cheers,

Richard

Build failure

[jonr]

Hello,

Following the recent update on the pv_ops page on how to grab latest  
git repo of kernel and xen, and then trying to use Boris' page I get a  
failed kernel build.

I had built this yesterday with no problems and booted into a working dom0.

During 'make' I get the following error:

drivers/w1/masters/ds2490.c:826: warning: passing argument 2 of  
'ds_write_block' discards qualifiers from pointer target type
   CC [M]  drivers/w1/masters/ds2482.o
   LD      drivers/w1/slaves/built-in.o
   CC [M]  drivers/w1/slaves/w1_therm.o
   CC [M]  drivers/w1/slaves/w1_smem.o
   CC [M]  drivers/w1/slaves/w1_ds2433.o
   CC [M]  drivers/w1/slaves/w1_ds2760.o
   LD      drivers/w1/built-in.o
   CC [M]  drivers/w1/w1.o
   CC [M]  drivers/w1/w1_int.o
   CC [M]  drivers/w1/w1_family.o
   CC [M]  drivers/w1/w1_netlink.o
   CC [M]  drivers/w1/w1_io.o
   LD [M]  drivers/w1/wire.o
   CC      drivers/xen/grant-table.o
   CC      drivers/xen/features.o
   CC      drivers/xen/events.o
   CC      drivers/xen/manage.o
   CC      drivers/xen/biomerge.o
   CC      drivers/xen/blkback/blkback.o
   CC      drivers/xen/blkback/xenbus.o
   CC      drivers/xen/blkback/interface.o
   CC      drivers/xen/blkback/vbd.o
   LD      drivers/xen/blkback/blkbk.o
   LD      drivers/xen/blkback/built-in.o
   CC      drivers/xen/netback/netback.o
drivers/xen/netback/netback.c: In function 'netif_be_start_xmit':
drivers/xen/netback/netback.c:337: error: implicit declaration of  
function '__mod_timer'
make[3]: *** [drivers/xen/netback/netback.o] Error 1
make[2]: *** [drivers/xen/netback] Error 2
make[1]: *** [drivers/xen] Error 2
make: *** [drivers] Error 2

Re: Build failure

[Jeremy Fitzhardinge]

jonr@destar.net wrote:
> Hello,
>
> Following the recent update on the pv_ops page on how to grab latest 
> git repo of kernel and xen, and then trying to use Boris' page I get a 
> failed kernel build.
>
> I had built this yesterday with no problems and booted into a working 
> dom0.

Fixing it up now.

    J

Re: Build failure

[jonr]

Quoting Jeremy Fitzhardinge <jeremy@goop.org>:

> jonr@destar.net wrote:
>> Hello,
>>
>> Following the recent update on the pv_ops page on how to grab   
>> latest git repo of kernel and xen, and then trying to use Boris'   
>> page I get a failed kernel build.
>>
>> I had built this yesterday with no problems and booted into a working dom0.
>
> Fixing it up now.
>
>    J

Fixed and booted into dom0.

Thanks Jeremy!

build failure

[Christoph Egger]

Hi,

c/s 18166 causes below build failure.
The compiler does not find ./tools/include/xen/xen.h due to
a missing -I include path parameter.

In file included from ../util.h:4,
                 from tcgbios.c:27:
../../../hvmloader/acpi/acpi2_0.h:22:21: error: xen/xen.h: No such file or 
directory
gmake[9]: *** [tcgbios.o] Error 1
gmake[9]: Leaving directory 
`/root/xen-staging-netbsd.hg/tools/firmware/rombios/32bit/tcgbios
gmake[8]: *** [subdir-all-tcgbios] Error 2
gmake[8]: Leaving directory 
`/root/xen-staging-netbsd.hg/tools/firmware/rombios/32bit'
gmake[7]: *** [subdirs-all] Error 2
gmake[7]: Leaving directory 
`/root/xen-staging-netbsd.hg/tools/firmware/rombios/32bit'
gmake[6]: *** [subdir-all-32bit] Error 2
gmake[6]: Leaving directory 
`/root/xen-staging-netbsd.hg/tools/firmware/rombios'
gmake[5]: *** [subdirs-all] Error 2
gmake[5]: Leaving directory 
`/root/xen-staging-netbsd.hg/tools/firmware/rombios'
gmake[4]: *** [subdir-all-rombios] Error 2
gmake[4]: Leaving directory `/root/xen-staging-netbsd.hg/tools/firmware'
gmake[3]: *** [subdirs-all] Error 2
gmake[1]: Leaving directory `/root/xen-staging-netbsd.hg/tools'
gmake: *** [subdirs-all] Error 2


Christoph


-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

Re: build failure

[Keir Fraser]

On 30/7/08 10:29, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> c/s 18166 causes below build failure.
> The compiler does not find ./tools/include/xen/xen.h due to
> a missing -I include path parameter.

Thanks. My build box had stale header files installed in /usr/include which
prevented build failure. :-(

 -- Keir

Re: build failure

[Christoph Egger]

On Wednesday 30 July 2008 11:49:48 Keir Fraser wrote:
> On 30/7/08 10:29, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > c/s 18166 causes below build failure.
> > The compiler does not find ./tools/include/xen/xen.h due to
> > a missing -I include path parameter.
>
> Thanks. My build box had stale header files installed in /usr/include which
> prevented build failure. :-(

I can confirm c/s 18176 fixes the build failure.

Christoph


-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

Build failure

[Steinar H. Gunderson]

Hi,

Today nfs-utils stopped building for me, probably due to a libc update or
something. The failed part was, from support/include/nfs/nfs.h:

   #include <linux/version.h>
   #if LINUX_VERSION_CODE > KERNEL_VERSION(2,5,70)
   # define __nfsd_dev_t  __kernel_old_dev_t
   #else
   # define __nfsd_dev_t  __kernel_dev_t
   #endif

The failure from gcc was:

   gcc -DHAVE_CONFIG_H -I. -I../../support/include  -I../../support/include -D_GNU_SOURCE -Wall  -pipe -g -O2 -Wall -MT client.o -MD -MP -MF .deps/client.Tpo -c -o client.o client.c
   In file included from ../../support/include/nfslib.h:22,
                    from client.c:22:
   ../../support/include/nfs/nfs.h:73:24: error: operator '>' has no left operand
   In file included from ../../support/include/nfslib.h:22,
                    from client.c:22:
   ../../support/include/nfs/nfs.h:83: error: expected specifier-qualifier-list before '__kernel_dev_t'
   ../../support/include/nfs/nfs.h:104: error: expected specifier-qualifier-list before '__kernel_dev_t'

Is userspace allowed to assume that a symbol such as LINUX_VERSION_CODE
exists at all?

/* Steinar */
-- 
Homepage: http://www.sesse.net/

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: Build failure

[Steinar H. Gunderson]

On Fri, Jun 08, 2007 at 12:24:57PM +0200, Steinar H. Gunderson wrote:
> Today nfs-utils stopped building for me, probably due to a libc update or
> something. The failed part was, from support/include/nfs/nfs.h:

Nevermind; I upgraded my build environment, and the problem went away. I
guess something was broken on my side.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs