On Fri, 28 Sep 2012 18:22:29 -0400 (EDT) Lawrence K. Chen, P.Eng. articulated:
> Well, I had to a bunch of reboots yesterday....so I tried > 304.51....no joy. I then tried 295.75, and that works. In the past, I have had problems that occurred when I updated a port and failed to rebuild the ports that were dependent upon that port. It is rare, but it does happen. In such instances, I find that "portmanager" used with the "-p" flag comes in extremely handy. I might suggest that you first update your ports tree and then run something like: "portmanager -u -l -y -p" It will do all of that automatically for you and provide you with a log file should something not work as expected. Just a thought. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
