Bug 1061 - Recipe texinfo does not build
Summary: Recipe texinfo does not build
Status: RESOLVED WORKSFORME
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard: possible dependency failure, built OK
Depends on:
Blocks:
 
Reported: 2011-05-12 14:10 UTC by Scott Garman
Modified: 2011-08-23 09:49 UTC (History)
2 users (show)

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

Attachments
do_compile log (41.49 KB, application/octet-stream)
2011-05-12 16:21 UTC, Scott Garman 		no flags Details
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 Scott Garman 2011-05-12 14:10:36 UTC 
As part of the documentation audit, the texinfo recipe failed to build for qemux86 on my Fedora 14 host. I will attach the build error log to this bug.
Comment 1 Scott Garman 2011-05-12 16:21:04 UTC 
Created attachment 153 [details]
do_compile log
Comment 2 Saul Wold 2011-05-18 23:12:23 UTC 
Built correctly, which may indicate a dependency issue, will investigate further.
Comment 3 Saul Wold 2011-05-19 07:58:44 UTC 
Tried a second build from scratch on an Ubuntu 11.04 machine and it built OK.

Scott, can you try to build again from scratch "bitbake texinfo", thanks.
Comment 4 Scott Garman 2011-05-19 10:29:52 UTC 
Hi Saul,

A build of texinfo from scratch on my Fedora 14 system using today's master fails during do_compile. The compilation is the same as from the do_compile log I previously attached to the bug - undefined references to tgoto, tputs, etc.

Sounds like this could be due to a missing host dependency on my Fedora system.

I'd be happy to take this bug if resolution of it can wait until next week.
Comment 5 Saul Wold 2011-08-23 09:49:30 UTC 
This seems to build correctly, may have been a host dependency issue.

If this problem re-appears, we can always reopen this bug.