Reading some of the handbook, it seems that Build-Pkg does not check dependencies, but that Build-Target does (??) Perhaps this is the problem.
mine fails looking for dialog.h There are lots of dialog.h files sprinkled around in the t2-trunk directory, and there is a [DEP] dialog in the mine.cache file. ./scripts/Build-Pkg mine works fine: == 13:28:04 =[9]=> Building archiver/mine [0.23 8.0-trunk]. -> Reading package config: package/archiver/mine/mine.conf -> Preparing build in src.mine.default.20091022.132759.329.susie -> Building. Writing output to $root/var/adm/logs/9-mine.out -> $root/var/adm/logs/9-mine.out -> 9-mine.log == 10/22/09 13:30:02 =[9]=> Finished building package mine. r...@susie:/usr/local/src/t2-trunk# The local var/adm/logs directory shows an err file which happened about ten minutes ago during the Build-Target run and a much older 0-mine.log file Note that the 9-mine.log file from the above Build-Pkg run appears in the system root directory /var/adm/logs These things are a puzzle to me. Why are these files scattered around and more importantly, why is mine failing to build under Build-Target? =========== The /var/adm/log r...@susie:/usr/local/src/t2-trunk/build/default-8.0-trunk-generic-x86-i486-linux/var/adm/logs# ls -l | grep mine -rw-r--r-- 1 root root 20409 Oct 19 14:31 0-mine.log -rw-r--r-- 1 root root 24579 Oct 22 13:11 1-mine.err r...@susie:/usr/local/src/t2-trunk/build/default-8.0-trunk-generic-x86-i486-linux/var/adm/logs# ls -l /var/adm/logs | grep mine -rw-r--r-- 1 root root 19427 Oct 22 13:30 9-mine.log ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
