From: Morgan Smith <Morgan.J.Smith@outlook.com>
To: anothersms@gmail.com
Cc: 47325@debbugs.gnu.org
Subject: bug#47325: newlib-nano: are lib names wrong?
Date: Fri, 26 Mar 2021 16:42:40 -0400 [thread overview]
Message-ID: <BYAPR05MB4023B25E292BDD8826C59967C5619@BYAPR05MB4023.namprd05.prod.outlook.com> (raw)
In-Reply-To: <87ft0nnm7r.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
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
)
}
next prev parent reply other threads:[~2021-03-26 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 17:15 bug#47325: newlib-nano: are lib names wrong? Nicolò Balzarotti
2021-03-26 20:42 ` Morgan Smith [this message]
2021-04-08 13:02 ` bug#47325: [PATCH] gnu: newlib-nano: Fix nano lib and header paths Morgan.J.Smith
2021-04-12 8:25 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR05MB4023B25E292BDD8826C59967C5619@BYAPR05MB4023.namprd05.prod.outlook.com \
--to=morgan.j.smith@outlook.com \
--cc=47325@debbugs.gnu.org \
--cc=anothersms@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).