This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
RE: FW: checking whether <arm-none-eabi-gcc accepts> -g... <no>
- From: "Kleiber Tamas (BCDS/ENG2)" <Tamas dot Kleiber at bosch-connectivity dot com>
- To: Sebastian Huber <sebastian dot huber at embedded-brains dot de>, "newlib at sourceware dot org" <newlib at sourceware dot org>
- Date: Fri, 5 Dec 2014 07:33:00 +0000
- Subject: RE: FW: checking whether <arm-none-eabi-gcc accepts> -g... <no>
- Authentication-results: sourceware.org; auth=none
- References: <fe7ec752437a424eb680254b08c247c4 at FE-MBX1020 dot de dot bosch dot com> <547EE679 dot 70403 at op dot pl> <547EE901 dot 7050004 at embedded-brains dot de> <9c3c4b9e2a8245d49da4c6394e2c4376 at FE-MBX1020 dot de dot bosch dot com> <548035ED dot 7090004 at embedded-brains dot de> <0632a451686749a7bb621de7b14be183 at FE-MBX1020 dot de dot bosch dot com> <54805B34 dot 6090403 at embedded-brains dot de> <49ac9f0dce8c4a0e8e6b9e99eba5f043 at FE-MBX1020 dot de dot bosch dot com> <548151BA dot 3070009 at embedded-brains dot de>
> On 04/12/14 17:17, Kleiber Tamas (BCDS/ENG2) wrote:
>> Any ideas why could this be happening?
>
> Do you build Newlib as a standalone package? I always build GCC and Newlib in one rush.
I am building as standalone package, directly configuring newlib via the top level configure file as it was described in newlib's README files and I disable newlib supplied syscalls so only libm and libc are built. Based on your question now I assume I am doing something uncommon regardless of the build process described in the README files.
Mit freundlichen Grüßen / Best regards
Tamas Kleiber
_