Your message dated Sun, 24 Dec 2017 00:41:37 +1100 with message-id <1514036497.4433.53.ca...@debian.org> and subject line Re: libmpich1.0-dev: doesn't links properlly has caused the Debian Bug report #305748, regarding libmpich1.0-dev: doesn't links properlly to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 305748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libmpich1.0-dev Version: 1.2.5.3-5 Severity: important *** Please type your report below this line *** when runing a program with mpich I found a mesage sayin something about linking the Petsc libraries to a subdirectory of /home/hazelsct The user doesn't exists or have ever existed, as it was a test of some other software the first thing I made was to send a report to the developer of the other software (PETSc-FEM). Then on a rerun of the command without MPICH (working on a single-procesor machine) the comand finished correctly. So I started a search and found the chain inside the /usr/lib/mpich/lib directory, especifically inside te files libfmpich.a liblmpe.a libmpe.a libmpich.a libmpichfarg.a libslog.a maybe it just need a rebuild sorry for my bad English and im sorry if I have send the report before (I've had no confirmation and I have a lousy BOFH) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=es_AR, LC_CTYPE=es_AR (charmap=UTF-8) Versions of packages libmpich1.0-dev depends on: ii libmpich1.0 1.2.5.3-5 mpich runtime shared library -- no debconf information -- Jorge Blengino Firma en construcción
--- End Message ---
--- Begin Message ---On Thu, 21 Apr 2005 19:05:28 -0300 Jorge Blengino <jbleng...@gmail.com> wrote: > Package: libmpich1.0-dev > Version: 1.2.5.3-5 > Severity: important > > *** Please type your report below this line *** > when runing a program with mpich I found a mesage sayin something about > linking the Petsc libraries to a subdirectory of > > /home/hazelsct > ... > So I started a search and found the chain inside the /usr/lib/mpich/lib > directory, especifically inside te files > libfmpich.a > liblmpe.a > libmpe.a > libmpich.a > libmpichfarg.a > libslog.a > The only static libraries in libmpich-dev 3.3~a2-4 are now /usr/lib/x86_64-linux-gnu/libmpich.a /usr/lib/x86_64-linux-gnu/libmpichcxx.a There are no stray paths in libmpichcxx.a. libmpich.a shows some relative paths like src/mpi/comm/comm_create.c and ./src/include/mpir_comm.h so the build user's home directory is no longer exposed. PETSc has been building and working ok (since 3.4 at least) against mpich 2 and 3. I think we can judge this bug has been dealt with now, and libmpich1.0-dev is no longer in the archives, so closing. Drew
--- End Message ---
-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
