[MacPorts] #71730: Fails to build Python313 on Sequoia

MacPorts noreply at macports.org
Sat Jan 4 00:32:32 UTC 2025


#71730: Fails to build Python313 on Sequoia
-------------------------+--------------------
  Reporter:  mouse07410  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  python313   |
-------------------------+--------------------

Comment (by kencu):

 Or (considerably more likely) there is still something wrong on your
 system.

 So far as we know, nobody else has this problem anywhere, and googling for
 it shows nothing to me. Python is extensively tested upstream, and by many
 users.

 Port stats show many installations:

 https://ports.macports.org/port/python313/stats/

 Homebrew has it's python3.13 installed with optimizations on:

 https://github.com/Homebrew/homebrew-
 core/blob/90efd58b0cd379a32147ae43fccb768e165d36eb/Formula/p/python at 3.13.rb

 and there are over 300,000 installations of that.

 https://formulae.brew.sh/formula/python@3.13

 So I would again look more closely at your system:

 1. does your Xcode match your CLTs? If so, make them match.
 1. is there anything in /usr/local? If so remove it.
 1. have you selected anything with "port select"? if so disable it all.
 1. have you monkey around with symlinks in your SDKs folder? If so, fix
 them.
 1. have you modified any of the builds of any of your ports manuallly --
 forced a compiler, editied a Portfile? If so, undo that.
 1. have any of the port you installed when you had no CLTs installed been
 installed in an "incorrect" fashion because there were no CLTs? Anything
 that burns in a path to an SDK or compiler setting (PERL, python, etc,
 etc, etc) are suspect.
 1. have you set up anything in your PATH besides default MacPorts
 settings? Are you modifying anything at all in or your .zshrc?
 1. are you using any non-default options? Any DEVEL ports? LIBRESSL
 instead of OPENSSL? Etc etc etc.

 If ALL of that indicates you have a 100% clean system, then all it can
 come down to after all that is an interaction with some port you have
 installed that most of us would not have installed that is hosing the
 build.

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


More information about the macports-tickets mailing list