libgcc9 and other ports that will never build on my system

chilli.namesake at gmail.com chilli.namesake at gmail.com
Mon Sep 12 19:14:57 UTC 2022


Excellent. Thank you. I suspected there was, just unaware of syntax. Whenever I consult the manual, I seem to only see that which I already knew, and what I wanted to know, hidden in plain sight, often eludes me. Thanks again.

> On Sep 12, 2022, at 15:12, Bill Cole <macportsusers-20171215 at billmail.scconsult.com> wrote:
> 
> On 2022-09-12 at 15:02:47 UTC-0400 (Mon, 12 Sep 2022 15:02:47 -0400)
> <chilli.namesake at gmail.com>
> is rumored to have said:
> 
>> 
>> Yes, you got it. How do I command MacPorts to upgrade all outdated ports "and not" this whatever troublesome port?  Is there a way? If you just told me, you'll have to be less subtle.
> 
> 3rd time's a charm maybe? Here's the command on a single line all by itself. enter all of it, hit return, and nothing more:
> 
> sudo port upgrade outdated and not libgcc9
> 
> Really. I was not kidding. This syntax is documented in the port(1) man page.
> 
> 
> P.S. no need to CC me on anything sent to this list.
> 
> 
> -- 
> Bill Cole
> bill at scconsult.com or billcole at apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire


More information about the macports-users mailing list