Package Details: med 3.1.0-3

Git Clone URL: https://aur.archlinux.org/med.git (read-only)
Package Base: med
Description: MED stands for Modelisation et Echanges de Donnees, i.e. Data Modelization and Exchanges - MED is code-aster exchange module linked to hdf5
Upstream URL: http://www.code-aster.org/outils/med/
Licenses: LGPL
Conflicts: med_fichier
Replaces: med_fichier
Submitter: None
Maintainer: deezy
Last Packager: deezy
Votes: 25
Popularity: 0.986148
First Submitted: 2007-09-25 18:28
Last Updated: 2016-05-19 13:45

Required by (4)

Sources (4)

Latest Comments

gborzi commented on 2016-05-24 00:26

There were another couple of declarations to fix, now I can save/read meshes in .med file format with gmsh. Here is the patch http://pastebin.com/WpUsW9uL

gborzi commented on 2016-05-23 19:33

I've been trying to debug med with hdf5 1.10. The main problem seems to be the switch from int (4 bytes) to long (8 bytes) for many hdf5 typedefs. Changing the various "int type_hdf" in med to "long type_hdf" fixes some problems, now gmsh complains "Could not create MED family x" with x = 1,2,... x=0 works.

mickele commented on 2016-05-13 16:55

This version of med (3.1.0) compiles fine with hdf5-1.10, but doesn't work properly. For example, gmsh doesn't create valid med file.
I recompiled the library linking to hdf5-1.8 and everything works fine. So I created a package hdf5-1.8 available at https://aur.archlinux.org/packages/hdf5-1.8/. To be compatible with hdf5 on main repository, it installs libraries in /opt/hdf5-1.8.

mickele commented on 2016-05-10 18:32

I was able to build med with hdf5-1.10, but it doesn't work. I had to downgrade to hdf5-1.8

deezy commented on 2016-05-05 19:10

@nchishol
I added patches for a rebuild against hdf5-1.10. Should work now.

nchishol commented on 2016-05-05 15:05

I'm getting the following error during compilation

<command-line>:0:0: note: this is the location of the previous definition
MEDequivInfo.c:27:1: error: conflicting types for 'MEDequivInfo'
MEDequivInfo(int fid, char *maa, int ind, char *eq, char *des)
^
In file included from ../../../include/2.3.6/med.h:143:0,
from MEDequivInfo.c:19:
../../../include/2.3.6/med_proto.h:221:1: note: previous declaration of 'MEDequivInfo' was here
MEDequivInfo(med_idt fid, char *maa, int ind, char *eq, char *des);
^
Makefile:621: recipe for target 'MEDequivInfo.lo' failed
make[3]: *** [MEDequivInfo.lo] Error 1

Has anyone else run into this issue? I was trying to recompile med and gmsh after gmsh began failing to start (probably related to the recent upgrade of the hdf5 package to 1.10.0-1). I also tried compiling med 3.08-4, but got the same error.

EDIT: The med-salome package seems to patch this problem as I'm able to compile it. After installing this package, I'm also able to build and run Gmsh without a problem.

mickele commented on 2016-03-31 21:44

With gmsh, saving mesh file in med format I have the following error

_MEDmeshDatagroupOpen.c [45] : Erreur à l'ouverture du groupe
_MEDmeshDatagroupOpen.c [45] : du maillage
_MEDmeshDatagroupOpen.c [46] : meshname = "1D_6"
MEDmeshNodeCoordinateWr.c [73] : Erreur à l'ouverture du groupe
MEDmeshNodeCoordinateWr.c [73] : du maillage
MEDmeshNodeCoordinateWr.c [74] : _meshpath = ""
MEDmeshNodeWr.c [72] : Erreur d'appel de l'API
MEDmeshNodeWr.c [72] : MEDmeshNodeCoordinateWr
_MEDmeshDatagroupOpen.c [45] : Erreur à l'ouverture du groupe
_MEDmeshDatagroupOpen.c [45] : du maillage
_MEDmeshDatagroupOpen.c [46] : meshname = "1D_6"
_MEDmeshAdvancedWr.c [125] : Erreur à l'ouverture du groupe
_MEDmeshAdvancedWr.c [125] : du maillage
_MEDmeshAdvancedWr.c [126] : _meshpath = ""
MEDmeshElementWr.c [79] : Erreur d'appel de l'API
MEDmeshElementWr.c [79] : MEDmeshElementConnectivityWr
_MEDmeshDatagroupOpen.c [45] : Erreur à l'ouverture du groupe
_MEDmeshDatagroupOpen.c [45] : du maillage
_MEDmeshDatagroupOpen.c [46] : meshname = "1D_6"
_MEDmeshAdvancedWr.c [125] : Erreur à l'ouverture du groupe
_MEDmeshAdvancedWr.c [125] : du maillage
_MEDmeshAdvancedWr.c [126] : _meshpath = ""
MEDmeshElementWr.c [79] : Erreur d'appel de l'API
MEDmeshElementWr.c [79] : MEDmeshElementConnectivityWr

Some time ago the same model gave no error. Any idea about possible causes?

Lone_Wolf commented on 2015-10-13 11:38

checking for swig... no
checking for swig2.0... no
configure: error: SWIG has been enable but can't find a valid version.
==> ERROR: A failure occurred in build().
Aborting...

Installing swig fixed the error, please check dependencies.

blixawillbargeld commented on 2015-10-08 07:54

Thanks, I also tried it on my private laptop and it did work there as well. So I have to locate the error on my system here.

deezy commented on 2015-10-07 07:44

@blixawillbargeld: just tried to build med (with openmpi 1.10.0) and it worked just fine. Seems to be something on your system.

All comments