Bug 33 - Build poky-image-sato failed
Summary: Build poky-image-sato failed
Status: RESOLVED WORKSFORME
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 x86
: high normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2007-08-24 17:42 UTC by Alan Lu
Modified: 2010-12-21 06:07 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Lu 2007-08-24 17:42:05 UTC
Hi, 
I got the following error messages when I build poky-image-sato image with 
akita machine config.

NOTE: package fixesproto-4.0: started
NOTE: package fixesproto-1_4.0-r1: task do_install: started 
ERROR: function do_install failed 
ERROR: log data follows (/home/alan/o-hand/poky/build/tmp/work/armv5te-poky-
linux-gnueabi/fixesproto-1_4.0-r1/temp/log.do_install.31916)
| NOTE: make DESTDIR=/home/alan/o-hand/poky/build/tmp/work/armv5te-poky-linux-
gnueabi/fixesproto-1_4.0-r1/image install 
| make: *** No rule to make target `install'.  Stop.
| FATAL: oe_runmake failed
NOTE: Task failed: /home/alan/o-hand/poky/build/tmp/work/armv5te-poky-linux-
gnueabi/fixesproto-1_4.0-r1/temp/log.do_install.31916 
NOTE: package fixesproto-1_4.0-r1: task do_install: failed
ERROR: TaskFailed event exception, aborting
NOTE: package fixesproto-4.0: failed

Any idea ? Appreciated!

Alan
Comment 1 Richard Purdie 2007-08-28 19:17:36 UTC
It sounds like the source didn't unpack for some reason. You could try "bitbake
fixesproto -c rebuild". If that fixed things it was some kind of intermittent
problem. If it doesn't fix it, send a listing of all the files under
/home/alan/o-hand/poky/build/tmp/work/armv5te-poky-
linux-gnueabi/fixesproto-1_4.0-r1/. How far into the build was this and did you
stop and try and restart it?
Comment 2 Richard Purdie 2007-10-30 10:54:20 UTC
No feedback and I've not has any other reports of the problem so it must have been some local issue.