----- Original Message ----- > 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. >
I mentioned in my first post that I already tried rebuilding everything on up. -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkc...@ksu.edu Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library _______________________________________________ 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"
