Summary: | sys-cluster/mpi-dotnet fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Matti Bickel (RETIRED) <mabi> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | hp-cluster |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 281207 | ||
Attachments: |
Build log
Unsafe.pl fix Best known fix so far |
Description
Diego Elio Pettenò (RETIRED)
2010-01-01 15:54:12 UTC
Created attachment 214833 [details]
Build log
Created attachment 220975 [details, diff]
Unsafe.pl fix
Thanks for the report and sorry for taking so long to respond.
The attached patch fixes the reported problem. However, mpi-dotnet still fails to build on my box. I will investigate this further in the coming days.
Created attachment 221225 [details, diff]
Best known fix so far
I fixed some more errors that came from LAM-MPI declaring extra constants in mpi.h.
After getting CustomUnsafe.cs to compile, I bumped into lam-mpi not supporting MPI_SIGNED_CHAR, which is required by mpi-dotnet (and by the mpi2 standard, btw). :-/
As I have no intention on being upstream for mpi-dotnet, i will just exclude lam-mpi from the list of choices you can run mpi-dotnet with.
I guess UPSTREAM is appropiate here, as this is a lam-mpi/mpi-dotnet interopability issues. Both upstreams appear to be dead/in maintainance mode, so you could read this as a WONTFIX. |