gcc49 fails to build

[Ryan Schmidt]

On Jun 10, 2018, at 23:39, Dave Horsfall wrote:

> On Sun, 10 Jun 2018, Ken Cunningham wrote:
> 
>> Dave, I would be tempted to uninstall gcc49 and just see what happens. I don't think you need it.
> 
> OK, with trepidation:
> 
>    ozzie:~ dave# port uninstall gcc49
>    --->  Deactivating gcc49 @4.9.4_2
>    --->  Cleaning gcc49
>    --->  Uninstalling gcc49 @4.9.4_2
>    --->  Cleaning gcc49
> 
> Well, nothing seemed to have depended upon it, but I guess I'll find out when I run my regular weekly check :-)
> 
> Q: Shouldn't old stuff be cleaned out for me?  Or do I have to keep track of them myself?
> 
> Sorry for seeming to be so obstreperous, but under FreeBSD this sort of thing "just works"...  And no, I am not denigrating the Mac etc; it is just one of the many horses in my stable.

MacPorts doesn't uninstall ports for you unless you ask it to.

The "leaves" pseudoport can be useful to find ports that you may no longer need:

port installed leaves