Skip to contentSkip to conversation

build failure 2 - poky-image-lsb-sdk-beagleboard with bernard-5.0

DISCUSSION Robert Berger 2 participants 4 messages Mar 22, 2011

lore
Share & tools
lore
#0 lore raw

Hi,

After resolving the first issue I did a fresh build from scratch using the bernard-5.0 tag and that's what I get:

Collected errors:
* resolve_conffiles: Existing conffile
/work/rber/poky-bernard-5.0-build-bb/tmp/work/beagleboard-poky-linux-gnueabi/poky-image-lsb-sdk-1.0-r0/rootfs/etc/sysctl.conf is different from the conffile in the new package. The new conffile will
be placed at /work/rber/poky-bernard-5.0-build-bb/tmp/work/beagleboard-poky-linux-gnueabi/poky-image-lsb-sdk-1.0-r0/rootfs/etc/sysctl.conf-opkg.

And yes, indeed those files are different: http://pastebin.com/kXpCS2uC

I'm wondering what's the configuration to build
http://autobuilder.yoctoproject.org/nightly/CURRENT/machines/beagleboard/arm/poky-image-lsb-sdk-beagleboard-20110320115716.rootfs.tar.bz2

Do you see anything strange in my local.conf? http://pastebin.com/bn4iDwBF

Please advise.

Regards,

Robert..."Java is, in many ways, C++--." - Michael Feldman

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

#1 lore raw

I think it boils down to the fact, that

meta/recipes-core/base-files/base-files/sysctl.conf meta/recipes-extended/procps/procps-3.2.8/sysctl.conf

are different and both should end up at the rootfs.

I guess I could just remove the procps package.

But how to resolve this in a more elegant way and how did the autobuilder get away with it?

Regards,

Robert

..."it doesn't matter how beautiful your theory is, it doesn't matter how smart you are -- if it doesn't agree with experiment, it's wrong." - Richard P. Feynman

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

#2 lore raw
Quoted 11 lines · Robert Berger

I think it boils down to the fact, that

meta/recipes-core/base-files/base-files/sysctl.conf meta/recipes-extended/procps/procps-3.2.8/sysctl.conf

are different and both should end up at the rootfs.

I guess I could just remove the procps package.

But how to resolve this in a more elegant way and how did the autobuilder get away with it?

Hi Robert,

Could you please report this in our bugzilla? I seem to recall running into something like this too.

http://bugzilla.pokylinux.org

Thanks,

Scott

Signature · 3 lines
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
#3 lore raw

Hi Scott,

Quoted 8 lines · Scott Garman

Hi Robert,

Could you please report this in our bugzilla? I seem to recall running into something like this too.

http://bugzilla.pokylinux.org

http://bugzilla.pokylinux.org/show_bug.cgi?id=924

Quoted 4 lines

Thanks,

Scott

Regards,

Robert...Distributed computing means that you cannot get your work done when some computer you never heard of crashes" -- L.Lamport

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1