emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#46496: closed (newlib-nano doesn't have libc_nano.a )


From: GNU bug Tracking System
Subject: bug#46496: closed (newlib-nano doesn't have libc_nano.a )
Date: Thu, 15 Apr 2021 18:40:01 +0000

Your message dated Thu, 15 Apr 2021 14:39:31 -0400
with message-id 
<BYAPR05MB4023B65678EE49734E449EDCC54D9@BYAPR05MB4023.namprd05.prod.outlook.com>
and subject line Bug closed
has caused the debbugs.gnu.org bug report #46496,
regarding newlib-nano doesn't have libc_nano.a 
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
46496: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46496
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: newlib-nano doesn't have libc_nano.a Date: Sun, 14 Feb 2021 03:11:07 +0800 User-agent: mu4e 1.4.15; emacs 27.1
I can't build ZephyrRTOS with arm-none-eabi-nano-toolchain,
because libc_nano.a is required by ZephyrRTOS when I enabled newlib nano
config.
Then I found there's only libc_nano.a in newlib-nano path, only libc.a.

I think libc.a is for newlib, and libc_nano.a is for newlib-nano.


Best regards.


-- 
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
Fingerprint F53B 4C56 95B5 E4D5 6093 4324 8469 6772 846A 0058

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Bug closed Date: Thu, 15 Apr 2021 14:39:31 -0400 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Icedove/78.9.0
Hello!

Thank you for reporting this bug. This bug was fixed in commit
8799369983315d799501b4f45a3954195b630ebb made on April 8th.

You are correct that libc_nano.a should be for newlib-nano and libc.a
should be for newlib. However, in the nano toolchain, both libc.a and
libc_nano.a (which was recently added) are used for newlib-nano.

In the future, we should combine the nano and non-nano toolchain
together so that it matches up with your (correct) intuition of what
should be where. But that is a job for another day.

Thanks,

Morgan


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]