Re: Compiler error with U_FORTIFY_SOURCE, D_FORTIFY_SOURCE options

2018-05-25 Thread Christian Mauderer
Am 25.05.2018 um 17:14 schrieb Joel Sherrill: > > > On Fri, May 25, 2018 at 10:09 AM, Amaan Cheval > wrote: > > Hi! > > I don't know the specifics of the thing you're talking about here, > so others should definitely weigh in

Re: Compiler error with U_FORTIFY_SOURCE, D_FORTIFY_SOURCE options

2018-05-25 Thread Joel Sherrill
On Fri, May 25, 2018 at 10:09 AM, Amaan Cheval wrote: > Hi! > > I don't know the specifics of the thing you're talking about here, so > others should definitely weigh in on that if they can, but regarding the > header file; the include syntax used (, as opposed to

Re: Compiler error with U_FORTIFY_SOURCE, D_FORTIFY_SOURCE options

2018-05-25 Thread Amaan Cheval
Hi! I don't know the specifics of the thing you're talking about here, so others should definitely weigh in on that if they can, but regarding the header file; the include syntax used (, as opposed to "ssp.h") is the one used for system header files (for eg. vs "my_header.h"). I see 2

Compiler error with U_FORTIFY_SOURCE, D_FORTIFY_SOURCE options

2018-05-25 Thread Udit agarwal
Hi all, While cross-compiling fio for RTEMS, by default in the compiler call > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 options are used which raises the following error: > /home/uka_in/development/benchmark/sandbox/5/lib/gcc/arm-rtems5/7.3.0/include/ssp/unistd.h:38:10: > fatal error: ssp.h: No