Hello - not relevant now but for reference, AVR seems to be OK (tested
nsh and custom stress app communicating through serial port - simple
tests, found no issues.)
$ tools/configure.sh -l breadxavr:nsh
$ make -j16
Memory region Used Size Region Size %age Used
flash: 47389 B 128 KB 36.15%
sram: 980 B 16 KB 5.98%
eeprom: 0 GB 512 B 0.00%
rodata: 558 B 4 KB 13.62%
(Haven't been able to get free to work in NSH.)
$ avr-gcc -v
Using built-in specs.
Reading specs from /usr/lib/gcc/avr/5.4.0/device-specs/specs-avr2
COLLECT_GCC=avr-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/avr/5.4.0/lto-wrapper
Target: avr
Configured with: ../gcc/configure -v --enable-languages=c,c++
--prefix=/usr/lib --infodir=/usr/share/info --mandir=/usr/share/man
--bindir=/usr/bin --libexecdir=/usr/lib --libdir=/usr/lib
--enable-shared --with-system-zlib --enable-long-long --enable-nls
--without-included-gettext --disable-libssp --disable-libcc1
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=avr ASFLAGS=
CFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong -Wformat ' CPPFLAGS='-Wdate-time
-D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong -Wformat ' DFLAGS=-frelease FCFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong' FFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong' GCJFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong' LDFLAGS=-Wl,-z,relro OBJCFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong -Wformat ' OBJCXXFLAGS='-g -O2
-ffile-prefix-map=/build/gcc-avr-Theg5v/gcc-avr-5.4.0+Atmel3.6.2=.
-fstack-protector-strong -Wformat '
Thread model: single
gcc version 5.4.0 (GCC)
On 2025-09-28 19:13, Alin Jerpelea wrote:
Hello all,
Apache NuttX 12.11.0 RC0 has been staged under [1] and it's
time to vote on accepting it for release. Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
required to pass.
The Apache requirements for approving a release can be found here [3]
"Before voting +1 PMC members are required to download the signed
source code package, compile it as provided, and test the resulting
executable on their own platform, along with also verifying that the
package meets the requirements of the ASF policy on releases."
A document to walk through some of this process has been published on
our project wiki and can be found here [4].
[ ] +1 accept (indicate what you validated - e.g. performed the non-RM
items in [4])
[ ] -1 reject (explanation required)
Thank you all,
Alin Jerpelea
SCM Information:
Release tag: nuttx-12.11.0-RC0
Hash for the release nuttx tag:
fccf2f6e0675b3c01f79d69bbb29f93abff389e7
Hash for the release nuttx-apps tag:
61e82925dc8dd8e9cb9544ef8b0b0f218a6d68c7
[1] https://dist.apache.org/repos/dist/dev/nuttx/12.11.0-RC0/
[2]
https://raw.githubusercontent.com/apache/nuttx/nuttx-12.11.0-RC0/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
