Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50481 - [arm-none-eabi-newlib] newlib nano's header files are overwritten by the header files of newlib
Attached to Project:
Community Packages
Opened by Pieter Willemsen (pieter_) - Monday, 22 August 2016, 13:16 GMT
Last edited by Anatol Pomozov (anatolik) - Wednesday, 30 May 2018, 12:33 GMT
Opened by Pieter Willemsen (pieter_) - Monday, 22 August 2016, 13:16 GMT
Last edited by Anatol Pomozov (anatolik) - Wednesday, 30 May 2018, 12:33 GMT
|
DetailsDescription: The package installs both newlib and newlib-nano. The header files of newlib nano are overwritten by the newlib's files during installation
Additional info: * package version: arm-none-eabi-newlib-2.4.0-3 Steps to reproduce: 1. pacman -Sy arm-none-eabi-newlib 2. the file /usr/arm-none-eabi/include/newlib.h is for the normall newlib build. I can't find newlib.h for the nano build |
This task depends upon
Why do you need nano's version of newlib.h? What is your use-case?
For the ubuntu package (https://packages.ubuntu.com/artful/all/libnewlib-arm-none-eabi/filelist), it is located in a separate directory. (/usr/include/newlib/nano/newlib.h vs /usr/include/newlib/newlib.h)
As a temporary fix I added:
install -d "$pkgdir"/usr/$_target/include/newlib-nano
install -m644 -t "$pkgdir"/usr/$_target/include/newlib-nano "$pkgdir"/usr/$_target/include/newlib.h
to the package section of the PKGBUILD just after installing the nano version so the nano newlib.h ends up in include/newlib-nano/. I called it newlib-nano because the nano.specs files have this directory name in it
My use-case for this is in (https://github.com/OTAkeys/RIOT/blob/d05c147c8ab7f12fa0cabf43573948def099168d/sys/newlib_thread_safe/Makefile.include) they are trying to detect if the installed version of newlib nano is compiled with reent small and it is based on the newlib.h header file. The gcc compilation flags are set in (https://github.com/OTAkeys/RIOT/blob/master/makefiles/libc/newlib.mk).
WTR other systems, see Gentoo's ebuild file, for example ( https://gitweb.gentoo.org/repo/gentoo.git/plain/sys-libs/newlib/newlib-2.5.0.ebuild ). They put the nano headers in a separate directory too.
For Fedora it seems to be missing
Thanks very much!