though I perhaps shouldn’t have to) as I have much more pressing things to work
on – and if I do report an issue on good ol' GitHub I usually get told its down
to my arch!
But I soldier on :)
From: Sebastien Lorquet
Sent: 07 March 2023 09:22
To: dev@nuttx.apache.org
Subject: Re: Nut
the problem is that the new SIGWORK is defined by CONFIG_SIG_WORK to 17
without condition
but SIGCHLD is configured by CONFIG_SIG_CHLD , but this var depends on
SCHED_HAVE_PARENT, this var is not defined in my build and SIGCHLD
defaults to 17 in code.
So something is wrong, SIGCHLD shoud not
Hello
So how do you explain this? I did not touch them either and my last
update is not so old, maybe a few weeks.
make menuconfig and saving again did not help.
make -j1 does not help either, in fact I am never using parallel make.
also omg this silent make is awful, seriously how do you r
Alan,
I am a bit tired of NuttX these last months.
Make is not clean. It is someone's preference that was DISCRETELY pushed
without any community discussion, as always.
All the error output is buffered in memory and kept for the last moment.
What is the way to restore the previous behaviour
Hi Sebastien,
I checked the logs and the lib_strsignal.c is untouched for a long time
I would start debugging with make -j1
Best regards
Alin
-Original Message-
From: Sebastien Lorquet
Sent: den 7 mars 2023 09:26
To: dev@nuttx.apache.org
Subject: NuttX is broken
What is this?
NuttX
Hi Sebastien,
Please read:
https://community.apache.org/contributors/etiquette
BTW, the new building system is strange, but more clean.
I think it should at least give some users feedback, like a text
progress bar, etc.
For course it needs improvement, but you don't need to do this way.
BR,
