[MacPorts] #71846: python 310 fails on 10.11 for _getentropy

MacPorts noreply at macports.org
Thu Jan 16 09:42:10 UTC 2025


#71846: python 310 fails on 10.11 for _getentropy
------------------------+------------------------------
  Reporter:  rmottola   |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:
Resolution:             |   Keywords:  elcapitan python
      Port:  python310  |
------------------------+------------------------------

Comment (by rmottola):

 I attempted a build with clang 17... expecting to actually reproduce the
 error or by change hanving the function, instead, it breaks with:


 {{{
 /opt/local/bin/clang-mp-17 -c -Wno-unused-result -Wsign-compare
 -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall
 -arch x86_64 -arch i386 -pipe -Os
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk -arch x86_64
 -arch i386   -flto -std=c99 -Wextra -Wno-unused-result -Wno-unused-
 parameter -Wno-missing-field-initializers -Werror=implicit-function-
 declaration -fvisibility=hidden -fprofile-instr-generate
 -I./Include/internal  -I. -I./Include -I/opt/local/include
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
 -DPy_BUILD_CORE -o Parser/token.o Parser/token.c
 fatal error: /opt/local/bin/lipo: can't figure out the architecture type
 of:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/.tmp
 /token-0e029b/token-x86_64.o
 fatal error: /opt/local/bin/lipo: can't figure out the architecture type
 of:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/.tmp
 /python-71cd2a/python-x86_64.o
 clang: error: lipo command failed with exit code 1 (use -v to see
 invocation)
 clang: error: lipo command failed with exit code 1 (use -v to see
 invocation)
 }}}

 I don't know what the lipo command is, but appears a glitch in the
 macports compiler it it can't know the architecture?

-- 
Ticket URL: <https://trac.macports.org/ticket/71846#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list