public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Charles Brown <cab_77573@yahoo.com>
Cc: IPFire Development <development@lists.ipfire.org>
Subject: Re: Failed Build of 'next' x86_64 on GNU/Linux 13 (trixie)
Date: Tue, 16 Sep 2025 11:02:32 +0100	[thread overview]
Message-ID: <EAD1A508-9ACB-4DD1-AEE8-3FBF020757E6@ipfire.org> (raw)
In-Reply-To: <82cf8abd-de70-4495-8997-36db9d8f2ebd@yahoo.com>

Ah, you are building the toolchain. I pushed a change:

  https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=8e9dd5d165b1cbb6b9ebd6d1e4bd0a7a2af0a3dd

Could you please pull and resume the build?

-Michael

> On 16 Sep 2025, at 10:49, Charles Brown <cab_77573@yahoo.com> wrote:
> 
> The directory contains only a README file ...
> cbrown@samba:~/myProject/ipfire-2.x/build_x86_64$ ls -l ./tools_x86_64/lib/python3.10/site-packages
> total 4
> -rw-r--r-- 1 root root 119 Sep 16 04:35 README.txt
> 
> On 9/16/2025 4:24 AM, Michael Tremer wrote:
>> And? Does the directory actually not exist?
>> 
>> -Michael
>> 
>>> On 15 Sep 2025, at 22:19, Charles Brown <cab_77573@yahoo.com> wrote:
>>> 
>>> Hi All,
>>> I did a fresh pull ...
>>> 
>>>     commit 0fb06f864f987396be173350362b35f1ebe1fd17 (HEAD -> next, origin/next)
>>>     Author: Adolf Belka <adolf.belka@ipfire.org>
>>>     Date:   Mon Sep 15 17:47:27 2025 +0200
>>> 
>>> Then did a clean and build -- resulting in new/different breakage
>>> 
>>> =============================================================================================
>>> ...
>>> perl (5.36.0)      [     2:24 ][ DONE ]
>>> python3 (3.10.8)       [     1:22 ][ FAIL ]
>>> 
>>>     rm -f /tools_x86_64/bin/pydoc3
>>>     (cd /tools_x86_64/bin; ln -s pydoc3.10 pydoc3)
>>>     rm -f /tools_x86_64/bin/2to3
>>>     (cd /tools_x86_64/bin; ln -s 2to3-3.10 2to3)
>>>     if test "x" != "x" ; then \
>>>     rm -f /tools_x86_64/bin/python3-32; \
>>>     (cd /tools_x86_64/bin; ln -s python3.10-32 python3-32) \
>>>     fi
>>>     if test "x" != "x" ; then \
>>>     rm -f /tools_x86_64/bin/python3-intel64; \
>>>     (cd /tools_x86_64/bin; ln -s python3.10-intel64 python3-intel64) \
>>>     fi
>>>     rm -f /tools_x86_64/share/man/man1/python3.1
>>>     (cd /tools_x86_64/share/man/man1; ln -s python3.10.1 python3.1)
>>>     if test "xno" != "xno"  ; then \
>>>     case no in \
>>>     upgrade) ensurepip="--upgrade" ;; \
>>>     install|*) ensurepip="" ;; \
>>>     esac; \
>>>     ./python -E -m ensurepip \
>>>     $ensurepip --root=/ ; \
>>>     fi
>>>     make[1]: Leaving directory '/home/cbrown/myProject/ipfire-2.x/build_x86_64/usr/src/Python-3.10.8'
>>>     # Remove precompiled pycache at toolchain and tests
>>>     cd /tools_x86_64/lib/python3.10 && find . | grep -E "(/__pycache__|/test/)" | xargs rm -rf
>>>     # Remove the bundled setuptools directories
>>>     cd /usr/lib/python3.10/site-packages/ && rm -r setuptools*
>>> /bin/sh: 1: cd: can't cd to /usr/lib/python3.10/site-packages/
>>>     make: *** [python3:104: /home/cbrown/myProject/ipfire-2.x/log_x86_64/Python-3.10.8-tools] Error 2
>>>     make: Leaving directory '/home/cbrown/myProject/ipfire-2.x/lfs'
>>> 
>>> ERROR: Building python3      [ FAIL ]
>>>     Check /home/cbrown/myProject/ipfire-2.x/log_x86_64/_build.toolchain.log for errors if applicable[ FAIL ]
>>> 
>>> ===============================================================================================
>>> 
>>> -Charles
>>> 
>>> 
>>> 
>>> 
> 



  reply	other threads:[~2025-09-16 10:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5cd17450-2b6a-48d3-921f-6c6a2c48ee1c.ref@yahoo.com>
2025-09-15 21:19 ` Charles Brown
2025-09-16  9:24   ` Michael Tremer
2025-09-16  9:46     ` Charles Brown
2025-09-16  9:49     ` Charles Brown
2025-09-16 10:02       ` Michael Tremer [this message]
2025-09-16 10:39         ` Charles Brown
2025-09-16 10:46           ` Michael Tremer
     [not found] <e08f7347-f278-44e8-9980-52f975f1202c.ref@yahoo.com>
2025-09-15 21:06 ` Charles Brown
     [not found] <91d9cd50-25da-4eb2-8500-88978d759a7b.ref@yahoo.com>
2025-09-07 23:52 ` Charles Brown
2025-09-13 10:36   ` Michael Tremer
2025-09-13 12:47     ` Matthias Fischer
2025-09-13 12:48       ` Michael Tremer
2025-09-13 14:12         ` Matthias Fischer
2025-09-13 15:00           ` Adolf Belka
2025-09-13 15:06             ` Adolf Belka
2025-09-13 15:43               ` Adolf Belka
2025-09-13 15:52                 ` Adolf Belka
2025-09-13 19:21           ` Matthias Fischer
2025-09-13 20:37             ` Adolf Belka
2025-09-14  9:31               ` Michael Tremer
2025-09-14 10:32                 ` Adolf Belka
2025-09-14 10:48                   ` Michael Tremer
2025-09-14 11:21                     ` Adolf Belka
2025-09-14 11:44                       ` Adolf Belka
2025-09-14 15:47                         ` Adolf Belka
2025-09-14 15:51                           ` Michael Tremer
2025-09-15 10:13                             ` Michael Tremer
2025-09-15 15:29                               ` Adolf Belka
2025-09-15 15:36                                 ` Matthias Fischer
2025-09-15 23:04                                 ` Matthias Fischer
2025-09-16 11:31                                 ` Matthias Fischer
2025-09-13 19:19     ` Charles Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EAD1A508-9ACB-4DD1-AEE8-3FBF020757E6@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=cab_77573@yahoo.com \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox