Adriaan de Groot wrote: > I've been running into lots of "interesting" issues with the packages; it > took > me a long time to get gettext and iconv packages *removed* from my system > after transferring them from dillon; many dillon-built packages don't install > but fail silently during the veryifying stage (popt is one of them). Now I've > built a qt package that cores out like so: > > bash-3.2# mdb /usr/sbin/pkgadd core > Loading modules: [ libc.so.1 libnvpair.so.1 libavl.so.1 libuutil.so.1 > ld.so.1 ] >> $C > 08045b9c libadm.so.1`verscmp+0x50(69676e65, 809e110) > 08045bb8 libadm.so.1`ckinst+0x41(bf7343b2, 80a3148, 809e110, 0, 69676e65) > 08046080 libadm.so.1`ckinfo+0x16e(bf7343b2, 0, 69676e65) > 080460b0 libadm.so.1`fpkginst+0xa4(809781a, 0, 69676e65) > 080460e8 dockdeps+0x175(8046100, 0, 0) > 08046704 ckdepend+0xad(0, 809c7ec, 8047dac, 80609db, 8059384, 4) > 08046714 ck_w_dryrun+0xa(8059384, 4) > 08047dac main+0x1c33(9, 8047dd8, 8047e00) > > Weirdly, pkgtool install-pkgs *does* manage to install the same package > (pkgtool install-pkgs FOSSqt). What's going on?
I don't do app. debugging so frequently with mdb, but does "::status" tell you anything more interesting? Michael -- Michael Schuster Sun Microsystems, Inc. recursion, n: see 'recursion'
