[Buildroot] [git commit] Revert "configs/stm32f769_disco_sd: fix boot failure after uClibc bump"

Fiona Klute via buildroot <[email protected]>
Newsgroups net.busybox.buildroot
Message-ID <[email protected]>
commit: https://gitlab.com/buildroot.org/buildroot/-/commit/c784c1fadb54f16f0f8655362694456fe89f9f5f
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master

This reverts commit dd67de1bd3374a75ab1845ef29e3ad3c3bed2aac.

The MALLOC_SIMPLE workaround is no longer needed: the root cause, a
zero _dl_pagesize on noMMU/FLAT targets, is fixed by commit
35d3927e8564 ("package/uclibc: fix for noMMU targets using FLAT
binaries").

Signed-off-by: Dario Binacchi <[email protected]>
Signed-off-by: Fiona Klute <[email protected]>
---
 board/stmicroelectronics/stm32f769-disco/uclibc-fragment.config | 2 --
 configs/stm32f769_disco_sd_defconfig                            | 1 -
 2 files changed, 3 deletions(-)

diff --git a/board/stmicroelectronics/stm32f769-disco/uclibc-fragment.config b/board/stmicroelectronics/stm32f769-disco/uclibc-fragment.config
deleted file mode 100644
index fb8fa9ee01..0000000000
--- a/board/stmicroelectronics/stm32f769-disco/uclibc-fragment.config
+++ /dev/null
@@ -1,2 +0,0 @@
-# MALLOC is not set
-MALLOC_SIMPLE=y
diff --git a/configs/stm32f769_disco_sd_defconfig b/configs/stm32f769_disco_sd_defconfig
index 602d3e8018..a025bd7802 100644
--- a/configs/stm32f769_disco_sd_defconfig
+++ b/configs/stm32f769_disco_sd_defconfig
@@ -1,7 +1,6 @@
 BR2_arm=y
 BR2_cortex_m7=y
 BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_15=y
-BR2_UCLIBC_CONFIG_FRAGMENT_FILES="board/stmicroelectronics/stm32f769-disco/uclibc-fragment.config"
 BR2_GLOBAL_PATCH_DIR="board/stmicroelectronics/stm32f769-disco/patches"
 BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
 BR2_ROOTFS_POST_BUILD_SCRIPT="board/stmicroelectronics/stm32f769-disco/post-build.sh"
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.