Package Details: med-openmpi 4.1.0-2

Git Clone URL: (read-only, click to copy)
Package Base: med-openmpi
Description: Generic pre- and post-processing platform for numerical simulation (openmpi version)
Upstream URL:
Licenses: LGPL
Conflicts: med
Provides: med
Replaces: med
Submitter: mortbauer
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 3
Popularity: 0.000000
First Submitted: 2014-05-06 15:15 (UTC)
Last Updated: 2022-02-25 01:04 (UTC)

Latest Comments

sl1pkn07 commented on 2022-02-25 01:11 (UTC)

Hi. adopted and made a rework. now fixed my problems when build

  • uses gentoo patch
  • enable test (and filter the python ones due a circular dependency probem)
  • use openmpi compilers

i have filled a bug for promote landing in official repos


Nim65s commented on 2021-12-13 08:43 (UTC)


I don't use this package, since med has been moved to community. I resign from its maintainership.

sl1pkn07 commented on 2021-12-12 17:12 (UTC)

[ 13%] Building C object src/hdfi/CMakeFiles/_hdfi.dir/_MEDattributeNumWrByName.c.o
In file included from /usr/include/H5public.h:32,
                 from /usr/include/hdf5.h:22,
                 from /tmp/makepkg/med-openmpi/src/med-4.1.0/include/med.h:22,
                 from /tmp/makepkg/med-openmpi/src/med-4.1.0/src/hdfi/_MEDattributeNumWrByName.c:20:
/tmp/makepkg/med-openmpi/src/med-4.1.0/src/hdfi/_MEDattributeNumWrByName.c: In function '_MEDattributeNumWrByName':
/tmp/makepkg/med-openmpi/src/med-4.1.0/src/hdfi/_MEDattributeNumWrByName.c:71:10: error: too few arguments to function 'H5Oget_info3'
   71 |     if ( H5Oget_info( pid, &_oinfo ) <0) {
      |          ^~~~~~~~~~~
In file included from /usr/include/H5Apublic.h:22,
                 from /usr/include/hdf5.h:23,
                 from /tmp/makepkg/med-openmpi/src/med-4.1.0/include/med.h:22,
                 from /tmp/makepkg/med-openmpi/src/med-4.1.0/src/hdfi/_MEDattributeNumWrByName.c:20:
/usr/include/H5Opublic.h:497:15: note: declared here
  497 | H5_DLL herr_t H5Oget_info3(hid_t loc_id, H5O_info2_t *oinfo, unsigned fields);
      |               ^~~~~~~~~~~~
make[2]: *** [src/hdfi/CMakeFiles/_hdfi.dir/build.make:118: src/hdfi/CMakeFiles/_hdfi.dir/_MEDattributeNumWrByName.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:975: src/hdfi/CMakeFiles/_hdfi.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Rhinoceros commented on 2021-01-02 23:03 (UTC)

Ah that might be it. Thanks @Nim65s!

Nim65s commented on 2021-01-02 09:09 (UTC)

I just upgraded from 4.0.0 to 4.1.0, following community/med. So I guess that fix was upstream :)

Rhinoceros commented on 2021-01-01 23:25 (UTC)

Thanks @frankspace. I just rebuilt to check and this time it created all three files. Previously it just created the other two. Not sure what's going on, but it seems fine now. Sorry for the noise!

frankspace commented on 2021-01-01 17:35 (UTC)

For whatever it's worth, I just compiled the latest version of this (med-openmpi 4.1.0-1), and for me at least, it does actually install /usr/lib/, /usr/lib/, and /usr/lib/

Rhinoceros commented on 2021-01-01 10:18 (UTC)

Yeah apparently not @Nim65s. import Meshpart complained about missing specifically. I can get the precise error message if you want, but I installed med instead, and the absence of that file was one difference I noticed.

Nim65s commented on 2021-01-01 10:08 (UTC)

There is /usr/lib/ and /usr/lib/ Isn't it enough ?

By the way, I handed over the med package to @xyproto so that he could include it in community, so there are no reason for me to keep maintaining med-openmpi. If anybody wants to adopt it, don't hesitate to ask :)

Rhinoceros commented on 2021-01-01 04:39 (UTC)

I had some problems with freecad and this package. med correctly installs /usr/lib/, but this package med-openmpi does not. Without this file, I cannot import MeshPart.

potatoe commented on 2020-08-30 15:50 (UTC)

Is replaces=('med') correct for this package? Or would just conflicts and provides be enough (e.g. this is an alternative and either med or med-openmpi can be chosen but not both together)? My understanding is replaces means the med package is obsolete (and presumably should be removed from AUR now that this exists as a replacement), and the replaces flags is there to ensure everybody is automatically updated to this new replacement package med-openmpi. The wiki describes it as being "An array of obsolete packages that are replaced by the package" and points out pacman "will immediately replace an installed package upon encountering another package with the matching replaces", and suggests using only conflicts and provides if it's just an alternate version.

One of the unofficial user repositories, andontie-aur, includes prebuilt packages for both med and med-openmpi now and as such my pacman wants to automatically replace med with med-openmpi. Is that intended / the correct approach with med-openmpi vs med?

Nim65s commented on 2020-04-28 08:16 (UTC)

Thanks @jedbrown. I applied that to med & med-openmpi.

jedbrown commented on 2020-04-28 05:07 (UTC)

This is currently broken with hdf5-1.12 from community. This gist applies the patch I developed for PETSc, which has been using it for the past several weeks.

Nim65s commented on 2019-08-07 17:58 (UTC)

The code that compiles Python files looks broken (maybe a wrong path is hardcoded somewhere, or we failed at configuring that properly) for me too. I think that it doesn't really matter, as those file will be compiled on the fly by the Python interpreter as soon as they well be needed.

Anyway, I am only using this package as a dependency of freecad, which works equally well with med and med-openmpi… But if someone have an actual issue at runtime, please provide a reproducible way to see that.

valandil commented on 2019-08-07 15:48 (UTC)

I don't have a way to test med-openmpi easily, but I get these errors when trying to package med-openmpi in a clean chroot:

Does the package work for you?

Also, FWIW, I had to build in a clean chroot to sidestep the issue I described in an ealier comment.

Nim65s commented on 2019-08-02 11:11 (UTC)

Fixed, thanks !

valandil commented on 2019-07-29 16:45 (UTC)

FWIW, here's the proposed diff:

diff --git a/PKGBUILD b/PKGBUILD
index 11019b3..08ad911 100644
@@ -15,10 +15,7 @@ url=""
 depends=('hdf5-openmpi' 'tk' 'python')
 makedepends=('gcc-fortran' 'swig' 'openmpi' 'cmake')

@@ -36,6 +33,9 @@ build() {

 package_med-openmpi() {
+  provides=('med')
+  conflicts=('med')
+  replaces=('med')
   cd ${_pkgname}-${pkgver}
   make DESTDIR=${pkgdir} install

valandil commented on 2019-07-29 16:44 (UTC)

The provides, conflicts and replaces variables should be set in the package_med-openmpi() function, not at the top of the PKGBUILD. Otherwise, both packages will inherit these. Only med-openmpi actually provides med, not med-openmpi-docs.

And yes, the patch files to when I was maintainint that package haha. They are definitely old.

I haven't tested my proposed change because I keep getting this compilation error:

[ 41%] Building Fortran object src/CMakeFiles/medfwrap.dir/MEDiteratorsF.f.o

   15 |      &  MED_OCTA12, MED_PYRA13, MED_PENTA15, MED_PENTA18, MED_HEXA20,
      |                                                        1
Error: Symbol ‘med_penta18’ must be a PARAMETER in DATA statement at (1)
make[2]: *** [src/CMakeFiles/medfwrap.dir/build.make:63: src/CMakeFiles/medfwrap.dir/MEDiteratorsF.f.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:167: src/CMakeFiles/medfwrap.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

Nim65s commented on 2019-07-27 10:32 (UTC)

I don't know how to make med-openmpi and med-openmpi-docs not conflict with each other, while still ensure that med conflict with med-openmpi… Does anyone have an idea ?

jedbrown commented on 2019-07-25 21:50 (UTC)

:: med-openmpi-docs and med-openmpi are in conflict (med). Remove med-openmpi? [y/N]

Also, the obsolete patch files can be removed.

valandil commented on 2017-04-03 15:56 (UTC)

I am no longer interested in maintaining this package, since I do not use it anymore. Moreover, it requires the creation of a new package, hdf5_18-openmpi. I will leave this task to the users of this package. Cheers,

valandil commented on 2016-05-08 17:19 (UTC)

Thanks for the fix. I'll try to report this upstream. This needs to patches to compile...

simonp commented on 2016-05-05 14:44 (UTC)

There is a compile error with the current hdf5 version because of a conflicting function signature. Here is a patch:

valandil commented on 2015-04-27 20:43 (UTC)

Go ahead then.

mortbauer commented on 2015-04-27 20:42 (UTC)

well don't worry, I actually do have some time for such stuff now, but if you wan't you can have, I don't really care as long as it works.

valandil commented on 2015-04-27 20:08 (UTC)

Turns out that my earlier request for orphaning the package has been heeded, although a little bit late. If you wish, you can continue maintaining the package. However, if you are too busy, I'll gladly take over.

valandil commented on 2015-04-21 14:44 (UTC)

As long as the code works, it's fine by me. I don't think you added me as a contributor, though ;)

mortbauer commented on 2015-04-18 10:09 (UTC)

Sorry I had a lot to do recently, finishing my studies, so I actually didn't see your modified PKGBUILD, worked perfectly with it. I added you as a contributor (only username) hope that is ok for you. greets martin

valandil commented on 2015-04-15 14:12 (UTC)

Did you use my PKGBUILD along with my patch? This builds for me, with no SWIG errors.

mortbauer commented on 2015-04-15 13:22 (UTC)

sorry, made a quick try now, but the python wrapper fails, will maybe have a look at the weekend

valandil commented on 2015-04-11 00:25 (UTC)

Please update or disown.

valandil commented on 2015-03-05 16:32 (UTC)

This should work.