It is likely that the issue with the SIGNAL number was introduced by
commit e6227e19433c4999d500437d0a8a5c05f476ceb1
Author: chenrun1 <chenr...@xiaomi.com>
Date: Wed Feb 1 17:17:43 2023 +0800
include/signal.h:Expanding SIGNAL to be consistent with Linux
There is nothing inherently wrong with the commit. However, none of the
default configurations were changed. Since the config->defconfig
compression removes all settings that are left at the default value,
changing the default value of a configuration setting effectively
changes the value used by the configuration.
When the default value of a configuration setting changes in a Kconfig,
NuttX uses should get some kind of heads up in the dev list so that they
can all fix their local configurations as well.
