Justin,
I just tried building libcanberra on x86_64 and it built and installed just fine. original error logs: http://avalon.dragonflybsd.org/reports/x86_64/2.11/20110603.0214/libcanberra-0.26nb1/

The current version in pkgsrc is "libcanberra-0.26nb2" but I don't think the pkg revision made a difference.
It looks like the bulk-build itself screwed up.  e.g.

pkg_add: Write error for share/locale/am/LC_MESSAGES/gtk20-properties.mo: Write 
failed
pkg_add: Directory `/usr/pkg/lib/gtk-2.0/immodules' disappeared, skipping
pkg_add: Directory `/usr/pkg/lib/gtk-2.0/2.10.0/filesystems' disappeared, 
skipping

Anyway, I think canberra is okay.

John


On 6/6/2011 5:36 AM, Justin Sherrill wrote:
pkgsrc bulk build report
========================

DragonFly 2.11/x86_64
Compiler: gcc

Build start: 2011-06-03 02:14
Build end:   2011-06-06 03:10

Full report: 
http://avalon.dragonflybsd.org/reports/i386/2.11/20110603.0214/meta/report.html
Machine readable version:
http://avalon.dragonflybsd.org/reports/i386/2.11/20110603.0214/meta/report.bz2

Total number of packages:      10967
  Successfully built:           8551
  Failed to build:               591
  Depending on failed package:  1255
  Explicitly broken or masked:   507
  Depending on masked package:    63

Packages breaking the most other packages

Package                               Breaks Maintainer
-------------------------------------------------------------------------
devel/libglade                           360 [email protected]
net/avahi                                251 [email protected]
audio/libcanberra                        156 [email protected]
databases/postgresql84-client            103 [email protected]
editors/emacs                             87 [email protected]
devel/libgweather                         62 [email protected]
multimedia/xine-lib                       62 [email protected]
x11/wxGTK28                               61 [email protected]
print/teTeX3-texmf                        42 [email protected]
lang/ocaml                                37 [email protected]

B

Reply via email to