First stab at multilib/uClibc.

Create a separate 'libc_backend_once', install headers into a
subdirectory (different sets of headers are installed for 32- and 64-bit
architectures), and create a symlink for the dynamic linker location
expected by GCC.

Signed-off-by: Alexey Neyman <stilor@att.net>

1 files changed, 23 insertions, 1 deletions

diff --git a/scripts/build/arch.sh b/scripts/build/arch.sh
index 6414b54a..b75c1bed 100644
--- a/scripts/build/arch.sh
+++ b/scripts/build/arch.sh
@@ -29,11 +29,33 @@ CT_DoArchUClibcSelectArch() {
 }
 
 # uClibc: Adjust configuration file according to the CT-NG configuration
-# Usage CT_DoArchUClibcConfig <config-file>
+# Usage: CT_DoArchUClibcConfig <config-file>
 CT_DoArchUClibcConfig() {
     CT_DoLog WARN "Support for '${CT_ARCH}' is not implemented in uClibc config tweaker."
     CT_DoLog WARN "Exact configuration file must be provided."
 }
 
+# Multilib/uClibc: Adjust configuration file for given CFLAGS
+# Usage: CT_DoArchUClibcCflags <config-file> <cflags>
+CT_DoArchUClibcCflags() {
+    local cfg="${1}"
+    local cflags="${2}"
+
+    # Likely, any non-default cflags need to be reflected into the config.
+    # It may work if we just pass them into EXTRA_CFLAGS, but we have no
+    # idea as they might interact with the CFLAGS inferred by uClibc from
+    # the configuration file.
+    if [ "${cflags}" != "" ]; then
+        CT_DoLog WARN "Multilib configuration not supported for uClibc/${CT_ARCH}"
+    fi
+}
+
+# Multilib/uClibc: Adjust header installation path for given CFLAGS
+# Usage: CT_DoArchUClibcHeaderDir <path-variable> <cflags>
+CT_DoArchUClibcHeaderDir() {
+    # Only needed if a given architecture may select different uClibc architectures.
+    :;
+}
+
 # Override from the actual arch implementation as needed.
 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"