March 16
On 2020-03-15 23:40, Peter Jacobs wrote:

> Tried the most recent dstep but was unsuccessful...
> $ ../dstep/bin/dstep /usr/include/mpi/mpi.h -o mpi.d
> /usr/include/mpi/mpi.h:351:8: warning: a type renamed to 'ompi_status_public_t_' due to the collision with the symbol declared in /usr/include/mpi/mpi.h:364:37
> dstep: an unknown error occurred: core.exception.AssertError@dstep/translator/Type.d(32): Assertion failure
> ----------------
> ??:? _d_assertp [0x5625185d8659]
> dstep/translator/Type.d:32 dstep.translator.Output.SourceNode dstep.translator.Type.translateType(dstep.translator.Context.Context, clang.Cursor.Cursor, clang.Type.Type, bool, bool) [0x5625185c1941]
> --- snip ---
> clang/Visitor.d:66 extern (C) clang.c.Index.CXChildVisitResult clang.Visitor.Visitor.visitorFunction(clang.c.Index.CXCursor, clang.c.Index.CXCursor, void*) [0x562518562feb]
> ??:? [0x7f7d196f7bff]

Please report an issue here [1]. Seems to be similar to this issue [2]


/Jacob Carlborg
March 22
On Monday, 16 March 2020 at 10:40:09 UTC, Peter Jacobs wrote:
> On Monday, 16 March 2020 at 01:12:42 UTC, bachmeier wrote:
>> On Friday, 13 March 2020 at 08:08:17 UTC, Peter Jacobs wrote:
>>> Given the recent thread that mentioned dpp for generating an interface module for a C library, I thought that I would give it a go on the openmpi headers.
>>> Thoughts or suggestions on how to proceed?
> --- snip ---
>> Have you seen this project?
>> As I think about this, OpenMPI is probably one of the most difficult libraries to deal with. It's such a complicated beast to build that you're supposed to use their wrapper compiler.
> Yes, indeed, we use that OpenMPI wrapper, actually the version at which has been maintained by John Colvin.

Just to let interested parties know... I went with updating the interface in this project.  It turned out to be a reasonably direct transcription of the MPI header into a D module.  Now, it works for a range of modern openmpi versions.

Next ›   Last »
1 2