>> >>> libgailutil is 26.0 now,, it must have picked up an old installed lib. >> >>> As dpb(1) says, "some packages only build on a clean machine right now" >> >>> >> >> >> >> I picked up the libc minor bump. This was on a clean machine with >> >> 1) rm -rf /usr/local/* >> >> 2) rm -rf /usr/ports/packages/* >> >> 3) rm -rf /usr/ports/plist/* >> > >> > is WRKOBJDIR clean? >> >> Sorry to get back so late... >> Everything is clean. I did a rm -rf /usr/ports/pobj/* >> >> When I change this in the Makefile AND have to do a make plist (lots >> of changes there), the gtk+2 package is created. Please take a look in >> gtk+2 port, and see if the plist on your machine is okay with whats in >> cvs. > > It looks like you are using a broken or wrong copy of libtool somehow. > Those file names are meant to be under control of ports and that is > obviously being ignored on your machine. > > Build logs might tell more but I'm pretty sure it's a local problem > of some sort.
Might be true, as I had to fsck a lot to recover from the hangs. Would a rebuilt userland (or the pre-built binaries from base49.tgz) help? Thanks
