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 <[email protected]> wrote:
> 
> 
> 
>>> On 10 Nov 2022, at 20:05, Chris Jones <[email protected]> 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 
>>>> <[email protected]> wrote:
>>>> 
>>> 
>>>> On 10 Nov 2022, at 18:52, Artemio González López <[email protected]> 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
>>>> [email protected]
>>>> 
>>> 
>>> 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:       0x0000000000000000, 0x0000000000000000
>>> 
>>> 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
>>> [email protected]
>>> 
> 
> Artemio Gonzalez Lopez
> [email protected]
> 

Reply via email to