https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289224

            Bug ID: 289224
           Summary: building net/samba416 KO with lang/python312
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-b...@freebsd.org
          Reporter: nico...@nlhq.co.uk
                CC: python@FreeBSD.org, sa...@freebsd.org
                CC: python@FreeBSD.org, sa...@freebsd.org

Created attachment 263378
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=263378&action=edit
samba416-4.16.11_10.log

When I'm building net/samba416:

Checking for program 'python3'                                                 
  : /usr/local/bin/python3.12 
Checking for program 'python'                                                  
  : /usr/local/bin/python3.12 
Checking for program 'python3'                                                 
  : not found 
The distutils module is unusable: install "python-devel"?
(complete log in
/wrkdirs/usr/ports/net/samba416/work-default/samba-4.16.11/bin/config.log)
===>  Script "configure" failed unexpectedly.
Please report the problem to sa...@freebsd.org [maintainer] and attach the
"/wrkdirs/usr/ports/net/samba416/work-default/samba-4.16.11/bin/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

Stop.
make: stopped in /usr/ports/net/samba416
=>> Cleaning up wrkdir
===>  Cleaning for samba416-4.16.11_10
build of net/samba416@default | samba416-4.16.11_10 ended at Mon Sep  1
08:16:23 CEST 2025
build time: 00:04:49
!!! build failure encountered !!!


Everything's OK when I use lang/python3.11. Issue seems to occur only when
using lang/python3.12

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to