Bug 6883 - Hob cannot build receipts due to No GNU HASH in the elf binary libossp-uuid.so
Summary: Hob cannot build receipts due to No GNU HASH in the elf binary libossp-uuid.so
Status: RESOLVED INVALID
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.8
Hardware: Other arm
: Medium critical
Target Milestone: 1.8
Assignee: Egor
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-10-24 06:00 UTC by Egor
Modified: 2015-01-08 16:03 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Egor 2014-10-24 06:00:02 UTC 
I had built Yocto for altera-cyclonev
and got issues:
 - Package: ossp-uuid-1.6.2-r1
  - Task_ do_package
  - QA Issue: No GNU_HASH in the elf binary: ' ... /yocto/build-hob/tmp/work/armv7ahf-vfp-neon-poky-linux-gnueabi/ossp-uuid-1.6.2-r1/packages-split/ossp-uuid/usr/lib/libossp-uuid.so.16.0.22'
  - QA run found fatal errors. ...
  - Function failed: do_package_qa
Comment 1 Alexandru Georgescu 2014-10-27 06:50:10 UTC 
Hi,
Due to the bug summary, seems more like a build issue than Automated testing or HOB.
Can you share what version (poky commit did you use?) and all the steps that you followed so we can reproduce the issue?
Comment 2 Richard Purdie 2014-10-30 14:47:11 UTC 
This target is not a standard OE-Core target machine. Are you using some standalone toolchain with the altera BSP?

At a guess, the compiler options/flags are not being passed into the software being compiled but as Alex mentioned, we really do need more information.
Comment 3 Alexandru Georgescu 2014-11-18 06:35:28 UTC 
Assigned to reporter since we need reproducing info.
Comment 4 Paul Eggleton 2015-01-08 16:03:05 UTC 
As mentioned earlier this isn't for a standard BSP, we don't see this error during regular builds and we're missing additional info on how to reproduce, so at this time I'm marking is as invalid. Egor, if you can supply that information please do so and reopen the bug.