Opened 8 years ago

Closed 8 years ago

#1045 closed defect (fixed)

rasnet compilation not working with --enable-strict

Reported by: George Merticariu Owned by: George Merticariu
Priority: major Milestone:
Component: undecided Version: development
Keywords: Cc: Alex Toader, Vlad Zamfir
Complexity: Medium

Description


Change History (6)

comment:1 by Dimitar Misev, 8 years ago

There are ways to selectively ignore the warnings, see the

#pragma GCC diagnostic

in source:qlparser/oql.yy for example (at top and bottom of the code in oql.yy).

Last edited 8 years ago by Dimitar Misev (previous) (diff)

in reply to:  1 comment:2 by George Merticariu, 8 years ago

Replying to dmisev:

There are ways to selectively ignore the warnings, see the

#pragma GCC diagnostic

in source:qlparser/oql.yy for example (at top and bottom of the code in oql.yy).

There is a bug in GCC: ​https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431
The C++ preprocessor is ingnorring pragma commands. Thus, I couldn't find any workaround to ignore the warnings and enable the compilation with —enable-strict.

Any suggestions?

comment:3 by Dimitar Misev, 8 years ago

Are you sure? It seems like it works in oql.yy and elsewhere where there are generated warnings, otherwise the jenkins test would never pass (it uses —enable-strict).

comment:4 by Dimitar Misev, 8 years ago

Cc: Vlad Zamfir added

comment:5 by Dimitar Misev, 8 years ago

Maybe we can reassign to Vlad, he has experience with the warnings :)

comment:6 by Alex Dumitru, 8 years ago

Resolution: → fixed
Status: new → closed

Fixed in the latest patch

Note: See TracTickets for help on using tickets.