Unless you are installing something universal, or i386, it will be 64 bit (i.e.
x86_64 arch).
( Also, by construction, if the port finds and runs on macOS 10.15 it will have
to be 64 bit… )
> On 10 Oct 2019, at 10:12 pm, Murray Eisenberg
> wrote:
>
> Is the current version of octave.app,
On 10 Oct 2019, at 17:25, Christopher Jones wrote:
Unless you are installing something universal, or i386, it will be 64
bit (i.e. x86_64 arch).
Also, you can check the architecture of whatever is actually installed
with:
port -v installed
Of course you should reinstall or rebuild from
Something Apple did in either the latest update to Mojave or the latest Xcode
breaks gfortran's (8.3.0) ability to find the system library. I updated to the
latest macports recently, too. gfortran 8.3.0 that compiled code easily under
previous versions of Mojave/Xcode/macports now throws an
After some difficulties caused by upgrading to XCode 11, I'm sure a lot of
people are weary of upgrading to Catalina just yet, so could someone give a
timeframe for when it should be >95% safe for most macports users to
upgrade to Catalina trouble free?
Hi,
Just to add one detail to that below. Part of the problem is Xcode 11 even on
maOS10.14 only supplies the 10.15 SDK. gcc when built gets the SDK baked into
the default search paths it will use, and because you are (I presume) using
gcc binary install it is using the one built on the
On Oct 10, 2019, at 18:05, Carlo Tambuatco wrote:
> After some difficulties caused by upgrading to XCode 11, I'm sure a lot of
> people are weary of upgrading to Catalina just yet, so could someone give a
> timeframe for when it should be >95% safe for most macports users to upgrade
> to
On Thu, 10 Oct 2019 at 23:12, Murray Eisenberg wrote:
>
> Is the current version of octave.app, installed with octave+app, 64-bit and
> hence compatible with Catalina?
>
> if not, what are the prospects?
>
> In general, is there any way to tell which macports ports are, or are not,
> 64-bit?
A
Hi,
Apple has been depreciating shipping the SDK under /usr/include for some time
now, and come Xcode11/macOS10.15 they are gone (with Xcode10 they where gone by
default but you could add them back).
You need to specify the SDK root you need to use. See
Is the current version of octave.app, installed with octave+app, 64-bit and
hence compatible with Catalina?
if not, what are the prospects?
In general, is there any way to tell which macports ports are, or are not,
64-bit?
---
Murray Eisenbergmurrayeisenb...@gmail.com
What does this mean?
Warning: All compilers are either blacklisted or unavailable; defaulting to
first fallback option
10.14.6 with xcode 10.
Showed up after the latest port update I ran after here:
Adding subport libomp-devel
Warning: All compilers are either blacklisted or unavailable;
10 matches
Mail list logo
