Where to Set Global Flag -std=gnu++11
Posted: Thu Jun 14, 2018 11:39 pm
Hi,
I am struggling with resolving the __off64_t error reported in the build log below.
My workspace contains three projects. Two create DLLs, they're written in C, and they compile and build fine. The third project is a GUI written in C++ with g++ for a compiler/linker in CodeLite v12.0.3. The GUI is composed of 12 classes; six of them build a page. Of the four classes that report this error: one does not build a page and the other three do build pages. I have compared the *.h and *.cpp files of the three classes that error out with one of the classes that builds a page but does not throw the error. I see differences, of course, but I can't find any issue common to all three that would suggest where the error is coming from.
There are a number of web sites that report different methods of getting rid of that error. On https://github.com/CleverRaven/Cataclys ... ssues/8201, people advised each other to edit the standard C files, which I have not done because it seemed like a bad idea. One writer said renaming the flag fixed some errors but caused more new ones. And anyway, this post went up in 2014, four years ago, so you'd think the problem should have been addressed by now.
On https://sourceforge.net/p/mingw/bugs/2024/, which is 2 years old, Keith Marshall said it was a known bug in the headers but it is fixed now. Not helpful.
On https://stackoverflow.com/questions/226 ... me-off64-t, which is 4 years old, some people post suggestions about editing the header file or changing compiler options. But they're working on Ubuntu. I don't know if those suggestions would fix my problem, and frankly, I am learning to be wary about trying something new that will be tricky to undo if it fails.
Anyway, I am still lost.
I would like to try the solution reported at the bottom of this page: https://groups.google.com/forum/#!topic ... v92_hQi7o8
He says he added the flag -std=gnu++11 to his project, and the error went away.
My question for here is: in CodeLite, where do I put that flag?
Thanks.
Colleen
I am struggling with resolving the __off64_t error reported in the build log below.
My workspace contains three projects. Two create DLLs, they're written in C, and they compile and build fine. The third project is a GUI written in C++ with g++ for a compiler/linker in CodeLite v12.0.3. The GUI is composed of 12 classes; six of them build a page. Of the four classes that report this error: one does not build a page and the other three do build pages. I have compared the *.h and *.cpp files of the three classes that error out with one of the classes that builds a page but does not throw the error. I see differences, of course, but I can't find any issue common to all three that would suggest where the error is coming from.
There are a number of web sites that report different methods of getting rid of that error. On https://github.com/CleverRaven/Cataclys ... ssues/8201, people advised each other to edit the standard C files, which I have not done because it seemed like a bad idea. One writer said renaming the flag fixed some errors but caused more new ones. And anyway, this post went up in 2014, four years ago, so you'd think the problem should have been addressed by now.
On https://sourceforge.net/p/mingw/bugs/2024/, which is 2 years old, Keith Marshall said it was a known bug in the headers but it is fixed now. Not helpful.
On https://stackoverflow.com/questions/226 ... me-off64-t, which is 4 years old, some people post suggestions about editing the header file or changing compiler options. But they're working on Ubuntu. I don't know if those suggestions would fix my problem, and frankly, I am learning to be wary about trying something new that will be tricky to undo if it fails.
Anyway, I am still lost.
I would like to try the solution reported at the bottom of this page: https://groups.google.com/forum/#!topic ... v92_hQi7o8
He says he added the flag -std=gnu++11 to his project, and the error went away.
My question for here is: in CodeLite, where do I put that flag?
Thanks.
Colleen