[Ipopt] status on MPI issue in latest ipopt?

Greg Horn gregmainland at gmail.com
Sat Apr 5 08:45:23 EDT 2014


Hi Stefan,

Thanks for the quick response. Do you have a rough estimate when 3.11.8
might be released?

Thank you,
Greg


On Sat, Apr 5, 2014 at 2:43 PM, Stefan Vigerske <stefan at math.hu-berlin.de>wrote:

> Hi,
>
> it should be fixed in the Ipopt source when we release 3.11.8, but that
> still has to happen.
> The Debian bugtracking talks about some patch, so maybe they will do
> something based on 3.11.7. But I'm not involved in this, so I cannot tell.
>
> Stefan
>
>
> On 04/05/2014 02:24 PM, Greg Horn wrote:
>
>> Hello,
>>
>> Is the bug discussed here
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736842 and here
>> http://list.coin-or.org/pipermail/ipopt/2014-February/003651.htmlsupposed
>> to be resolved? I am still getting the error:
>>
>> *** The MPI_Comm_f2c() function was called before MPI_INIT was invoked.
>> *** This is disallowed by the MPI standard.
>> *** Your MPI job will now abort.
>> [deb-kerman:19011] Local abort before MPI_INIT completed successfully; not
>> able to aggregate error messages, and not able to guarantee that all other
>> processes were killed!
>>
>> I'm using the latest Ipopt in debian unstable: 3.11.7-2
>>
>> Thanks,
>> Greg
>>
>>
>>
>> _______________________________________________
>> Ipopt mailing list
>> Ipopt at list.coin-or.org
>> http://list.coin-or.org/mailman/listinfo/ipopt
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.coin-or.org/pipermail/ipopt/attachments/20140405/6f2959a9/attachment.html>


More information about the Ipopt mailing list