[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#47325: newlib-nano: are lib names wrong?
From: |
Morgan Smith |
Subject: |
bug#47325: newlib-nano: are lib names wrong? |
Date: |
Fri, 26 Mar 2021 16:42:40 -0400 |
Hello Nicolò,
This is definitely a bug that I encountered today. I'm convinced it's a
bug because I came across this page that says so:
https://newlib.sourceware.narkive.com/kfT8XDEe/building-libc-nano-and-libg-nano
The git repo it links to has the following shell function. I think we
should emulate its behavior.
(On a slightly unrelated note, can someone PLEASE accept my patch in bug
44750 for a different arm-none-eabi issue. It's desperately needed.)
copyNanoLibraries() {
(
source="${1}"
destination="${2}"
messageA "\"nano\" libraries copy"
multilibs=$("${destination}/bin/${target}-gcc" -print-multi-lib)
sourcePrefix="${source}/${target}/lib"
destinationPrefix="${destination}/${target}/lib"
for multilib in ${multilibs}; do
multilib="${multilib%%;*}"
sourceDirectory="${sourcePrefix}/${multilib}"
destinationDirectory="${destinationPrefix}/${multilib}"
mkdir -p "${destinationDirectory}"
cp "${sourceDirectory}/libc.a"
"${destinationDirectory}/libc_nano.a"
cp "${sourceDirectory}/libg.a"
"${destinationDirectory}/libg_nano.a"
cp "${sourceDirectory}/librdimon.a"
"${destinationDirectory}/librdimon_nano.a"
cp "${sourceDirectory}/libstdc++.a"
"${destinationDirectory}/libstdc++_nano.a"
cp "${sourceDirectory}/libsupc++.a"
"${destinationDirectory}/libsupc++_nano.a"
done
mkdir -p "${destination}/${target}/include/newlib-nano"
cp "${source}/${target}/include/newlib.h"
"${destination}/${target}/include/newlib-nano"
if [ "${keepBuildFolders}" = "n" ]; then
messageB "\"nano\" libraries remove install folder"
maybeDelete "${top}/${buildNative}/${nanoLibraries}"
fi
)
}