This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Error Building Newlib for arm-none-eabi


On Thu, Feb 22, 2018 at 12:13 PM, Jim Wilson <jimw@sifive.com> wrote:
> On 02/22/2018 05:55 AM, R0b0t1 wrote:
>>
>> The gets definition looks as if it is replaced with the
>> _FORTIFY_SOURCE expansion. Manually setting _FORTIFY_SOURCE=0 seems to
>> compile the file.
>
>
> Check for environment variables that you might have set and forgotten about.
> An environment variable set for native gcc may also be used for cross gcc.
>

I think it is an option embedded in the toolchain.

> Check the .i file for accidental uses of /usr/include.  There might be a
> problem with your arm cross compiler using /usr/include when it shouldn't.
> You can also see the header file search dirs by adding -v to the compiler
> command.
>

No accidental use of out of tree includes.

> You might try using someone else's build scripts that are known to work, for
> instance crosstools-NG.
>
> Jim

I did try Freddie Choppin's bleeding-edge-toolchain, but have only
been able to test on an Ubuntu host. It has been hard to find a way to
verify the authenticity of the downloads. My commands are modeled
after his, when appropriate. There is also a method of building the
libraries in-tree that I need to investigate, it seems better
supported, though harder to integrate with some package managers.

In any case, I am now hitting issues with GCC (missing stdint.h), so
hopefully I get a response w.r.t. soon.

Cheers,
     R0b0t1


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]