public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Unending item build
Date: Wed, 15 Jan 2025 15:57:41 +0000	[thread overview]
Message-ID: <961FB81A-3E08-40E7-A2BD-FA10E772B79E@ipfire.org> (raw)
In-Reply-To: <DB6F5ACC-3FDB-4D2D-A085-1196AC99DDEA@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 10859 bytes --]

Hello,

Yes, but that does not seem to matter I think.

I am usually getting a root console and don’t use sudo every time I run ./make.sh. Can you confirm the problem remains if you become root first with “sudo -i” and then run ./make.sh?

-Michael

> On 15 Jan 2025, at 15:30, jon <jon.murphy(a)ipfire.org> wrote:
> 
> For `/home/jon` yes.
> 
> Is this what "bash start" is?
> 
> 
> jon(a)deb12HPZ:~/development/ipfire-2.x$ cat /home/jon/.bash_aliases
> cat /home/jon/.bash_aliases
> # .bash_aliases
> # Added by JCM
> 
> # If not running interactively, don't do anything
> if [[ $- == *i* ]] ; then
> alias ll='ls -al --time-style=long-iso --color=auto'
> alias hs='history | grep --color -i'
> alias sfind='sudo find / \( -path /proc -o -path /dev -o -path /sys -o -path /mnt \) -prune -o -iname' 2>/dev/null
> alias dfind='sudo find . \( -path /proc -o -path /dev -o -path /sys -o -path /mnt -o -path /ccache \) -prune -o -iname' 2>/dev/null
> 
> lso() { ls -al "$@" --color | awk '{k=0;for(i=0;i<=8;i++)k+=((substr($1,i+2,1)~/[rwx]/)*2^(8-i));if(k)printf(" %0o ",k);print}'; }
> printf "\nThe date now is %s\n" "$(date)"
> fi
> jon(a)deb12HPZ:~/development/ipfire-2.x$ 
> 
> 
> 
>> On Jan 15, 2025, at 9:20 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>> 
>> Hello,
>> 
>> root(a)michael:/build/ipfire-2.x# cat /etc/os-release
>> PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
>> NAME="Debian GNU/Linux"
>> VERSION_ID="12"
>> VERSION="12 (bookworm)"
>> VERSION_CODENAME=bookworm
>> ID=debian
>> HOME_URL="https://www.debian.org/"
>> SUPPORT_URL="https://www.debian.org/support"
>> BUG_REPORT_URL="https://bugs.debian.org/"
>> 
>> root(a)michael:/build/ipfire-2.x# uname -a
>> Linux michael.haj.ipfire.org 6.1.0-28-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux
>> 
>> root(a)michael:/build/ipfire-2.x# bash --version
>> GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
>> Copyright (C) 2022 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>> 
>> This is free software; you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> 
>> We seem to be pretty much on the same software and I am not experiencing this problem. Did you change the bash start files?
>> 
>> -Michael
>> 
>>> On 15 Jan 2025, at 15:06, jon <jon.murphy(a)ipfire.org> wrote:
>>> 
>>> Michael,
>>> 
>>> Here ya go!
>>> 
>>> Is there something else I can send to help fix?
>>> 
>>> Jon
>>> 
>>> 
>>>> On Jan 15, 2025, at 5:17 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>>> 
>>>> Hello Jon,
>>>> 
>>>> Someone has reported this before, and it seems to be a bug in some versions of bash.
>>> 
>>> 
>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ bash -version
>>> bash -version
>>> GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)
>>> Copyright (C) 2022 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>>> 
>>> This is free software; you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>> jon(a)deb12HPZ:~/development/ipfire-2.x$
>>> 
>>> 
>>>> 
>>>> What OS are you running this on?
>>> 
>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ uname -a
>>> Linux deb12HPZ 6.1.0-29-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.123-1 (2025-01-02) x86_64 GNU/Linux
>>> 
>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ cat /etc/os-release
>>> PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
>>> NAME="Debian GNU/Linux"
>>> VERSION_ID="12"
>>> VERSION="12 (bookworm)"
>>> VERSION_CODENAME=bookworm
>>> ID=debian
>>> HOME_URL="https://www.debian.org/"
>>> SUPPORT_URL="https://www.debian.org/support"
>>> BUG_REPORT_URL="https://bugs.debian.org/"
>>> 
>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ cat /etc/debian_version
>>> 12.9
>>> 
>>> 
>>> 
>>> 
>>>> I am usually not experiencing this at all on an up to date Debian 12.
>>>> 
>>>> -Michael
>>>> 
>>>>> On 15 Jan 2025, at 04:27, jon <jon.murphy(a)ipfire.org> wrote:
>>>>> 
>>>>> Hello all!
>>>>> 
>>>>> For the past two or three days the ./make.sh build  goes into a loop and builds an item forever.   
>>>>> 
>>>>> Once it happened when building:  samba (4.21.0)                         [  9:41:23 ]^C
>>>>> pcengines-apu-firmware (4.19.0.1)      [  1:32:17 ]^C
>>>>> perl-Parse-Yapp (1.21)                 [  2:38:07 ]^C
>>>>> 
>>>>> 
>>>>> When it runs away I will terminate the build.  
>>>>> 
>>>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ sudo ./make.sh clean
>>>>> Cleaning build directory...                                                                              [ DONE ]
>>>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ sudo ./make.sh build
>>>>> Packaged toolchain compilation
>>>>> Building IPFire
>>>>> stage2                                                                                        [        0 ][ DONE ]
>>>>> linux (6.6.47) HEADERS=1                                                                      [       26 ][ DONE ]
>>>>> man-pages (6.9.1)                                                                             [        8 ][ DONE ]
>>>>> . . .
>>>>> perl-Device-Modem (1.56)                                                                      [        1 ][ DONE ]
>>>>> perl-Apache-Htpasswd (1.9)                                                                    [        1 ][ DONE ]
>>>>> perl-Parse-Yapp (1.21)                                                                        [  2:38:07 ]^C
>>>>>   cp lib/Parse/Yapp.pm blib/lib/Parse/Yapp.pm
>>>>>   cp lib/Parse/Yapp/Grammar.pm blib/lib/Parse/Yapp/Grammar.pm
>>>>>   cp lib/Parse/Yapp/Output.pm blib/lib/Parse/Yapp/Output.pm
>>>>>   cp lib/Parse/Yapp/Parse.pm blib/lib/Parse/Yapp/Parse.pm
>>>>>   cp lib/Parse/Yapp/Lalr.pm blib/lib/Parse/Yapp/Lalr.pm
>>>>>   cp yapp blib/script/yapp
>>>>>   "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/yapp
>>>>>   Manifying 1 pod document
>>>>>   Manifying 1 pod document
>>>>>   make[1]: Leaving directory '/usr/src/Parse-Yapp-1.21'
>>>>>   cd /usr/src/Parse-Yapp-1.21 && make install
>>>>>   make[1]: Entering directory '/usr/src/Parse-Yapp-1.21'
>>>>>   Manifying 1 pod document
>>>>>   Manifying 1 pod document
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp.pm
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Driver.pm
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Options.pm
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Output.pm
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Lalr.pm
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Grammar.pm
>>>>>   Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Parse.pm
>>>>>   Installing /usr/share/man/man1/yapp.1
>>>>>   Installing /usr/share/man/man3/Parse::Yapp.3
>>>>>   Installing /usr/bin/yapp
>>>>>   Appending installation info to /usr/lib/perl5/5.36.0/x86_64-linux-thread-multi/perllocal.pod
>>>>>   make[1]: Leaving directory '/usr/src/Parse-Yapp-1.21'
>>>>>   Updating linker cache...
>>>>>   Install done; saving file list to /usr/src/log/Parse-Yapp-1.21 ...
>>>>> 
>>>>>   make: Leaving directory '/usr/src/lfs'
>>>>> 
>>>>> ERROR: Build process interrupted                                                                          [ FAIL ]
>>>>>   Check /home/jon/development/ipfire-2.x/log_x86_64/_build.ipfire.log for errors if applicable          [ FAIL ]
>>>>> jon(a)deb12HPZ:~/development/ipfire-2.x$ 
>>>>> 
>>>>> 
>>>>> 
>>>>> And here is the build.ipfire.log:
>>>>> 
>>>>> make[1]: Leaving directory '/usr/src/Apache-Htpasswd-1.9'
>>>>> Updating linker cache...
>>>>> Install done; saving file list to /usr/src/log/Apache-Htpasswd-1.9 ...
>>>>> 
>>>>> make: Leaving directory '/usr/src/lfs'
>>>>> Jan 14 21:51:47: Building perl-Parse-Yapp make: Entering directory '/home/jon/development/ipfire-2.x/lfs'
>>>>> make: Nothing to be done for 'download'.
>>>>> make: Leaving directory '/home/jon/development/ipfire-2.x/lfs'
>>>>> make: Entering directory '/usr/src/lfs'
>>>>> ====================================== Installing Parse-Yapp-1.21 ...
>>>>> Install started; saving file list to /usr/src/lsalr ...
>>>>> cd /usr/src/Parse-Yapp-1.21 && perl Makefile.PL
>>>>> Checking if your kit is complete...
>>>>> Looks good
>>>>> Generating a Unix-style Makefile
>>>>> Writing Makefile for Parse::Yapp
>>>>> Writing MYMETA.yml and MYMETA.json
>>>>> cd /usr/src/Parse-Yapp-1.21 && make -j12 
>>>>> make[1]: Entering directory '/usr/src/Parse-Yapp-1.21'
>>>>> cp lib/Parse/Yapp/Options.pm blib/lib/Parse/Yapp/Options.pm
>>>>> cp lib/Parse/Yapp/Driver.pm blib/lib/Parse/Yapp/Driver.pm
>>>>> cp lib/Parse/Yapp.pm blib/lib/Parse/Yapp.pm
>>>>> cp lib/Parse/Yapp/Grammar.pm blib/lib/Parse/Yapp/Grammar.pm
>>>>> cp lib/Parse/Yapp/Output.pm blib/lib/Parse/Yapp/Output.pm
>>>>> cp lib/Parse/Yapp/Parse.pm blib/lib/Parse/Yapp/Parse.pm
>>>>> cp lib/Parse/Yapp/Lalr.pm blib/lib/Parse/Yapp/Lalr.pm
>>>>> cp yapp blib/script/yapp
>>>>> "/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/yapp
>>>>> Manifying 1 pod document
>>>>> Manifying 1 pod document
>>>>> make[1]: Leaving directory '/usr/src/Parse-Yapp-1.21'
>>>>> cd /usr/src/Parse-Yapp-1.21 && make install
>>>>> make[1]: Entering directory '/usr/src/Parse-Yapp-1.21'
>>>>> Manifying 1 pod document
>>>>> Manifying 1 pod document
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp.pm
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Driver.pm
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Options.pm
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Output.pm
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Lalr.pm
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Grammar.pm
>>>>> Installing /usr/lib/perl5/site_perl/5.36.0/Parse/Yapp/Parse.pm
>>>>> Installing /usr/share/man/man1/yapp.1
>>>>> Installing /usr/share/man/man3/Parse::Yapp.3
>>>>> Installing /usr/bin/yapp
>>>>> Appending installation info to /usr/lib/perl5/5.36.0/x86_64-linux-thread-multi/perllocal.pod
>>>>> make[1]: Leaving directory '/usr/src/Parse-Yapp-1.21'
>>>>> Updating linker cache...
>>>>> Install done; saving file list to /usr/src/log/Parse-Yapp-1.21 ...
>>>>> 
>>>>> make: Leaving directory '/usr/src/lfs'
>>>>> 
>>>>> 
>>>>> Any thoughts on why an item build would not complete?
>>>>> 
>>>>> Jon
>>>>> 
>>>> 
>>> 
>>> Jon
>>> 
>>> 
>>> -- 
>>> Jon Murphy
>>> jon.murphy(a)ipfire.org
>> 
>> 
> 
> Jon
> 
> 
> -- 
> Jon Murphy
> jon.murphy(a)ipfire.org
> 
> 
> 
> 


       reply	other threads:[~2025-01-15 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DB6F5ACC-3FDB-4D2D-A085-1196AC99DDEA@ipfire.org>
2025-01-15 15:57 ` Michael Tremer [this message]
     [not found] <CFF4CB57-76DE-4DEE-B326-7A9C4DB10167@ipfire.org>
2025-01-16 14:51 ` Adolf Belka
     [not found] <38F20545-1C4D-4215-989B-F5F3B36A414F@ipfire.org>
2025-01-15 15:20 ` Michael Tremer
     [not found] <59D090B9-5E2E-4ED5-913C-16636CC46903@ipfire.org>
2025-01-15 11:17 ` Michael Tremer

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=961FB81A-3E08-40E7-A2BD-FA10E772B79E@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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