From: Efraim Flashner <efraim@flashner.co.il>
To: Morgan.J.Smith@outlook.com
Cc: 47325-done@debbugs.gnu.org, anothersms@gmail.com
Subject: bug#47325: [PATCH] gnu: newlib-nano: Fix nano lib and header paths
Date: Mon, 12 Apr 2021 11:25:06 +0300 [thread overview]
Message-ID: <YHQD4sNsSsKumMU/@3900XT> (raw)
In-Reply-To: <BYAPR05MB4023C6AEC80E53FED3A4C55FC5749@BYAPR05MB4023.namprd05.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
On Thu, Apr 08, 2021 at 09:02:20AM -0400, Morgan.J.Smith@outlook.com wrote:
> From: Morgan Smith <Morgan.J.Smith@outlook.com>
>
> * gnu/packages/embedded.scm (newlib-nano-arm-none-eabi)[arguments]: Hard link
> library files from *.a to *_nano.a. Hard link newlib.h to a common location.
> ---
>
> I CC'd Efraim because they commited my last gcc-arm-none-eabi patch. I hope
> that's ok. I'm not really sure who is responsible for this toolchain.
>
> I successfully compiled some QMK firmware using this patch, something that
> failed previously.
>
No one is really in charge of the cross toolchains, it's more of when it
becomes relevant to someone and it's time to fix something.
It looks good to me, I made a small change, changing link to symlink and
made the link relative. I thought about factoring out 'lib' or '.a' from
the find-files but ultimately decided against it, I think it's probably
easier to read as-is.
Patch pushed! Feel free to tag me on other ones like this too.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-04-13 11:37 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YHQD4sNsSsKumMU/@3900XT \
--to=efraim@flashner.co.il \
--cc=47325-done@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.