On Oct 31, 2013, at 11:40 PM, Gurjot Singh wrote: > When I run 'make' command it gives me the following error: > > [ 13%] Building C object src/libbn/CMakeFiles/libbn.dir/obr.c.o > /home/scott/brlcad/src/libbn/obr.c: In function ‘bn_obr’: > /home/scott/brlcad/src/libbn/obr.c:581:28: error: variable ‘dmax2’ set > but not used [-Werror=unused-but-set-variable] > /home/scott/brlcad/src/libbn/obr.c:567:9: error: variable ‘dim’ set > but not used [-Werror=unused-but-set-variable] > cc1: all warnings being treated as errors > make[2]: *** [src/libbn/CMakeFiles/libbn.dir/obr.c.o] Error 1 > make[1]: *** [src/libbn/CMakeFiles/libbn.dir/all] Error 2 > make: *** [all] Error 2 > > How would this be resolved?
If you have coding experience, you should not shy away from reading and understanding that output. The information is right there rather plainly in the output: "variable X is set but not used" and "all warnings being treated as errors". It says there is a variable. It's in the obr.c file. It's getting set to some value apparently, but that variable is then not being used. If it's not used, why did we bother setting it? So a warning is getting issued by the compiler. The current mode of compilation turns all warnings into errors. Compilation stops. The error is resolved by 1) removing the unused variable(s), 2) using the variable(s), or 3) don't treat warnings as errors. Since you had to ask this question, I presume #3 is most suitable to your situation. The INSTALL file says the BRLCAD_ENABLE_STRICT option controls that mode of compilation, so you can run cmake with the -DBRLCAD_ENABLE_STRICT=NO argument and then rerun make. Alternatively, just wait and try again later because you're apparently compiling our trunk sources, which rapidly change throughout the day. Compilation of trunk is not guaranteed. If you want a more stable compilation, try the STABLE branch or a source release instead. Sean ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
