Libomp notes

[John Wiggins via macports-users]

I am running macOS Monterey 12.6.1 and updated Xcode and CLT to 14.1.
When I “upgrade outdate” I get note concerning libomp:

…
> --->  Some of the ports you installed have notes:
>   libomp has the following notes:
> To use this OpenMP library:
>  * For clang-3.8+, or clang-3.7 with +openmp variant:
> add "-fopenmp" during compilation / linking.
>  * For clang-3.7 without +openmp variant, use:
> "-I/opt/local/include/libomp -L/opt/local/lib/libomp -fopenmp"
>   libpsl has the following notes:
> libpsl API documentation is provided by the port 'libpsl-docs’.


There any action required of me?  It seems to not apply as:

> $ clang --version
> Apple clang version 14.0.0 (clang-1400.0.29.202)
> Target: arm64-apple-darwin21.6.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> jwMini: (macports_dir) /Users/jw/macports_dir
> $

Thanks,
jw


This 
…snip…
> --->  Fetching archive for libomp
> --->  Attempting to fetch libomp-15.0.3_0.darwin_21.arm64.tbz2 from 
> https://packages.macports.org/libomp
> --->  Attempting to fetch libomp-15.0.3_0.darwin_21.arm64.tbz2.rmd160 from 
> https://packages.macports.org/libomp
> --->  Installing libomp @15.0.3_0
> --->  Cleaning libomp
> --->  Deactivating libomp @14.0.6_0
> --->  Cleaning libomp
> --->  Activating libomp @15.0.3_0
> --->  Cleaning libomp
> --->  Uninstalling libomp @14.0.6_0
> --->  Cleaning libomp

…snip…

Re: Clang config issues after update to Xcode 13.1 on Big Sur

[John Wiggins via macports-users]

Thanks for the help.  I was able to get things working with latest Big Sur  
11.6.1 && Xcode 13.1 && CLT for Xcode 13.1 by: 
a) removing everything  from /opt/local
b) install package “maxOS Big Sur v11” from the “Installing Macports” 
page,  https://www.macports.org/install.php 

c) reinstall my packages, and instead of “port install emacs-devel 
+x11” doing the simple emacs with
port install emacs +x11

I did not even try the “emacs-devel” because I was running the “level” version 
only because I was seeing issues with trying to install the simple “emacs” with 
my new M1 Mac mini.
Before blowing away /opt/local I was able to install emacs +x11 but the 
emacs-devel +x11 was still showing the config issues.

Thanks,
jw


> On Nov 5, 2021, at 10:39 AM, Ryan Schmidt  wrote:
> 
> On Oct 28, 2021, at 08:05, John Wiggins wrote:
>> 
>> It seemed to work yesterday under Xcode 13.0 and its CLT.
>> Now emacs-dev seems to fail after update to Xcode 13.1 and CLT for Xcode 
>> 13.1.
>> 
>> I am a bit of a novice, doe the following in
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_emacs/emacs-devel/work/emacs-20211020/config.log
>> Mean that I merely need to wait until the macports tools are updated to 
>> Xcode 13.1?
>> 
>> Thanks in advance.
>> John
>> 
>> …snip...
> 
> It's difficult to make a diagnosis just based on what you've shown. The 
> purpose of a configure script is to determine the capabilities of your 
> operating system. It can be normal for errors to appear in the config.log. I 
> do not know if these specific errors are normal for this specific port or for 
> your OS version, whatever that is. On my macOS 10.13 system none of the files 
> mentioned in those errors exist, so probably those errors are normal, and the 
> type name "barfbarf" certainly sounds like something used for testing. 
> Usually if a port fails to build you should file a bug report and attach the 
> main.log (and if it is a configuration failure also the config.log).
> 

Clang config issues after update to Xcode 13.1 on Big Sur

[John Wiggins via macports-users]

It seemed to work yesterday under Xcode 13.0 and its CLT.
Now emacs-dev seems to fail after update to Xcode 13.1 and CLT for Xcode 13.1.

I am a bit of a novice, doe the following in
 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_emacs/emacs-devel/work/emacs-20211020/config.log
Mean that I merely need to wait until the macports tools are updated to Xcode 
13.1?

Thanks in advance.
John


Errors seen in

configure:6360: checking whether the compiler is clang
configure:6382: /usr/bin/clang -c -pipe -Os 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 
-I/opt/local/include 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
conftest.c:12:12: error: unknown type name 'barfbarf'
   barfbarf
   ^
1 error generated.
configure:6382: $? = 1
configure: failed program was:
| /* confdefs.h */

And
configure:6629: result: no
configure:6629: checking for sys/systeminfo.h
configure:6629: /usr/bin/clang -c -pipe -Os 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 
-I/opt/local/include -isysroot/Library/Dev
eloper/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
conftest.c:48:10: fatal error: 'sys/systeminfo.h' file not found
#include 
 ^~
1 error generated.
configure:6629: $? = 1

And

configure:6629: /usr/bin/clang -c -pipe -Os 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 
-I/opt/local/include 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
conftest.c:48:10: fatal error: 'coff.h' file not found
#include 
 ^~~~
1 error generated.
configure:6629: $? = 1

And

configure:6629: /usr/bin/clang -c -pipe -Os 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 
-I/opt/local/include 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
conftest.c:48:10: fatal error: 'pty.h' file not found
#include 
 ^~~
1 error generated.
configure:6629: $? = 1
configure: failed program was:
| /* confdefs.h */

And

configure:6629: /usr/bin/clang -c -pipe -Os 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX11.sdk -arch arm64 
-I/opt/local/include -isysroot/Library/Dev
eloper/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
conftest.c:59:10: fatal error: 'vfork.h' file not found
#include 
 ^
1 error generated.
configure:6629: $? = 1


And

loper/CommandLineTools/SDKs/MacOSX11.sdk conftest.c >&5
conftest.c:61:10: fatal error: 'stdio_ext.h' file not found
#include 
 ^
1 error generated.

And perhaps a couple others.

Re: Ports emacs and emacs-devel Question

[John Wiggins via macports-users]

Thanks, the +x11 works very nicely for me.
(Just started using macports and did not know about the variants options.)

> Date: Sun, 28 Feb 2021 23:20:16 -0800
> From: Dan Ports 
> To: macports-users@lists.macports.org
> Subject: Re: Ports emacs and emacs-devel Question
> Message-ID: 
> Content-Type: text/plain; charset=us-ascii
> 
> Belatedly answering...
> 
> On Thu, Feb 18, 2021 at 12:03:28PM -0500, John Wiggins via macports-users 
> wrote:
>> From a standard XQuartz xterm neither emacs command opens a new window.
> 
> By default, the emacs and emacs-devel ports install the text-only
> console variant. If you'd like a X11 version, you can install the port
> with the +gtk (more modern) or +x11 (older, lighterweight) variant.
> 
> Dan
> 
> -- 
> Dan R. K. Ports  https://drkp.net/
> 
> 

Ports emacs and emacs-devel Question

[John Wiggins via macports-users]

Both ports are working beautifully for me from the most recent 11_arm64 builds,
and I am currently using emacs-devel.
From a standard XQuartz xterm neither emacs command opens a new window.

This is easily worked around with an alias such as
alias xemacs="xterm -e emacs $*”
a shell script containing
xterm -e emacs $@ &

However, I wonder if there is some Security configuration I need to tweak on my
Apple M1 MacOS 12.2.1 with XQuartz 2.8.0_beta3?

Thanks,
jw