On 11/03/11 22:44, Bryan wrote:
I invoked dpb with the following switches:
./dpb -b /usr/ports/logs/amd64/build.log -c -f 0 -j 4 -U
I did a build with dpb, and came up with the following failures:
math/kst
multimedia/k3b
graphics/ImageMagick,no_x11
multimedia/xine-lib
net/telepathy/telepathy-glib
x11/gnome/devel-docs
graphics/digikam
graphics/kimdaba
textproc/xerces-c
math/R
graphics/clutter/core
x11/fluxbox
audio/pulseaudio
audio/libgpod
Is there a port output that will show me the error messages, or will I
have to go back and build them individually.
What if they do build... was it scheduling issues with dpb, or something else?
I just finished a bulk build yesterday with only two avahi flavors
complaining. Bulk building usually works well, but if you miss
something you can get cascading failures, resulting in lots of
failed packages.
You might want to make sure that
- you have up to date kernel & userland compiled. I always
compile the world just before a bulk build to make sure any
late changes are covered. I also verify that I have the latest
cvs updates,
- the ports tree is clean, so pobj, bulk, plist and packages
are empty,
- the src for new packages has been fetched,
- bsd.port.mk has trust packages and bulk set to yes,
- /var/db/pkg is empty
Look in /usr/ports/logs/i386/paths/<catagory> for transcripts
of builds.
One of things I messed up several times was starting a build
when I hadn't gotten a complete set of updates. You really
want to always watch the cvs changes list, and then make sure
that your mirror has them all.
--STeve Andre'
