Hello Andrew !
The same problem also was reported before:
https://lists.gnu.org/archive/html/bug-glpk/2019-04/threads.html
I also found this other reported problem/fix on the mailing list that
affects GLPK 4.65 (see bellow).
https://lists.gnu.org/archive/html/bug-glpk/2019-07/msg00000.html
Is the above a valid issue/solution ?
Cheers !
On 14/7/20 12:16, Domingo Alvarez Duarte wrote:
Hello Andrew !
Thank you for reply !
There is an official GLPK repository where we can find all fixes ?
Looking at this pattern in the mailing list I found another one:
====
Date: Thu, 01 Mar 2018 13:06:00 +0300
Subject: Re: [Bug-glpk] glpk prints warnings which lead to failing
sagemath tests
====
To fix the bug please replace lines 923-930 in glpk/src/draft/glpios03.c
#if 1 /* 16/III-2016 */
if (((glp_iocp *)T->parm)->flip)
#if 0 /* 20/I-2018 */
xprintf("WARNING: LONG-STEP DUAL SIMPLEX WILL BE USED\n");
#else
xprintf("Long-step dual simplex will be used\n");
#endif
#endif
with the following ones:
#if 1 /* 01/III-2018 */
if (((glp_iocp *)T->parm)->flip)
if (T->parm->msg_lev >= GLP_MSG_ALL)
xprintf("Long-step dual simplex will be used\n");
#endif
Please note that this change will appear in the next release of glpk.
====
Cheers !
On 14/7/20 12:00, Andrew Makhorin wrote:
On Tue, 2020-07-14 at 11:46 +0200, Domingo Alvarez Duarte wrote:
Hello Andrew !
Looking at your fix suggestion and through the GLPK code it seems
that
all marks like:
=====
//#if 1 /* 14/VII-2020 */
#if 1 /* DD/XXX-DDDD */
...
#endif
=====
Are fixes for problems reported on the mailing list at that specified
date ?
Is this a "definitive fix" or a "temporary fix" ?
It is just a comment to see when and which code fragment was changed.
