Bug 43 - error generic in in distcc without patch
Summary: error generic in in distcc without patch
Status: RESOLVED INVALID
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: All Multiple
: medium normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2008-01-16 09:21 UTC by stefano
Modified: 2010-12-21 06:07 UTC (History)
2 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 stefano 2008-01-16 09:21:41 UTC
| mkdir /home/stefano/poky/build/tmp/work/armv5te-poky-linux-gnueabi/distcc-2.18.3-r3/image/usr/share/doc/distcc
| for p in AUTHORS COPYING NEWS README INSTALL TODO doc/protocol-1.txt doc/status-1.txt doc/protocol-2.txt doc/reporting-bugs.txt survey.txt; do                              \
|       /usr/bin/install -c -m 644 $p /home/stefano/poky/build/tmp/work/armv5te-poky-linux-gnueabi/distcc-2.18.3-r3/image/usr/share/doc/distcc || exit 1;     \
|       done
| make: *** No rule to make target `man/distccmon-gnome.1', needed by `install-man'.  Stop.
| FATAL: oe_runmake failed
NOTE: Task failed: /home/stefano/poky/build/tmp/work/armv5te-poky-linux-gnueabi/distcc-2.18.3-r3/temp/log.do_install.19005
NOTE: package distcc-2.18.3-r3: task do_install: failed
ERROR: TaskFailed event exception, aborting
NOTE: package distcc-2.18.3: failed
ERROR: Build of /home/stefano/poky/meta/packages/distcc/distcc_2.18.3.bb do_install failed
ERROR: Task 2070 (/home/stefano/poky/meta/packages/distcc/distcc_2.18.3.bb, do_install) failed
NOTE: Tasks Summary: Attempted 2047 tasks of which 2047 didn't need to be rerun and 1 failed.
ERROR: '/home/stefano/poky/meta/packages/distcc/distcc_2.18.3.bb' failed
Comment 1 Richard Purdie 2008-01-16 11:53:05 UTC
You can't remove a patch and expect things to still work! The underlying issue with the patch from #705 should now be fixed.