Compilation error on module_run.c with Ubuntu 16.04.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, ubuntu
- Domain
- build-system, operating-systems
Research direction
Start by reproducing the build from the repository Makefile on Ubuntu 16.04 and inspect module_run.c around process_control_event, especially line 277. Review the OpenFlow headers in use and utils.h for the reported warnings; done means the project builds successfully without the reported compilation failure.
Written by the indexing model from the issue text.
Description
The error is as follows:
module_run.c: In function ‘process_control_event’:
module_run.c:277:20: error: ‘OFPT_STATS_REPLY’ undeclared (first use in this function)
if(ofph->type > OFPT_STATS_REPLY) // FIXME: update for new openflow versions
^
module_run.c:277:20: note: each undeclared identifier is reported only once for each function it appears in
module_run.c:279:24: warning: format ‘%zd’ expects argument of type ‘signed size_t’, but argument 4 has type ‘int’ [-Wformat=]
fprintf(stderr, "%s:%zd :: Data buffer probably trashed : unknown openflow type %d\n",
^
In file included from module_run.c:20:0:
module_run.c: At top level:
utils.h:34:12: warning: inline function ‘time_diff’ declared but never defined
inline int time_diff(struct timeval now, struct timeval *then);
^
Makefile:605: recipe for target 'module_run.o' failed
make[2]: ** [module_run.o] Error 1
make[2]: Leaving directory '/home/mininet/oflops'
Makefile:641: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/mininet/oflops'
Makefile:433: recipe for target 'all' failed
make: *** [all] Error 2
Let me know if you need any further information to trace the error
- Dominant language
- C
- Stars
- 32
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mininet/oflops
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
cbench opendaylightOpen
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
DaveGamble/cJSON#1094 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Status: Opened
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Issue-Bug Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day