Bug 291360 - lang/python313: Fails to build on 16-CURRENT or could be something else
Summary: lang/python313: Fails to build on 16-CURRENT or could be something else
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-python (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-03 03:02 UTC by Cy Schubert
Modified: 2025-12-04 00:55 UTC (History)
1 user (show)

See Also:
vishwin: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cy Schubert freebsd_committer freebsd_triage 2025-12-03 03:02:54 UTC 
lang/python313 fails to build with the error,

install -s -m 0644 Modules/_curses_panel.cpython-313.so /usr/local/lib/python3.13/lib-dynload/_curses_panel.cpython-313.so
install: Modules/_curses_panel.cpython-313.so: No such file or directory
*** Error code 71
Comment 1 Charlie Li freebsd_committer freebsd_triage 2025-12-03 06:24:17 UTC 
Looks like _curses_panel failed to build. Unlike most other ports, the overall build continues if modules, but not the main interpreter or other critical components, fail to build.

That said, I can't reproduce. You may want to check that your libcurses is intact.
Comment 2 Cy Schubert freebsd_committer freebsd_triage 2025-12-03 12:55:31 UTC 
(In reply to Charlie Li from comment #1)

I'm running,

FreeBSD slippy.cwsent.com 16.0-CURRENT FreeBSD 16.0-CURRENT #6 komquats-n282287-07d5a9b1b2dd: Tue Dec  2 07:29:13 PST 2025     root@stinky:/export/obj/opt/src/git-src/amd64.amd64/sys/BREAK amd64

The build failure occurs on all five of my 16-CURRENT machines here.

The world/kernel are rebuilt weekly at a minimum. Many times daily. The port build failure has been occurring ever since the port hit the ports repo. I did not submit the PR then in the hope that it might be fixed.
Comment 3 Charlie Li freebsd_committer freebsd_triage 2025-12-03 15:17:36 UTC 
Yes, I also run frequently-updated -CURRENT and have never reproduced this. The package builders also don't fallout in this manner either. Do you have a configure, build, stage log?
Comment 4 Cy Schubert freebsd_committer freebsd_triage 2025-12-03 16:15:11 UTC 
Hmmm. My poudriere fails on the same error too. I'll need to see why that library fails to build and report back.
Comment 5 Cy Schubert freebsd_committer freebsd_triage 2025-12-04 00:55:11 UTC 
This is local problem. The ports tree I was using was not my latest copy new-ports. It was a older copy with cherry-picks. My new-ports poudriere build did work after all.