#1045 closed defect (fixed)

rasnet compilation not working with --enable-strict

Reported by: gmerticariu Owned by: gmerticariu
Priority: major Milestone:
Component: undecided Version: development
Keywords: Cc: atoader, vzamfir
Complexity: Medium

Description


Change History (6)

comment:1 follow-up: Changed 17 months ago by 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).

Last edited 17 months ago by dmisev (previous) (diff)

comment:2 in reply to: ↑ 1 Changed 17 months ago by gmerticariu

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 Changed 17 months ago by dmisev

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 Changed 17 months ago by dmisev

  • Cc vzamfir added

comment:5 Changed 17 months ago by dmisev

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

comment:6 Changed 16 months ago by mdumitru

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in the latest patch

Note: See TracTickets for help on using tickets.