On Sep 12, 2022, at 14:02, chilli.namesake wrote:
> On Sep 12, 2022, at 11:49, Eric Gallager wrote:
>
>> On Mon, Sep 12, 2022 at 9:29 AM Bill Cole wrote:
>>
>>> Why are you trying to to build it for i386, e.g. 32-bit? Is there some
>>> dependent that can't be built for x86_64?
>>
>> There are
> On Sep 12, 2022, at 3:18 PM, chilli.names...@gmail.com wrote:
>
> Mostly got it. But what if there are two bad ports?
>
That’s the
port upgrade outdated and not \( badport1 or badport2 \)
example. One could have three or more in there too, as far as that goes. The
backslashes are not
>> port upgrade outdated and not \( badport1 or badport2 \)
that works perfect, thank you!
feel free to mock me, I deserve it.
> On Sep 12, 2022, at 15:19, chilli.names...@gmail.com wrote:
>
> No, I got it. Ignore.
>
> And thank you all.
>
>> On Sep 12, 2022, at 15:16, Richard L. Hamilton
No, I got it. Ignore.
And thank you all.
> On Sep 12, 2022, at 15:16, Richard L. Hamilton wrote:
>
> You can say
>
> port upgrade outdated and not badport1
>
> or even
>
> port upgrade outdated and not \( badport1 or badport2 \)
>
>
> although if badport1 (badport2, etc) is depended on
Mostly got it. But what if there are two bad ports?
> On Sep 12, 2022, at 15:16, Richard L. Hamilton wrote:
>
> You can say
>
> port upgrade outdated and not badport1
>
> or even
>
> port upgrade outdated and not \( badport1 or badport2 \)
>
>
> although if badport1 (badport2, etc) is
You can say
port upgrade outdated and not badport1
or even
port upgrade outdated and not \( badport1 or badport2 \)
although if badport1 (badport2, etc) is depended on by something else being
upgraded, it will probably get upgraded too (and fail, I suppose).
You can upgrade a port without
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
> wrote:
>
> On
On 2022-09-12 at 15:02:47 UTC-0400 (Mon, 12 Sep 2022 15:02:47 -0400)
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
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.
> On Sep 12, 2022, at 14:00, Bill Cole
> wrote:
> On 2022-09-12 at 12:04:41 UTC-0400 (Mon, 12 Sep 2022
(note: my reply all does not include the list, annoyingly)
That is pretty unsettling.
uname -p gives i386
uname -m gives x86_86
I vaguely recall that in the past MacPorts has ignored the arch specification.
If macports.conf arch setting is ignored, is there a way I can force x86_64?
Thanks.
Thanks for catching that.
From my macports.conf file:
# CPU architecture to target. Supported values are "ppc", "ppc64",
# "i386", "x86_64", and "arm64". Defaults to:
# - Mac OS X 10.5 and earlier: "ppc" on PowerPC, otherwise "i386".
# - Mac OS X 10.6 - 10.15: "x86_64" on 64-bit Intel, otherwise
On Mon, Sep 12, 2022 at 9:29 AM Bill Cole
wrote:
>
> On 2022-09-12 at 01:29:31 UTC-0400 (Mon, 12 Sep 2022 01:29:31 -0400)
>
> is rumored to have said:
>
> > With Mojave on Macmini6,1 & XCode 11.3.1
> > I get this:
> >
> > port -vsN upgrade libgcc9
> > ---> Computing dependencies for libgcc9.
On 2022-09-12 at 01:29:31 UTC-0400 (Mon, 12 Sep 2022 01:29:31 -0400)
is rumored to have said:
With Mojave on Macmini6,1 & XCode 11.3.1
I get this:
port -vsN upgrade libgcc9
---> Computing dependencies for libgcc9.
---> Fetching distfiles for libgcc9
Error: gcc9 9.5.0 is not supported on
With Mojave on Macmini6,1 & XCode 11.3.1
I get this:
port -vsN upgrade libgcc9
---> Computing dependencies for libgcc9.
---> Fetching distfiles for libgcc9
Error: gcc9 9.5.0 is not supported on Darwin 18 i386
Error: Failed to fetch libgcc9: incompatible macOS version
Error: See
14 matches
Mail list logo
