> Perhaps not a bug, but the following constatnts are defined twice to the
> same values in glplpx.h with annoying consequences when I try to bind to
> ruby.
> 
> [EMAIL PROTECTED] ruby]$ ruby sample.rb 
> ./nigelzGLPK.so: warning: already initialized constant LPX_FR
> ./nigelzGLPK.so: warning: already initialized constant LPX_LO
> ./nigelzGLPK.so: warning: already initialized constant LPX_UP
> ./nigelzGLPK.so: warning: already initialized constant LPX_DB
> ./nigelzGLPK.so: warning: already initialized constant LPX_FX
> ./nigelzGLPK.so: warning: already initialized constant LPX_BS
> ./nigelzGLPK.so: warning: already initialized constant LPX_NL
> ./nigelzGLPK.so: warning: already initialized constant LPX_NU
> ./nigelzGLPK.so: warning: already initialized constant LPX_NF
> ./nigelzGLPK.so: warning: already initialized constant LPX_NS
> *     0:   objval =   0.000000000e+00   infeas =   0.000000000e+00 (0)
> *     2:   objval =   7.333333333e+02   infeas =   0.000000000e+00 (0)
> OPTIMAL SOLUTION FOUND

Thank you for your report. However, I do not completely understand
the situation, because those are preprocessor variables which exist
only during compilation. I think there must be a way to disable such
warning messages.



_______________________________________________
Bug-glpk mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-glpk

Reply via email to