Swatantra-66 opened a new pull request, #21335:
URL: https://github.com/apache/nuttx/pull/21335

   ## Summary
   In `lm3s6965-ek:qemu-protected`, commit d9d9d3fbed dropped the DNS client 
(`CONFIG_NETDB_DNSCLIENT`) to recover kernel flash headroom. However, the DNS 
client was previously the sole selector of `CONFIG_NET_SOCKOPTS` for this board 
configuration.
   
   Because `CONFIG_NETUTILS_DHCPC` selects `CONFIG_NET_BINDTODEVICE`, the 
absence of `CONFIG_NET_SOCKOPTS` caused `s_boundto` to be omitted from `struct 
socket_conn_s` (`include/nuttx/net/net.h`), breaking compilation in 
`net/icmp/icmp_sendmsg.c`, `tcp_finddev.c`, and `udp_finddev.c` during the CI 
`arm-ti` build.
   
   Related to https://github.com/apache/nuttx-apps/pull/3954. While 
`apache/nuttx-apps#3954` attempted to select `NET_SOCKOPTS` from DHCPC, that 
caused defconfig normalization failures on boards where `CONFIG_NET_SOCKOPTS=y` 
was already explicitly set (such as `nucleo-h563zi:netnsh`). 
   
   This patch explicitly re-enables `CONFIG_NET_SOCKOPTS=y` in 
`boards/arm/tiva/lm3s6965-ek/configs/qemu-protected/defconfig`. This solves the 
issue cleanly at the source where `CONFIG_NETDB_DNSCLIENT` was removed, 
provides the required `s_boundto` field, and avoids any normalization side 
effects across other architectures.
   
   ## Impact
   - **Architecture**: ARM Cortex-M3 (TI Stellaris / Tiva `lm3s6965-ek`).
   - **Configuration**: `lm3s6965-ek:qemu-protected`.
   - **User Impact**: Resolves missing `s_boundto` member compilation error 
when building DHCP client with `NET_BINDTODEVICE`. Adds negligible flash 
footprint (~80 bytes), well within the ~2.6 KiB headroom recovered in PR #21320.
   
   ## Testing
   - Inspected defconfig alignment with `tools/savedefconfig`.
   - Verified `CONFIG_NET_SOCKOPTS=y` placement in alphabetical order.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to