Bug 204 - gdb has apparently host-contamination
Summary: gdb has apparently host-contamination
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 0.9 M3
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on: 117
Blocks:
  Show dependency tree
 
Reported: 2010-08-11 07:48 UTC by Mark Hatle
Modified: 2010-12-21 06:09 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

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 Mark Hatle 2010-08-11 07:48:34 UTC 
GDB has a dependency on libexpat.so.0 on my RHEL 5 build machine.  There is no libexpat.so.0 in an image-sato build.
Comment 1 Nitin Kamble 2010-08-25 17:22:24 UTC 
gdb recipe is configured with this option --without-expat
so it should not be expecting expat library. Also we have expat recipe in the poky tree. If it is just a matter of adding dependency, then it's easy. But I don't have RHEL 5 build machine to test.

Mark, can you clarify what do you mean by "GDB has a dependency on libexpat.so.0.
Comment 2 Mark Hatle 2010-08-25 21:30:09 UTC 
The GDB on the target image had a dependency to libexpat.so.0.

I did not see this failure in the latest sato builds, so it's like another commit has corrected this problem.