Skip to contentSkip to conversation

db compile failure

DISCUSSION Jack Mitchell 4 participants 5 messages Jan 8, 2014 – Jan 10, 2014

lore
Share & tools
lore
#0 lore raw

On latest master I am running into the following failure:

http://ix.io/9Kh

I'm also getting a _lot_ of warnings like these:

WARNING: The recipe eglibc-locale is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

/home/jack/Work/oe-core.git/test-build/tmp-eglibc/deploy/ipk/core2/eglibc-localedata-el-gr_2.18-r0_core2.ipk
Matched in manifest-core2-eglibc-locale.deploy-ipk

/home/jack/Work/oe-core.git/test-build/tmp-eglibc/deploy/ipk/core2/eglibc-binary-localedata-wae-ch_2.18-r0_core2.ipk

Can anyone shed any light, it seems as though the something is getting it's wires crossed somewhere...

I haven't yet tried wiping the tmp folder but I could as a last resort.

Cheers,

Signature · 5 lines
  Jack Mitchell ([email protected])
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 
#1 lore raw
Quoted 3 lines · Jack Mitchell

On latest master I am running into the following failure:

http://ix.io/9Kh

This should be the following link:

http://ix.io/9Ki

Quoted 19 lines

I'm also getting a _lot_ of warnings like these:

WARNING: The recipe eglibc-locale is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

/home/jack/Work/oe-core.git/test-build/tmp-eglibc/deploy/ipk/core2/eglibc-localedata-el-gr_2.18-r0_core2.ipk
Matched in manifest-core2-eglibc-locale.deploy-ipk

/home/jack/Work/oe-core.git/test-build/tmp-eglibc/deploy/ipk/core2/eglibc-binary-localedata-wae-ch_2.18-r0_core2.ipk

Can anyone shed any light, it seems as though the something is getting it's wires crossed somewhere...

I haven't yet tried wiping the tmp folder but I could as a last resort.

Cheers,

Signature · 5 lines
  Jack Mitchell ([email protected])
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 
#2 lore raw
Quoted 9 lines · Jack Mitchell
Quoted 3 lines · Jack Mitchell

On latest master I am running into the following failure:

http://ix.io/9Kh

This should be the following link:

http://ix.io/9Ki

I'm hitting the same error building poky at master for raspberrypi, it's just worded slightly differently:

| /usr/lib/libstdc++.so: file not recognized: File format not recognized

I can't see a '-L/usr/lib' argument anywhere but something seems to be causing the linker to look at my host system's libraries.

Running 'bitbake db -c cleansstate' then 'bitbake db' again hits the same error.

Any ideas?

Signature · 4 lines
Paul Barker

Email: [email protected]
http://www.paulbarker.me.uk
#3 lore raw
In reply to Jack Mitchell

Hi Jack,

There were some sstate/manifest changes to master before Christmas which is why this happens. You should only get the warning once per package as it rebuilds and updates the manifest, or just delete tmp:
it will be rebuilt from sstate quickly.

Ross

Quoted 32 lines · Jack Mitchell

On latest master I am running into the following failure:

http://ix.io/9Kh

I'm also getting a _lot_ of warnings like these:

WARNING: The recipe eglibc-locale is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

/home/jack/Work/oe-core.git/test-build/tmp-eglibc/deploy/ipk/core2/eglibc-localedata-el-gr_2.18-r0_core2.ipk
Matched in manifest-core2-eglibc-locale.deploy-ipk

/home/jack/Work/oe-core.git/test-build/tmp-eglibc/deploy/ipk/core2/eglibc-binary-localedata-wae-ch_2.18-r0_core2.ipk

Can anyone shed any light, it seems as though the something is getting it's wires crossed somewhere...

I haven't yet tried wiping the tmp folder but I could as a last resort.

Cheers,

--
Jack Mitchell ([email protected])
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#4 lore raw
Quoted 6 lines · Ross

Hi Jack,

There were some sstate/manifest changes to master before Christmas which is why this happens. You should only get the warning once per package as it rebuilds and updates the manifest, or just delete tmp:
it will be rebuilt from sstate quickly.

The manifest file names changed and cause those spurious warnings. A clean tmp dir or wiping out the stale (or all) manifest files in tmp/sstate-control will "fix" that.

Cheers,

Richard