Unending item build

Unending item build

[Matthias Fischer]

Hi all,

I'd like to warm up an old problem...perhaps I found something like a
solution.

The original problem is rather old - it dates from 2025-01-15. It still
can be found here:
https://marc.info/?l=ipfire-development&m=173691503411708

Once in a while I experienced the same problem like Jon - building
stopped suddenly: "./make.sh build  goes into a loop and builds an item
forever." And it doesn't matter which item. Either the counter kept
running indefinitely, or it stopped displaying anything at all.

That was pretty annoying. No errors, nothing in the logs. After stopping
the build with CTRL-C and restarting the whole build, usually everything
ran through and worked again as if nothing had happened.

The last message often was just "make: Leaving directory '/usr/src/lfs'"
and that was all.

Lastly I was thinking it might have something to do with counters.
So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.

Since then buildings are running without stopping anymore...

Did anyone had similar problems?

Best
Matthias

Re: Unending item build

[Michael Tremer]

Hello Matthias,

> On 8 Jun 2026, at 12:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> Hi all,
> 
> I'd like to warm up an old problem...perhaps I found something like a
> solution.
> 
> The original problem is rather old - it dates from 2025-01-15. It still
> can be found here:
> https://marc.info/?l=ipfire-development&m=173691503411708
> 
> Once in a while I experienced the same problem like Jon - building
> stopped suddenly: "./make.sh build  goes into a loop and builds an item
> forever." And it doesn't matter which item. Either the counter kept
> running indefinitely, or it stopped displaying anything at all.
> 
> That was pretty annoying. No errors, nothing in the logs. After stopping
> the build with CTRL-C and restarting the whole build, usually everything
> ran through and worked again as if nothing had happened.
> 
> The last message often was just "make: Leaving directory '/usr/src/lfs'"
> and that was all.
> 
> Lastly I was thinking it might have something to do with counters.
> So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.
> 
> Since then buildings are running without stopping anymore...
> 
> Did anyone had similar problems?

Very rarely. I think I have seen it before, but I cannot reproduce it at all.

I am happy to remove the timer entirely because it would be sufficient to see the build time after the package has finished building.

Would anyone be opposed to that?

-Michael

> Best
> Matthias
> 
> 

Re: Unending item build

[Matthias Fischer]

On 08.06.2026 16:03, Michael Tremer wrote:
> Hello Matthias,

Hi Michael,

>> On 8 Jun 2026, at 12:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>> 
>> Hi all,
>> 
>> I'd like to warm up an old problem...perhaps I found something like a
>> solution.
>> 
>> The original problem is rather old - it dates from 2025-01-15. It still
>> can be found here:
>> https://marc.info/?l=ipfire-development&m=173691503411708
>> 
>> Once in a while I experienced the same problem like Jon - building
>> stopped suddenly: "./make.sh build  goes into a loop and builds an item
>> forever." And it doesn't matter which item. Either the counter kept
>> running indefinitely, or it stopped displaying anything at all.
>> 
>> That was pretty annoying. No errors, nothing in the logs. After stopping
>> the build with CTRL-C and restarting the whole build, usually everything
>> ran through and worked again as if nothing had happened.
>> 
>> The last message often was just "make: Leaving directory '/usr/src/lfs'"
>> and that was all.
>> 
>> Lastly I was thinking it might have something to do with counters.
>> So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.
>> 
>> Since then buildings are running without stopping anymore...
>> 
>> Did anyone had similar problems?
> 
> Very rarely. I think I have seen it before, but I cannot reproduce it at all.

Yep. It happens just now and then, you never know when and why...

> I am happy to remove the timer entirely because it would be sufficient to see the build time after the package has finished building.

+1. You got my vote. The simpler, the better.
> Would anyone be opposed to that?

No. ;-)

Best
Matthias

Re: Unending item build

[Adolf Belka]

Hi Michael and Matthias,

On 08/06/2026 16:09, Matthias Fischer wrote:
> On 08.06.2026 16:03, Michael Tremer wrote:
>> Hello Matthias,
> Hi Michael,
>
>>> On 8 Jun 2026, at 12:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>
>>> Hi all,
>>>
>>> I'd like to warm up an old problem...perhaps I found something like a
>>> solution.
>>>
>>> The original problem is rather old - it dates from 2025-01-15. It still
>>> can be found here:
>>> https://marc.info/?l=ipfire-development&m=173691503411708
>>>
>>> Once in a while I experienced the same problem like Jon - building
>>> stopped suddenly: "./make.sh build  goes into a loop and builds an item
>>> forever." And it doesn't matter which item. Either the counter kept
>>> running indefinitely, or it stopped displaying anything at all.
>>>
>>> That was pretty annoying. No errors, nothing in the logs. After stopping
>>> the build with CTRL-C and restarting the whole build, usually everything
>>> ran through and worked again as if nothing had happened.
>>>
>>> The last message often was just "make: Leaving directory '/usr/src/lfs'"
>>> and that was all.
>>>
>>> Lastly I was thinking it might have something to do with counters.
>>> So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.
>>>
>>> Since then buildings are running without stopping anymore...
>>>
>>> Did anyone had similar problems?
>> Very rarely. I think I have seen it before, but I cannot reproduce it at all.
> Yep. It happens just now and then, you never know when and why...

I also very occasionally get the same problem. I have also had it when 
doing a build on the IPFire aarch64 and riscv64 builder.
>> I am happy to remove the timer entirely because it would be sufficient to see the build time after the package has finished building.
> +1. You got my vote. The simpler, the better.
>> Would anyone be opposed to that?
> No. ;-)

I have no problems with that.

Regards,

Adolf.
> Best
> Matthias
>
>

-- 
Sent from my laptop

Re: Unending item build

[Stefan Schantl]

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


Hi @all,

I've also stumbled over this issue from time to time.

So let's give the fix a try.

Best regards,

-Stefan
Am 8. Juni 2026 18:14:30 schrieb Adolf Belka <adolf.belka@ipfire.org>:

> Hi Michael and Matthias,
>
> On 08/06/2026 16:09, Matthias Fischer wrote:
>> On 08.06.2026 16:03, Michael Tremer wrote:
>>> Hello Matthias,
>> Hi Michael,
>>
>>>> On 8 Jun 2026, at 12:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I'd like to warm up an old problem...perhaps I found something like a
>>>> solution.
>>>>
>>>> The original problem is rather old - it dates from 2025-01-15. It still
>>>> can be found here:
>>>> https://marc.info/?l=ipfire-development&m=173691503411708
>>>>
>>>> Once in a while I experienced the same problem like Jon - building
>>>> stopped suddenly: "./make.sh build  goes into a loop and builds an item
>>>> forever." And it doesn't matter which item. Either the counter kept
>>>> running indefinitely, or it stopped displaying anything at all.
>>>>
>>>> That was pretty annoying. No errors, nothing in the logs. After stopping
>>>> the build with CTRL-C and restarting the whole build, usually everything
>>>> ran through and worked again as if nothing had happened.
>>>>
>>>> The last message often was just "make: Leaving directory '/usr/src/lfs'"
>>>> and that was all.
>>>>
>>>> Lastly I was thinking it might have something to do with counters.
>>>> So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.
>>>>
>>>> Since then buildings are running without stopping anymore...
>>>>
>>>> Did anyone had similar problems?
>>> Very rarely. I think I have seen it before, but I cannot reproduce it at all.
>> Yep. It happens just now and then, you never know when and why...
>
> I also very occasionally get the same problem. I have also had it when
> doing a build on the IPFire aarch64 and riscv64 builder.
>>> I am happy to remove the timer entirely because it would be sufficient to 
>>> see the build time after the package has finished building.
>> +1. You got my vote. The simpler, the better.
>>> Would anyone be opposed to that?
>> No. ;-)
>
> I have no problems with that.
>
> Regards,
>
> Adolf.
>> Best
>> Matthias
>
> --
> Sent from my laptop


[-- Attachment #2: Type: text/html, Size: 5302 bytes --]

Re: Unending item build

[Matthias Fischer]

Hi all,

Okay, I got my hopes up too soon — after about ten rounds with 'next'
and several builds the build got stuck again today. This time it stopped
while compiling a firmware update which needs about four seconds. Timer
disappeared and nothing happens...

So my 'sleep 2' fix looked good at first sight, worked for a few days,
but didn't help, sorry.

@Michael:
How do I get rid of this d**** counter the fastest and easiest way...!? ;-)

Best
Matthias

On 08.06.2026 18:55, Stefan Schantl wrote:
> 
> Hi @all,
> 
> I've also stumbled over this issue from time to time.
> 
> So let's give the fix a try.
> 
> Best regards,
> 
> -Stefan
> Am 8. Juni 2026 18:14:30 schrieb Adolf Belka <adolf.belka@ipfire.org>:
> 
>> Hi Michael and Matthias,
>>
>> On 08/06/2026 16:09, Matthias Fischer wrote:
>>> On 08.06.2026 16:03, Michael Tremer wrote:
>>>> Hello Matthias,
>>> Hi Michael,
>>>
>>>>> On 8 Jun 2026, at 12:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I'd like to warm up an old problem...perhaps I found something like a
>>>>> solution.
>>>>>
>>>>> The original problem is rather old - it dates from 2025-01-15. It still
>>>>> can be found here:
>>>>> https://marc.info/?l=ipfire-development&m=173691503411708
>>>>>
>>>>> Once in a while I experienced the same problem like Jon - building
>>>>> stopped suddenly: "./make.sh build  goes into a loop and builds an item
>>>>> forever." And it doesn't matter which item. Either the counter kept
>>>>> running indefinitely, or it stopped displaying anything at all.
>>>>>
>>>>> That was pretty annoying. No errors, nothing in the logs. After stopping
>>>>> the build with CTRL-C and restarting the whole build, usually everything
>>>>> ran through and worked again as if nothing had happened.
>>>>>
>>>>> The last message often was just "make: Leaving directory '/usr/src/lfs'"
>>>>> and that was all.
>>>>>
>>>>> Lastly I was thinking it might have something to do with counters.
>>>>> So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.
>>>>>
>>>>> Since then buildings are running without stopping anymore...
>>>>>
>>>>> Did anyone had similar problems?
>>>> Very rarely. I think I have seen it before, but I cannot reproduce it at all.
>>> Yep. It happens just now and then, you never know when and why...
>>
>> I also very occasionally get the same problem. I have also had it when
>> doing a build on the IPFire aarch64 and riscv64 builder.
>>>> I am happy to remove the timer entirely because it would be sufficient to 
>>>> see the build time after the package has finished building.
>>> +1. You got my vote. The simpler, the better.
>>>> Would anyone be opposed to that?
>>> No. ;-)
>>
>> I have no problems with that.
>>
>> Regards,
>>
>> Adolf.
>>> Best
>>> Matthias
>>
>> --
>> Sent from my laptop
> 
> 

Re: Unending item build

[Michael Tremer]

Hello Matthias,

You can run the build like this: ./make.sh build < /dev/null

The script will then think that it is not talking to a console and just print the default output instead of the timer.

Best,
-Michael

> On 9 Jun 2026, at 18:47, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> Hi all,
> 
> Okay, I got my hopes up too soon — after about ten rounds with 'next'
> and several builds the build got stuck again today. This time it stopped
> while compiling a firmware update which needs about four seconds. Timer
> disappeared and nothing happens...
> 
> So my 'sleep 2' fix looked good at first sight, worked for a few days,
> but didn't help, sorry.
> 
> @Michael:
> How do I get rid of this d**** counter the fastest and easiest way...!? ;-)
> 
> Best
> Matthias
> 
> On 08.06.2026 18:55, Stefan Schantl wrote:
>> 
>> Hi @all,
>> 
>> I've also stumbled over this issue from time to time.
>> 
>> So let's give the fix a try.
>> 
>> Best regards,
>> 
>> -Stefan
>> Am 8. Juni 2026 18:14:30 schrieb Adolf Belka <adolf.belka@ipfire.org>:
>> 
>>> Hi Michael and Matthias,
>>> 
>>> On 08/06/2026 16:09, Matthias Fischer wrote:
>>>> On 08.06.2026 16:03, Michael Tremer wrote:
>>>>> Hello Matthias,
>>>> Hi Michael,
>>>> 
>>>>>> On 8 Jun 2026, at 12:58, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>> I'd like to warm up an old problem...perhaps I found something like a
>>>>>> solution.
>>>>>> 
>>>>>> The original problem is rather old - it dates from 2025-01-15. It still
>>>>>> can be found here:
>>>>>> https://marc.info/?l=ipfire-development&m=173691503411708
>>>>>> 
>>>>>> Once in a while I experienced the same problem like Jon - building
>>>>>> stopped suddenly: "./make.sh build  goes into a loop and builds an item
>>>>>> forever." And it doesn't matter which item. Either the counter kept
>>>>>> running indefinitely, or it stopped displaying anything at all.
>>>>>> 
>>>>>> That was pretty annoying. No errors, nothing in the logs. After stopping
>>>>>> the build with CTRL-C and restarting the whole build, usually everything
>>>>>> ran through and worked again as if nothing had happened.
>>>>>> 
>>>>>> The last message often was just "make: Leaving directory '/usr/src/lfs'"
>>>>>> and that was all.
>>>>>> 
>>>>>> Lastly I was thinking it might have something to do with counters.
>>>>>> So I changed "while sleep 1" to "while sleep 2" in 'make.sh'. Nothing more.
>>>>>> 
>>>>>> Since then buildings are running without stopping anymore...
>>>>>> 
>>>>>> Did anyone had similar problems?
>>>>> Very rarely. I think I have seen it before, but I cannot reproduce it at all.
>>>> Yep. It happens just now and then, you never know when and why...
>>> 
>>> I also very occasionally get the same problem. I have also had it when
>>> doing a build on the IPFire aarch64 and riscv64 builder.
>>>>> I am happy to remove the timer entirely because it would be sufficient to 
>>>>> see the build time after the package has finished building.
>>>> +1. You got my vote. The simpler, the better.
>>>>> Would anyone be opposed to that?
>>>> No. ;-)
>>> 
>>> I have no problems with that.
>>> 
>>> Regards,
>>> 
>>> Adolf.
>>>> Best
>>>> Matthias
>>> 
>>> --
>>> Sent from my laptop
>> 
>> 
> 
> 

How to disable the item timer? (was: Re: Unending item build)

[Matthias Fischer]

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

Hi Michael,

On 09.06.2026 20:24, Michael Tremer wrote:
> You can run the build like this: ./make.sh build < /dev/null
> 
> The script will then think that it is not talking to a console and just print the default output instead of the timer.

This worked for a while - today the system suddenly thinks that it needs
*two* timers - on 'next'. Hm!

One timer is always "0", the other is showing the build time of the
current item. Both are not counting (see screenshot). Besides that, all
is running, but... ;-)

Is there a chance to disable these timers completely? The only one which
I think is useful would be the buildtime of the whole build at the end.
I don't need nothing more...

Best
Matthias

[-- Attachment #2: 2026-06-15 - Timers on Devel 2.jpg --]
[-- Type: image/jpeg, Size: 69699 bytes --]

Re: How to disable the item timer? (was: Re: Unending item build)

[Michael Tremer]

Hello Matthias,

This is very interesting.

I have removed the timer completely from next, so if you are building against next, you shouldn’t run into any problems any more.

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

All the best,
-Michael

> On 15 Jun 2026, at 13:22, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 09.06.2026 20:24, Michael Tremer wrote:
>> You can run the build like this: ./make.sh build < /dev/null
>> 
>> The script will then think that it is not talking to a console and just print the default output instead of the timer.
> 
> This worked for a while - today the system suddenly thinks that it needs
> *two* timers - on 'next'. Hm!
> 
> One timer is always "0", the other is showing the build time of the
> current item. Both are not counting (see screenshot). Besides that, all
> is running, but... ;-)
> 
> Is there a chance to disable these timers completely? The only one which
> I think is useful would be the buildtime of the whole build at the end.
> I don't need nothing more...
> 
> Best
> Matthias
> <2026-06-15 - Timers on Devel 2.jpg>

Re: How to disable the item timer?

[Matthias Fischer]

On 16.06.2026 12:58, Michael Tremer wrote:
> Hello Matthias,
> 
> This is very interesting.
> 
> I have removed the timer completely from next, so if you are building against next, you shouldn’t run into any problems any more.

Great - thanks!

>   https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=31d52aabde211aabb3ce376b87a0b397b3abe270
> 
> All the best,
> -Michael
> 
>> On 15 Jun 2026, at 13:22, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>> 
>> Hi Michael,
>> 
>> On 09.06.2026 20:24, Michael Tremer wrote:
>>> You can run the build like this: ./make.sh build < /dev/null
>>> 
>>> The script will then think that it is not talking to a console and just print the default output instead of the timer.
>> 
>> This worked for a while - today the system suddenly thinks that it needs
>> *two* timers - on 'next'. Hm!
>> 
>> One timer is always "0", the other is showing the build time of the
>> current item. Both are not counting (see screenshot). Besides that, all
>> is running, but... ;-)
>> 
>> Is there a chance to disable these timers completely? The only one which
>> I think is useful would be the buildtime of the whole build at the end.
>> I don't need nothing more...
>> 
>> Best
>> Matthias
>> <2026-06-15 - Timers on Devel 2.jpg>
> 
> 

Re: Unending item build

[Adolf Belka]

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

Hi All,

On 15/01/2025 21:45, jon wrote:
> Michael,
>
> 1st build went through A-OK.
>
> I’ll keep building this way and let you know what happens.
>
I just had my system just freeze at the start of btrfs-progs. I run my build always by first running sudo -s and then doing all the commands as root.

As the OS is Arch Linux it is also up to date. In fact I updated it this morning so it has the latest of everything that Arch Linux have updated.

Regards,

Adolf.


> Jon
>
>
>
>> On Jan 15, 2025, at 10:03 AM, jon <jon.murphy(a)ipfire.org> wrote:
>>
>> Will do!
>>
>>> On Jan 15, 2025, at 9:57 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>>
>>> 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
>>>>
>>>>
>>>>
>>>>
>>>
>>
>> Jon
>>
>>
>> -- 
>> Jon Murphy
>> jon.murphy(a)ipfire.org
>>
>>
>>
>>
>
> Jon
>
>
> -- 
> Jon Murphy
> jon.murphy(a)ipfire.org
>
>
>
>

Re: Unending item build

[Michael Tremer]

[-- 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
> 
> 
> 
> 

Re: Unending item build

[Michael Tremer]

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

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

Re: Unending item build

[Michael Tremer]

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

Hello Jon,

Someone has reported this before, and it seems to be a bug in some versions of bash.

What OS are you running this on? 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
>