Re: Octave.app 64-bit?

[Christopher Jones]

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, 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 Eisenberg  murrayeisenb...@gmail.com
> 503 King Farm Blvd #101   Home (240)-246-7240
> Rockville, MD 20850-6667  Mobile (413)-427-5334
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: Octave.app 64-bit?

[Bill Cole]

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 source all of your ports 
after a major system upgrade, because even if some of the installed 
binaries will still run on the new system, the pre-upgrade MacPorts 
won't work at all.



--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

gcc/gfortran can't find system library in latest Xcode/Mojave

[David Nicholls]

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 error:

M5118 error on build:
ld: library not found for -lSystem
collect2: error: ld returned 1 exit status
make[1]: *** [../lab/map51] Error 1
make: *** [build] Error 2 with gfortran 8.3.0

Does anyone know anything about this?

DN

David C Nicholls,
Research School of Astronomy & Astrophysics
Australian National University

The state of Catalina...

[Carlo Tambuatco]

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?

Re: gcc/gfortran can't find system library in latest Xcode/Mojave

[Christopher Jones]

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 buildbot which is still 
using Xcode 10 and thus the 10.14 SDK. If you want to see what gcc is doing, 
try building with the -v option added….

So, additional solutions, if you want to avoid having to manually set the SDK 
root as you use gcc, are :-

1. revert back to Xcode 10 on mac OS 10.14, to match the buildbot.
2. rebuild gcc/libgcc from source yourself, so then the SDK will (I think…) 
match what you now have.

I would go with 1. as that will likely fix other residual issues with Xcode 11 
on mac OS 10.14..

cheers Chris

3. I guess a third option is to update you OS to 10.15….

> On 10 Oct 2019, at 11:35 pm, Christopher Jones  
> wrote:
> 
> 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
> 
> https://www.mail-archive.com/macports-dev@lists.macports.org/msg06711.html 
> 
> 
> for a previous discussion.
> 
> Chris
> 
>> On 10 Oct 2019, at 11:20 pm, David Nicholls > > wrote:
>> 
>> 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 
>> error:
>> 
>> M5118 error on build:
>> ld: library not found for -lSystem
>> collect2: error: ld returned 1 exit status
>> make[1]: *** [../lab/map51] Error 1
>> make: *** [build] Error 2 with gfortran 8.3.0
>> 
>> Does anyone know anything about this?
>> 
>> DN
>> 
>> David C Nicholls,
>> Research School of Astronomy & Astrophysics
>> Australian National University
>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: The state of Catalina...

[Ryan Schmidt]

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 Catalina trouble free?

Most of the difficulties of using Xcode 11 on Mojave relate to the fact that 
Xcode 11 does not contain the Mojave SDK. Xcode 11 contains the Catalina SDK. 
As such, the same problems would not affect you if you're using Xcode 11 on 
Catalina.

Since Catalina has just been released and many port maintainers probably 
haven't updated yet, it will probably be months before we've all had a chance 
try to discover whatever problems might exist and to try to fix them. If you'd 
like to participate in that, please do and file tickets or pull requests if you 
discover problems. If you'd rather have an experience closer to things just 
working, then wait a few months before upgrading.

Re: Octave.app 64-bit?

[Mojca Miklavec]

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 dirty and maybe not 100% reliable way:
grep -r i386 | grep -v x86_64 | grep supported_archs

This returns 75 results, but some are just bogus, like TeXShop, when
there's a newer TeXShop4 port available, or Qt 3, ...

Probably the most problematic ones are Wine, some other emulators
(dosbox, ...) ... the rest are ancient apps that probably nobody would
notice if they get removed.

Mojca

Re: gcc/gfortran can't find system library in latest Xcode/Mojave

[Christopher Jones]

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

https://www.mail-archive.com/macports-dev@lists.macports.org/msg06711.html 


for a previous discussion.

Chris

> On 10 Oct 2019, at 11:20 pm, David Nicholls  wrote:
> 
> 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 error:
> 
> M5118 error on build:
> ld: library not found for -lSystem
> collect2: error: ld returned 1 exit status
> make[1]: *** [../lab/map51] Error 1
> make: *** [build] Error 2 with gfortran 8.3.0
> 
> Does anyone know anything about this?
> 
> DN
> 
> David C Nicholls,
> Research School of Astronomy & Astrophysics
> Australian National University
> 
> 



smime.p7s
Description: S/MIME cryptographic signature

Octave.app 64-bit?

[Murray Eisenberg]

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
503 King Farm Blvd #101 Home (240)-246-7240
Rockville, MD 20850-6667Mobile (413)-427-5334

compiler warning

[Andrew Hartung via macports-users]

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; defaulting to 
first fallback option
Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option
Adding port lang/llvm-9.0
Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option
Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option
Adding subport clang-9.0
Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option
Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option
Adding subport lldb-9.0


and here:

Warning: All compilers are either blacklisted or unavailable; defaulting to 
first fallback option
--->  Computing dependencies for llvm-9.0.