Re: Identified critical bug that breaks configure.sh

2025-02-01 Thread Tomek CEDRO
On Fri, Jan 31, 2025 at 5:26 PM Sebastien Lorquet wrote: > Dont loose too many time, reversing the commit already fixed the problem. > Or I'll charge you my own time :) > I think the two cancel anyway :) > It's a stm32f429 cpu, so you have all the stm32 "common" board stuff > inbetween. > host is

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Sebastien Lorquet
Dont loose too many time, reversing the commit already fixed the problem. Or I'll charge you my own time :) I think the two cancel anyway :) It's a stm32f429 cpu, so you have all the stm32 "common" board stuff inbetween. host is debian 12 or wsl. the problem happen just when running configu

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Tomek CEDRO
Sebastien, please provide details on build configuration / how to reproduce, we cannot reproduce the problem. I think I will charge you hourly rate for playing the "deaf phone" as your secretary :D :D @cederom which defconfig is used? I try the master branch sim:nsh with sed 4.9 without problem:

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Tomek CEDRO
On Fri, Jan 31, 2025 at 3:10 PM Sebastien Lorquet wrote: > Hi, > On 31/01/2025 15:07, Tomek CEDRO wrote: > > On Fri, Jan 31, 2025 at 2:54 PM Sebastien Lorquet > > wrote: > >> On 31/01/2025 13:56, Tomek CEDRO wrote: > >>> Can you please report that Issue on GitHub? 🙂 > >> I dont have github accoun

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Sebastien Lorquet
Hi, On 31/01/2025 15:07, Tomek CEDRO wrote: On Fri, Jan 31, 2025 at 2:54 PM Sebastien Lorquet wrote: On 31/01/2025 13:56, Tomek CEDRO wrote: Can you please report that Issue on GitHub? 🙂 I dont have github accounts anymore. The mentioned commit was part of PR https://github.com/apache/nuttx/

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Tomek CEDRO
On Fri, Jan 31, 2025 at 2:54 PM Sebastien Lorquet wrote: > On 31/01/2025 13:56, Tomek CEDRO wrote: > > Can you please report that Issue on GitHub? 🙂 > > I dont have github accounts anymore. The mentioned commit was part of PR https://github.com/apache/nuttx/pull/14552/files It changes tools/proc

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Sebastien Lorquet
On 31/01/2025 13:56, Tomek CEDRO wrote: Can you please report that Issue on GitHub? 🙂 I dont have github accounts anymore. It's a custom board, we're not shipping devboards in industrial access control. Sebastien

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Tomek CEDRO
On Fri, Jan 31, 2025 at 1:45 PM Sebastien Lorquet wrote: > I have the default sed from debian 12 > > slo@slolin:~/Sources/product-env/nuttx$ LANG=C sed --version > sed (GNU sed) 4.9 > Packaged by Debian > Copyright (C) 2022 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or late

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Sebastien Lorquet
Why, why should we suffer for trivial bugs like that? Life is hard enough. I have the default sed from debian 12 slo@slolin:~/Sources/product-env/nuttx$ LANG=C sed --version sed (GNU sed) 4.9 Packaged by Debian Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 o

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Tomek CEDRO
I have this problem on BSD too and need to replace with gsed (GNU Sed variant). Would be nice to fix :-) Tomek On Fri, Jan 31, 2025 at 11:30 AM Sebastien Lorquet wrote: > > After git bisect over more than 2000 revisions, I found that this commit > broke configure.sh for my board > > > slo@slolin:

Re: Identified critical bug that breaks configure.sh

2025-01-31 Thread Sebastien Lorquet
Reverting this does not seem to be a problem at all and fixes my problem. Why was this added in the first place? Maybe it increased some developer metric to show how productive they are. We'll never know. Sebastien On 31/01/2025 11:29, Sebastien Lorquet wrote: After git bisect over more than