Re: libmed 64 bits (was: Re: Code Aster version NEW11.0.10 uploaded to SVN)
Da: Adam C Powell IV hazel...@debian.org A: Andrea Palazzi palazziand...@yahoo.it Cc: Debian Science List debian-science@lists.debian.org Inviato: Venerdì 16 Dicembre 2011 1:50 Oggetto: Re: libmed 64 bits (was: Re: Code Aster version NEW11.0.10 uploaded to SVN) Hello Andrea, On Wed, 2011-12-14 at 20:50 +, Andrea Palazzi wrote: About this problem, I was wondering if it would be possible to build a libmed64 package beside the ones already built, so Could this be done somehow? Nobody on this topic? The maintainer of libmed? D'oh! I guess that's me and Aurelien Jarno, the only two who have uploaded. This might require building twice for the normal and libmed64 versions, which will change debian/rules quite a bit. Hi, other possible solutions could be to build CA without -fdefault-integer-8 etc or remove MED support (or leave it like this, not working); being things like this I'm getting convinced that the best solution for the moment is to build without the -f flags and wait for upstream to fix it: it's the easiest thing to do, and the package will be (hopefully) fully functional. If upstream doesn't show interest in fixing this issue, we'll think about libmed64 again, but they've always been collaborative; I'm going to test if my solution works as expected: if it does, we can go on without any other effort. Bye Andrea
Re: libmed 64 bits (was: Re: Code Aster version NEW11.0.10 uploaded to SVN)
Hello Andrea, On Wed, 2011-12-14 at 20:50 +, Andrea Palazzi wrote: However, the package builds but the executable has a big problems when reading MED files (containing mesh data and results). I'm almost sure that this comes from the use of the flag _MED_USE_SHORT_INT - as a reminder, the process of CA installation from the EDF package builds also the libraries, all with 64bit integers by default ( -fdefault-double-8 -fdefault-integer-8 -fdefault-real-8 ). About this problem, I was wondering if it would be possible to build a libmed64 package beside the ones already built, so that we can use that for CA and solve the problem; other advantages of this approach would be of less effort from upstream and a wider user base to use this configuration - I think I'm the only one using _MED_USE_SHORT_INT. Could this be done somehow? Nobody on this topic? The maintainer of libmed? D'oh! I guess that's me and Aurelien Jarno, the only two who have uploaded. This might require building twice for the normal and libmed64 versions, which will change debian/rules quite a bit. I have a bunch of other stuff to do around the mpi-defaults transition and might not get to this for a week or two, would you (or anyone else) be willing to investigate a patch? -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
