Re: C compiler not found after upgrade to macOS 13.0.1

[Chris Jones]

Looks like your ports are not up to date, please run

> sudo port -d sync
> sudo port upgrade outdated

Then report back.

> On 10 Nov 2022, at 7:12 pm, Artemio González López  wrote:
> 
> 
> 
>>> On 10 Nov 2022, at 20:05, Chris Jones  wrote:
>>> 
>>> Does
>>> 
>>>  /opt/local/lib/libicui18n.71.dylib
>>> 
>>> Actually exist in your system ?
>> 
>> No, but
>> 
>> /opt/local/lib/libicui18n.72.dylib
>> 
>> does. Also,
>> 
>> rtemio@mbp-13 ~ % otool -L /opt/local/lib/libxml2.2.dylib
>>   
>> /opt/local/lib/libxml2.2.dylib:
>>  /opt/local/lib/libxml2.2.dylib (compatibility version 13.0.0, current 
>> version 13.3.0)
>>  /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current 
>> version 1.2.13)
>>  /opt/local/lib/liblzma.5.dylib (compatibility version 8.0.0, current 
>> version 8.7.0)
>>  /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
>> version 1319.0.0)
>>  /opt/local/lib/libiconv.2.dylib (compatibility version 9.0.0, current 
>> version 9.1.0)
>>  /opt/local/lib/libicui18n.71.dylib (compatibility version 71.0.0, 
>> current version 71.1.0)
>>  /opt/local/lib/libicuuc.71.dylib (compatibility version 71.0.0, current 
>> version 71.1.0)
>>  /opt/local/lib/libicudata.71.dylib (compatibility version 71.0.0, 
>> current version 71.1.0)
>> 
>> However, I am embarrassed to say that the problem with the compiler seems to 
>> have been cause by not updating the path to Xcode after replacing the RC2 by 
>> the final version. Indeed, after executing
>> 
>> sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer 
>> 
>> And doing a port update clang seems to be working again! (The Emacs.app 
>> problem still persists, though).
>> 
>> Sorry for the snafu,
>> 
>> Artemio
>> 
 On 10 Nov 2022, at 7:02 pm, Artemio González López via macports-users 
  wrote:
 
>>> 
 On 10 Nov 2022, at 18:52, Artemio González López  wrote:
 
 After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find 
 any C compiler:
 
 checking for gcc... /opt/local/bin/clang-mp-14
 checking whether the C compiler works... no
 configure: error: in 
 `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
 configure: error: C compiler cannot create executables
 
 However, the CLT seems to be installed:
 
 artemio@mbp-13 ~ % pkgutil 
 --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
  2>/dev/null | sed -n 's/^version: //p'
 14.1.0.0.1.1666437224
 
 Does anybody know what’s going on here? (any help would be much 
 appreciated!)
 
 Thanks in advance,
 
 Artemio
 
 
 Artemio Gonzalez Lopez
 artem...@mac.com
 
>>> 
>>> Actually, this problem is also related to the icu library referenced from 
>>> libxml. Indeed, looking in Console.app I found a bunch of clang crashes 
>>> (basically every time it was called in the configure process) like the 
>>> following:
>>> 
>>> Crashed Thread:0
>>> 
>>> Exception Type:EXC_CRASH (SIGABRT)
>>> Exception Codes:   0x, 0x
>>> 
>>> Termination Reason:Namespace DYLD, Code 1 Library missing
>>> Library not loaded: /opt/local/lib/libicui18n.71.dylib
>>> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
>>> /opt/local/lib/libxml2.2.dylib
>>> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>>> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' 
>>> (no such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>>> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
>>> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
>>> 
>>> Cheers,
>>> 
>>> Artemio
>>> 
>>> 
>>> Artemio Gonzalez Lopez
>>> artem...@mac.com
>>> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com
> 

Re: C compiler not found after upgrade to macOS 13.0.1

[Artemio González López via macports-users]

> On 10 Nov 2022, at 20:05, Chris Jones  wrote:
> 
> Does
> 
>  /opt/local/lib/libicui18n.71.dylib
> 
> Actually exist in your system ?

No, but

/opt/local/lib/libicui18n.72.dylib

does. Also,

rtemio@mbp-13 ~ % otool -L /opt/local/lib/libxml2.2.dylib   
   
/opt/local/lib/libxml2.2.dylib:
/opt/local/lib/libxml2.2.dylib (compatibility version 13.0.0, current 
version 13.3.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current 
version 1.2.13)
/opt/local/lib/liblzma.5.dylib (compatibility version 8.0.0, current 
version 8.7.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1319.0.0)
/opt/local/lib/libiconv.2.dylib (compatibility version 9.0.0, current 
version 9.1.0)
/opt/local/lib/libicui18n.71.dylib (compatibility version 71.0.0, 
current version 71.1.0)
/opt/local/lib/libicuuc.71.dylib (compatibility version 71.0.0, current 
version 71.1.0)
/opt/local/lib/libicudata.71.dylib (compatibility version 71.0.0, 
current version 71.1.0)

However, I am embarrassed to say that the problem with the compiler seems to 
have been cause by not updating the path to Xcode after replacing the RC2 by 
the final version. Indeed, after executing

sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer 

And doing a port update clang seems to be working again! (The Emacs.app problem 
still persists, though).

Sorry for the snafu,

Artemio
> 
>> On 10 Nov 2022, at 7:02 pm, Artemio González López via macports-users 
>>  wrote:
>> 
>> 
>>> On 10 Nov 2022, at 18:52, Artemio González López  wrote:
>>> 
>>> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find 
>>> any C compiler:
>>> 
>>> checking for gcc... /opt/local/bin/clang-mp-14
>>> checking whether the C compiler works... no
>>> configure: error: in 
>>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
>>> configure: error: C compiler cannot create executables
>>> 
>>> However, the CLT seems to be installed:
>>> 
>>> artemio@mbp-13 ~ % pkgutil 
>>> --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
>>>  2>/dev/null | sed -n 's/^version: //p'
>>> 14.1.0.0.1.1666437224
>>> 
>>> Does anybody know what’s going on here? (any help would be much 
>>> appreciated!)
>>> 
>>> Thanks in advance,
>>> 
>>> Artemio
>>> 
>>> 
>>> Artemio Gonzalez Lopez
>>> artem...@mac.com
>>> 
>> 
>> Actually, this problem is also related to the icu library referenced from 
>> libxml. Indeed, looking in Console.app I found a bunch of clang crashes 
>> (basically every time it was called in the configure process) like the 
>> following:
>> 
>> Crashed Thread:0
>> 
>> Exception Type:EXC_CRASH (SIGABRT)
>> Exception Codes:   0x, 0x
>> 
>> Termination Reason:Namespace DYLD, Code 1 Library missing
>> Library not loaded: /opt/local/lib/libicui18n.71.dylib
>> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
>> /opt/local/lib/libxml2.2.dylib
>> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
>> such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
>> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
>> 
>> Cheers,
>> 
>> Artemio
>> 
>> 
>> Artemio Gonzalez Lopez
>> artem...@mac.com
>> 

Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Sriranga Veeraraghavan]

On Monterey libxml2 appears to declare a dependency on icu (I'm running 
MacPorts 2.8.0, so I'm guessing it probably would be the same on 13.0.1) :

$ port info libxml2
libxml2 @2.10.3 (textproc)
Variants: debug, readline, universal

Description:  Libxml is the XML C library developed for the
  GNOMEproject. XML itself is a metalanguage to design
  markup languages. Though the library is written in C, a
  variety of language bindings make it available in other
  environments.
Homepage: https://gitlab.gnome.org/GNOME/libxml2/-/wikis/home

Extract Dependencies: xz
Build Dependencies:   pkgconfig
Library Dependencies: libiconv, icu, xz, zlib
Platforms:darwin
License:  MIT
Maintainers:  Email: ryandes...@macports.org, GitHub: ryandesign
  Policy: openmaintainer



> On Nov 10, 2022, at 11:01, Chris Jones  wrote:
> 
> Does libxml2 declare a dependency against icu ?
> 
>> On 10 Nov 2022, at 6:57 pm, Sriranga Veeraraghavan  
>> wrote:
>> 
>> Hi,
>> 
>> On my Monterey (12.6.1) system, 'port provides' says that the missing 
>> library is provided by the 'icu' port:
>> 
>> $ port provides /opt/local/lib/libicui18n.71.dylib
>> /opt/local/lib/libicui18n.71.dylib is provided by: icu
>> 
>> Perhaps the 'icu' port is not properly installed on your system (you can 
>> check with 'port installed icu').  Or you may need to rebuild it for MacOS 
>> 13.0.1.
>> 
>> Best,
>> 
>> -ranga
>> 
>> 
>>> On Nov 10, 2022, at 10:48, Chris Jones >> > wrote:
>>> 
>>> 
>>> 
 On 10 Nov 2022, at 6:43 pm, Chris Jones >>> > wrote:
 
 
 Hi,
 
 Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a 
 coincidence i think you see something relating to this (and you aren’t the 
 only one),
>>> 
>>> Correction. The other message is also from you.
>>> 
>>> I am afraid until someone else reports the same issue and is willing to 
>>> investigate, you might have to do some digging yourself to figure out what 
>>> is going on.
>>> 
>>> Chris
>>> 
 although I cannot say how the OS update could affect macports builds of 
 this library. 
 
 I do not personally run macOS13 yet so cannot investigate, and I fear 
 someone running this OS is going to have to do some leg work to figure out 
 whats going on.
 
 Chris
 
> On 10 Nov 2022, at 5:56 pm, Artemio González López via macports-users 
>  > wrote:
> 
> After installing the 13.0.1 update on my M1 MacBooPro I emacs.app 
> crashes on launch. Apparently, the problem is that it cannot find a 
> library:
> 
> Crashed Thread:0
> 
> Exception Type:EXC_CRASH (SIGABRT)
> Exception Codes:   0x, 0x
> 
> Termination Reason:Namespace DYLD, Code 1 Library missing
> Library not loaded: /opt/local/lib/libicui18n.71.dylib
> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
> /opt/local/lib/libxml2.2.dylib
> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' 
> (no such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
> (terminated at launch; ignore backtrace)
> 
> Does anybody know how to fix this? (I depend on Emacs.app for all my 
> LaTeX editing, so this is quite a problem for me).
> 
> Thanks in advance,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com 
>> 

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Bill Cole]

On 2022-11-10 at 12:56:27 UTC-0500 (Thu, 10 Nov 2022 18:56:27 +0100)
Artemio González López via macports-users 
is rumored to have said:

> After installing the 13.0.1 update on my M1 MacBook Pro I emacs.app crashes 
> on launch. Apparently, the problem is that it cannot find a library:
>
> Crashed Thread:0
>
> Exception Type:EXC_CRASH (SIGABRT)
> Exception Codes:   0x, 0x
>
> Termination Reason:Namespace DYLD, Code 1 Library missing
> Library not loaded: /opt/local/lib/libicui18n.71.dylib
> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
> /opt/local/lib/libxml2.2.dylib
> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
> such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
> (terminated at launch; ignore backtrace)
>
> Does anybody know how to fix this? (I depend on Emacs.app for all my LaTeX 
> editing, so this is quite a problem for me).

Did you follow the documented NECESSARY procedure for reinstalling MacPorts 
after an OS upgrade?


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

Re: C compiler not found after upgrade to macOS 13.0.1

[Chris Jones]

Does

 /opt/local/lib/libicui18n.71.dylib

Actually exist in your system ?

> On 10 Nov 2022, at 7:02 pm, Artemio González López via macports-users 
>  wrote:
> 
> 
>> On 10 Nov 2022, at 18:52, Artemio González López  wrote:
>> 
>> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find any 
>> C compiler:
>> 
>> checking for gcc... /opt/local/bin/clang-mp-14
>> checking whether the C compiler works... no
>> configure: error: in 
>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
>> configure: error: C compiler cannot create executables
>> 
>> However, the CLT seems to be installed:
>> 
>> artemio@mbp-13 ~ % pkgutil 
>> --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
>>  2>/dev/null | sed -n 's/^version: //p'
>> 14.1.0.0.1.1666437224
>> 
>> Does anybody know what’s going on here? (any help would be much appreciated!)
>> 
>> Thanks in advance,
>> 
>> Artemio
>> 
>> 
>> Artemio Gonzalez Lopez
>> artem...@mac.com
>> 
> 
> Actually, this problem is also related to the icu library referenced from 
> libxml. Indeed, looking in Console.app I found a bunch of clang crashes 
> (basically every time it was called in the configure process) like the 
> following:
> 
> Crashed Thread:0
> 
> Exception Type:EXC_CRASH (SIGABRT)
> Exception Codes:   0x, 0x
> 
> Termination Reason:Namespace DYLD, Code 1 Library missing
> Library not loaded: /opt/local/lib/libicui18n.71.dylib
> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
> /opt/local/lib/libxml2.2.dylib
> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
> such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
> 
> Cheers,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com
> 

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Chris Jones]

Please run

 > otool -L /opt/local/lib/libxml2.2.dylib

and paste the output here, and also for each lib it references check it exists 
(and recursively check with otool for the libs they use).

> On 10 Nov 2022, at 7:00 pm, Artemio González López via macports-users 
>  wrote:
> 
> 
> 
>> On 10 Nov 2022, at 19:57, Sriranga Veeraraghavan  
>> wrote:
>> 
>> Hi,
>> 
>> On my Monterey (12.6.1) system, 'port provides' says that the missing 
>> library is provided by the 'icu' port:
>> 
>> $ port provides /opt/local/lib/libicui18n.71.dylib
>> /opt/local/lib/libicui18n.71.dylib is provided by: icu
>> 
>> Perhaps the 'icu' port is not properly installed on your system (you can 
>> check with 'port installed icu').  Or you may need to rebuild it for MacOS 
>> 13.0.1.
>> 
>> Best,
>> 
>> -ranga
> 
> 
> Hi, Sriranga,
> 
> Thank you for your input. However, I’m afraid that’s not the problem, since 
> Emacs.app worked perfectly well right before the update. In any case, icu is 
> still installed:
> 
> artemio@mbp-13 ~ % port installed icu
> The following ports are currently installed:
>   icu @72.1_0 (active)
> 
> Thanks a lot anyway,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com
> 

Re: C compiler not found after upgrade to macOS 13.0.1

[Artemio González López via macports-users]

> On 10 Nov 2022, at 18:52, Artemio González López  wrote:
> 
> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find any 
> C compiler:
> 
> checking for gcc... /opt/local/bin/clang-mp-14
> checking whether the C compiler works... no
> configure: error: in 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
> configure: error: C compiler cannot create executables
> 
> However, the CLT seems to be installed:
> 
> artemio@mbp-13 ~ % pkgutil 
> --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
>  2>/dev/null | sed -n 's/^version: //p'
> 14.1.0.0.1.1666437224
> 
> Does anybody know what’s going on here? (any help would be much appreciated!)
> 
> Thanks in advance,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com
> 

Actually, this problem is also related to the icu library referenced from 
libxml. Indeed, looking in Console.app I found a bunch of clang crashes 
(basically every time it was called in the configure process) like the 
following:

Crashed Thread:0

Exception Type:EXC_CRASH (SIGABRT)
Exception Codes:   0x, 0x

Termination Reason:Namespace DYLD, Code 1 Library missing
Library not loaded: /opt/local/lib/libicui18n.71.dylib
Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
/opt/local/lib/libxml2.2.dylib
Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
'/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
'/usr/local/lib/libicui18n.71.dylib' (no such file), 
'/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)

Cheers,

Artemio


Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Chris Jones]

Does libxml2 declare a dependency against icu ?On 10 Nov 2022, at 6:57 pm, Sriranga Veeraraghavan  wrote:Hi,On my Monterey (12.6.1) system, 'port provides' says that the missing library is provided by the 'icu' port:$ port provides /opt/local/lib/libicui18n.71.dylib/opt/local/lib/libicui18n.71.dylib is provided by: icuPerhaps the 'icu' port is not properly installed on your system (you can check with 'port installed icu').  Or you may need to rebuild it for MacOS 13.0.1.Best,-rangaOn Nov 10, 2022, at 10:48, Chris Jones  wrote:On 10 Nov 2022, at 6:43 pm, Chris Jones  wrote:Hi,Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a coincidence i think you see something relating to this (and you aren’t the only one), Correction. The other message is also from you.I am afraid until someone else reports the same issue and is willing to investigate, you might have to do some digging yourself to figure out what is going on.Chrisalthough I cannot say how the OS update could affect macports builds of this library. I do not personally run macOS13 yet so cannot investigate, and I fear someone running this OS is going to have to do some leg work to figure out whats going on.ChrisOn 10 Nov 2022, at 5:56 pm, Artemio González López via macports-users  wrote:After installing the 13.0.1 update on my M1 MacBooPro I emacs.app crashes on launch. Apparently, the problem is that it cannot find a library:Crashed Thread:        0Exception Type:        EXC_CRASH (SIGABRT)Exception Codes:       0x, 0xTermination Reason:    Namespace DYLD, Code 1 Library missingLibrary not loaded: /opt/local/lib/libicui18n.71.dylibReferenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> /opt/local/lib/libxml2.2.dylibReason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), '/usr/local/lib/libicui18n.71.dylib' (no such file), '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)(terminated at launch; ignore backtrace)Does anybody know how to fix this? (I depend on Emacs.app for all my LaTeX editing, so this is quite a problem for me).Thanks in advance,Artemio
Artemio Gonzalez Lopezartem...@mac.com

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Artemio González López via macports-users]

> On 10 Nov 2022, at 19:57, Sriranga Veeraraghavan  
> wrote:
> 
> Hi,
> 
> On my Monterey (12.6.1) system, 'port provides' says that the missing library 
> is provided by the 'icu' port:
> 
> $ port provides /opt/local/lib/libicui18n.71.dylib
> /opt/local/lib/libicui18n.71.dylib is provided by: icu
> 
> Perhaps the 'icu' port is not properly installed on your system (you can 
> check with 'port installed icu').  Or you may need to rebuild it for MacOS 
> 13.0.1.
> 
> Best,
> 
> -ranga


Hi, Sriranga,

Thank you for your input. However, I’m afraid that’s not the problem, since 
Emacs.app worked perfectly well right before the update. In any case, icu is 
still installed:

artemio@mbp-13 ~ % port installed icu
The following ports are currently installed:
  icu @72.1_0 (active)

Thanks a lot anyway,

Artemio


Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Sriranga Veeraraghavan]

Hi,

On my Monterey (12.6.1) system, 'port provides' says that the missing library 
is provided by the 'icu' port:

$ port provides /opt/local/lib/libicui18n.71.dylib
/opt/local/lib/libicui18n.71.dylib is provided by: icu

Perhaps the 'icu' port is not properly installed on your system (you can check 
with 'port installed icu').  Or you may need to rebuild it for MacOS 13.0.1.

Best,

-ranga


> On Nov 10, 2022, at 10:48, Chris Jones  wrote:
> 
> 
> 
>> On 10 Nov 2022, at 6:43 pm, Chris Jones  wrote:
>> 
>> 
>> Hi,
>> 
>> Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a 
>> coincidence i think you see something relating to this (and you aren’t the 
>> only one),
> 
> Correction. The other message is also from you.
> 
> I am afraid until someone else reports the same issue and is willing to 
> investigate, you might have to do some digging yourself to figure out what is 
> going on.
> 
> Chris
> 
>> although I cannot say how the OS update could affect macports builds of this 
>> library. 
>> 
>> I do not personally run macOS13 yet so cannot investigate, and I fear 
>> someone running this OS is going to have to do some leg work to figure out 
>> whats going on.
>> 
>> Chris
>> 
>>> On 10 Nov 2022, at 5:56 pm, Artemio González López via macports-users 
>>>  wrote:
>>> 
>>> After installing the 13.0.1 update on my M1 MacBooPro I emacs.app crashes 
>>> on launch. Apparently, the problem is that it cannot find a library:
>>> 
>>> Crashed Thread:0
>>> 
>>> Exception Type:EXC_CRASH (SIGABRT)
>>> Exception Codes:   0x, 0x
>>> 
>>> Termination Reason:Namespace DYLD, Code 1 Library missing
>>> Library not loaded: /opt/local/lib/libicui18n.71.dylib
>>> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
>>> /opt/local/lib/libxml2.2.dylib
>>> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>>> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' 
>>> (no such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>>> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
>>> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
>>> (terminated at launch; ignore backtrace)
>>> 
>>> Does anybody know how to fix this? (I depend on Emacs.app for all my LaTeX 
>>> editing, so this is quite a problem for me).
>>> 
>>> Thanks in advance,
>>> 
>>> Artemio
>>> 
>>> 
>>> Artemio Gonzalez Lopez
>>> artem...@mac.com
>>> 

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Chris Jones]

> On 10 Nov 2022, at 6:43 pm, Chris Jones  wrote:
> 
> 
> Hi,
> 
> Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a 
> coincidence i think you see something relating to this (and you aren’t the 
> only one),

Correction. The other message is also from you.

I am afraid until someone else reports the same issue and is willing to 
investigate, you might have to do some digging yourself to figure out what is 
going on.

Chris

> although I cannot say how the OS update could affect macports builds of this 
> library. 
> 
> I do not personally run macOS13 yet so cannot investigate, and I fear someone 
> running this OS is going to have to do some leg work to figure out whats 
> going on.
> 
> Chris
> 
>>> On 10 Nov 2022, at 5:56 pm, Artemio González López via macports-users 
>>>  wrote:
>>> 
>> After installing the 13.0.1 update on my M1 MacBooPro I emacs.app crashes 
>> on launch. Apparently, the problem is that it cannot find a library:
>> 
>> Crashed Thread:0
>> 
>> Exception Type:EXC_CRASH (SIGABRT)
>> Exception Codes:   0x, 0x
>> 
>> Termination Reason:Namespace DYLD, Code 1 Library missing
>> Library not loaded: /opt/local/lib/libicui18n.71.dylib
>> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
>> /opt/local/lib/libxml2.2.dylib
>> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
>> such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
>> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
>> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
>> (terminated at launch; ignore backtrace)
>> 
>> Does anybody know how to fix this? (I depend on Emacs.app for all my LaTeX 
>> editing, so this is quite a problem for me).
>> 
>> Thanks in advance,
>> 
>> Artemio
>> 
>> 
>> Artemio Gonzalez Lopez
>> artem...@mac.com
>> 

Re: C compiler not found after upgrade to macOS 13.0.1

[Artemio González López via macports-users]

> On 10 Nov 2022, at 19:33, Chris Jones  wrote:
> 
> 
> 
>> On 10 Nov 2022, at 5:53 pm, Artemio González López via macports-users 
>>  wrote:
>> 
>> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro),
> 
> Upgrading from what OS ?

Sorry, from macOS 13.0.
> 
>> port cannot find any C compiler:
>> 
>> checking for gcc... /opt/local/bin/clang-mp-14
>> checking whether the C compiler works... no
>> configure: error: in 
>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
>> configure: error: C compiler cannot create executables
>> 
>> However, the CLT seems to be installed:
>> 
>> artemio@mbp-13 ~ % pkgutil 
>> --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
>>  2>/dev/null | sed -n 's/^version: //p'
>> 14.1.0.0.1.1666437224
>> 
>> Does anybody know what’s going on here? (any help would be much appreciated!)
>> 
>> Thanks in advance,
>> 
>> Artemio
>> 
>> 
>> Artemio Gonzalez Lopez
>> artem...@mac.com
>> 

Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

Re: Emacs.app does not run after upgrade to macOS 13.0.1

[Chris Jones]

Hi,

Mac OS 13.0.1 predominantly addresses an issue with libxml2, so its not a 
coincidence i think you see something relating to this (and you aren’t the only 
one), although I cannot say how the OS update could affect macports builds of 
this library. 

I do not personally run macOS13 yet so cannot investigate, and I fear someone 
running this OS is going to have to do some leg work to figure out whats going 
on.

Chris

> On 10 Nov 2022, at 5:56 pm, Artemio González López via macports-users 
>  wrote:
> 
> After installing the 13.0.1 update on my M1 MacBooPro I emacs.app crashes on 
> launch. Apparently, the problem is that it cannot find a library:
> 
> Crashed Thread:0
> 
> Exception Type:EXC_CRASH (SIGABRT)
> Exception Codes:   0x, 0x
> 
> Termination Reason:Namespace DYLD, Code 1 Library missing
> Library not loaded: /opt/local/lib/libicui18n.71.dylib
> Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
> /opt/local/lib/libxml2.2.dylib
> Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
> such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/local/lib/libicui18n.71.dylib' (no such file), 
> '/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
> (terminated at launch; ignore backtrace)
> 
> Does anybody know how to fix this? (I depend on Emacs.app for all my LaTeX 
> editing, so this is quite a problem for me).
> 
> Thanks in advance,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com
> 

Re: C compiler not found after upgrade to macOS 13.0.1

[Chris Jones]

> On 10 Nov 2022, at 5:53 pm, Artemio González López via macports-users 
>  wrote:
> 
> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro),

Upgrading from what OS ?

> port cannot find any C compiler:
> 
> checking for gcc... /opt/local/bin/clang-mp-14
> checking whether the C compiler works... no
> configure: error: in 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
> configure: error: C compiler cannot create executables
> 
> However, the CLT seems to be installed:
> 
> artemio@mbp-13 ~ % pkgutil 
> --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
>  2>/dev/null | sed -n 's/^version: //p'
> 14.1.0.0.1.1666437224
> 
> Does anybody know what’s going on here? (any help would be much appreciated!)
> 
> Thanks in advance,
> 
> Artemio
> 
> 
> Artemio Gonzalez Lopez
> artem...@mac.com
> 

Emacs.app does not run after upgrade to macOS 13.0.1

[Artemio González López via macports-users]

After installing the 13.0.1 update on my M1 MacBook Pro I emacs.app crashes on 
launch. Apparently, the problem is that it cannot find a library:

Crashed Thread:0

Exception Type:EXC_CRASH (SIGABRT)
Exception Codes:   0x, 0x

Termination Reason:Namespace DYLD, Code 1 Library missing
Library not loaded: /opt/local/lib/libicui18n.71.dylib
Referenced from: <45F9A0DF-B06D-34C8-946F-88FFA574E722> 
/opt/local/lib/libxml2.2.dylib
Reason: tried: '/opt/local/lib/libicui18n.71.dylib' (no such file), 
'/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libicui18n.71.dylib' (no 
such file), '/opt/local/lib/libicui18n.71.dylib' (no such file), 
'/usr/local/lib/libicui18n.71.dylib' (no such file), 
'/usr/lib/libicui18n.71.dylib' (no such file, not in dyld cache)
(terminated at launch; ignore backtrace)

Does anybody know how to fix this? (I depend on Emacs.app for all my LaTeX 
editing, so this is quite a problem for me).

Thanks in advance,

Artemio


Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

C compiler not found after upgrade to macOS 13.0.1

[Artemio González López via macports-users]

After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find any C 
compiler:

checking for gcc... /opt/local/bin/clang-mp-14
checking whether the C compiler works... no
configure: error: in 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2/libxml2/work/libxml2-2.10.3':
configure: error: C compiler cannot create executables

However, the CLT seems to be installed:

artemio@mbp-13 ~ % pkgutil 
--pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo}
 2>/dev/null | sed -n 's/^version: //p'
14.1.0.0.1.1666437224

Does anybody know what’s going on here? (any help would be much appreciated!)

Thanks in advance,

Artemio


Artemio Gonzalez Lopez
artem...@mac.com



smime.p7s
Description: S/MIME cryptographic signature

Re: how to move "Python Launcher" away from /Application folder?

[Ryan Schmidt]

On Nov 9, 2022, at 17:57, supervisitor wrote:

> ... ups, this I have probably overlooked. (have made the installation from 
> source).
> 
> But before I now uninstall everything to perform a reinstall, some further 
> questions:
> 
> Can I do an installation with parameter "--with-applications-dir" carefree 
> over the existing installation... without losing the information about 
> installed apps, e.g. inside "registry.db"?
> The documentation for upgrading a source installation is described as follows 
> in the documentation:
>   MacPorts Guide, Chapter: 2.3:
>   "To upgrade a copy of MacPorts that was installed from source to the 
> newer release of the source code, simply repeat the source install with the 
> newer version of the MacPorts source code."
> But does this also apply if I specify an additional parameter like 
> "--with-applications-dir"?
> 
> Or can I change the path afterwards in configuration file(s), e.g. 
> '/opt/local/etc/macports/macports.conf:applications_dir
> /Applications/MacPorts'?
> (of course after a 'sudo mv /Applications/MacPorts /opt/local/.')

I think either is fine: Either reconfigure with a different 
--with-applications-dir or edit applications_dir in macports.conf. Neither will 
affect your installed ports. Any ports you already have installed that put 
files in /Applications/MacPorts will continue to believe that that's where 
their files are and you should not manually move them. After you change the 
setting, you should rebuild those ports (e.g. sudo port -n upgrade --force 
python310).

The pre-compiled archives we build on our servers are tailored to certain 
default MacPorts settings, including the prefix, applications_dir, 
frameworks_dir, and others. If you change these settings, you will not receive 
any pre-compiled archives and will have to compile every port from source when 
you install it. This is usually undesirable (people usually like receiving an 
archive in seconds instead of waiting minutes or hours for a port to compile) 
so I recommend you do not change these settings.

Re: how to move "Python Launcher" away from /Application folder?

[chilli.names...@gmail.com]

If it helps, it can be hidden from the Finder:
sudo chflags hidden /Applications/MacPorts
(undo with "nohidden")


> On Nov 10, 2022, at 09:56, Chris Jones  wrote:
> 
> 
> May I ask, what exactly is your problem with having the Apps installed by 
> MacPorts under /Applications/MacPorts ? I am not really sure I see what the 
> problem is you are trying to fix.
> 
> Chris
> 
>> On 09/11/2022 11:57 pm, supervisitor via macports-users wrote:
>> ... ups, this I have probably overlooked. (have made the installation from 
>> source).
>> But before I now uninstall everything to perform a reinstall, some further 
>> questions:
>> Can I do an installation with parameter "--with-applications-dir" carefree 
>> over the existing installation... without losing the information about 
>> installed apps, e.g. inside "registry.db"?
>> The documentation for upgrading a source installation is described as 
>> follows in the documentation:
>>MacPorts Guide, Chapter: 2.3:
>>"To upgrade a copy of MacPorts that was installed from source to the 
>> newer release of the source code, simply repeat the source install with the 
>> newer version of the MacPorts source code."
>> But does this also apply if I specify an additional parameter like 
>> "--with-applications-dir"?
>> Or can I change the path afterwards in configuration file(s), e.g. 
>> '/opt/local/etc/macports/macports.conf:applications_dir
>> /Applications/MacPorts'?
>> (of course after a 'sudo mv /Applications/MacPorts /opt/local/.')
>> Does anyone have any experience or reliable information on this?
>> Thanks and cheers!
 On 9 Nov 2022, at 16:54, Langer, Stephen A. (Fed) 
  wrote:
>>> 
>>> Build MacPorts from source and use the --with-applications-dir option when 
>>> configuring it.
>>> 
>>> -- Steve
>>> 
>>> -Original Message-
>>> From: macports-users  on behalf 
>>> of supervisitor via macports-users 
>>> Reply-To: supervisitor 
>>> Date: Wednesday, November 9, 2022 at 10:38 AM
>>> To: "macports-users@lists.macports.org" 
>>> Subject: how to move "Python Launcher" away from /Application folder?
>>> 
>>>Hi.
>>> 
>>>This "MacPorts" folder inside Applications, where the Python Launcher is 
>>> inside, looks useless for me... but is needed when I launch "port -v 
>>> upgrade outdated" from terminal.
>>>=> does someone know a solution to move this folder and files inside 
>>> away from there, best would be inside /opt/...
>>> 
>>>Cheers...
>>> 
>>> 

Re: how to move "Python Launcher" away from /Application folder?

[Chris Jones]

May I ask, what exactly is your problem with having the Apps installed 
by MacPorts under /Applications/MacPorts ? I am not really sure I see 
what the problem is you are trying to fix.


Chris

On 09/11/2022 11:57 pm, supervisitor via macports-users wrote:

... ups, this I have probably overlooked. (have made the installation from 
source).

But before I now uninstall everything to perform a reinstall, some further 
questions:

Can I do an installation with parameter "--with-applications-dir" carefree over the 
existing installation... without losing the information about installed apps, e.g. inside 
"registry.db"?
The documentation for upgrading a source installation is described as follows 
in the documentation:
MacPorts Guide, Chapter: 2.3:
"To upgrade a copy of MacPorts that was installed from source to the newer 
release of the source code, simply repeat the source install with the newer version of 
the MacPorts source code."
But does this also apply if I specify an additional parameter like 
"--with-applications-dir"?

Or can I change the path afterwards in configuration file(s), e.g. 
'/opt/local/etc/macports/macports.conf:applications_dir
/Applications/MacPorts'?
(of course after a 'sudo mv /Applications/MacPorts /opt/local/.')

Does anyone have any experience or reliable information on this?


Thanks and cheers!




On 9 Nov 2022, at 16:54, Langer, Stephen A. (Fed)  
wrote:

Build MacPorts from source and use the --with-applications-dir option when 
configuring it.

-- Steve

-Original Message-
From: macports-users  on behalf of 
supervisitor via macports-users 
Reply-To: supervisitor 
Date: Wednesday, November 9, 2022 at 10:38 AM
To: "macports-users@lists.macports.org" 
Subject: how to move "Python Launcher" away from /Application folder?

Hi.

This "MacPorts" folder inside Applications, where the Python Launcher is inside, 
looks useless for me... but is needed when I launch "port -v upgrade outdated" from 
terminal.
=> does someone know a solution to move this folder and files inside away 
from there, best would be inside /opt/...

Cheers...