I've uploaded a new cvs-stable package (1.11.22) to my experimental.
http://fink.cvs.sourceforge.net/fink/experimental/alexkhansen/common/finkinfo/devel/cvs-stable.info
It should work on 10.3 and both 10.4 trees.
I'd appreciate feedback before I add it.
--
Alexander K. Hansen
Fink Documenter
I have posted to fink tracking new proposed packaging for a
lammpi2 package and revised packaging for openmpi, gromacs-mpi,
maloc-mpi and apbs-mpi. The changes in lammpi2 involve making the
new package (which is effectively the current lammpi in unstable)
conflict with lammpi. The other
The Fink Developer Wiki has moved to a new location: http://
wiki.finkproject.org . Please make sure that any future changes to
the wiki that you make are made at the new location. The last
changes which were made at the old site were made on July 22 by
Fingolfin (to the page
Jack,
I've been working on the lammpi issues for the past few days, and
there is a workaround which will let us avoid creating a lammpi2
package: namely, creating symlinks in the new lammpi-shlibs which
point the old locations of the shared libraries to the new ones.
Here, I am assuming
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alfred Lee wrote:
Hi Guys,
I tried to install kdebase3-unified on my Mac G3. I've got Mac OS X 10.4,
XCode 2.3 and JRE1.5.0_06 installed.
It Failed with the following errors:
..
checking if javac works... configure: error: The Java
Dave,
If I understand the current situation correctly, if you attempt to
install openmpi with the old lammpi present, it won't install because
of conflicting files. That doesn't bother me to much since your average
user ought to be able to puzzle out that lammpi needs to be upgraded
first. Of
On Jul 22, 2006, at 6:49 PM, Jack Howarth wrote:
Dave,
If I understand the current situation correctly, if you attempt to
install openmpi with the old lammpi present, it won't install because
of conflicting files.
Well, the actual conflict is between some files in the new openmpi-
dev
Dave,
I guess that implies that there will be a problem
if the following steps occur...
1) the old lammpi is already installed
2) openmpi-dev is then installed overwriting the files in the old lammpi
3) the old lammpi is then upggraded to the new lammpi.
When dpkg deinstalls the old lammpi
Dave,
I think it is pretty safe to say that it would be the case that
anything that uses mpif77 to build a program would break when
liblamf77mpi.dylib is changed from being built with g77 to being
built with gfortran (or g95 for that matter). I guess we can check
the binaries in maloc-mpi,
Dave,
Back to the proposed lammpi2 packaging...I have run into a problem
that has me baffled. If I have the older unstable packages...
ii lammpi 7.0.6-1012 MPI implementation for parallel computing
ii lammpi-dev 7.0.6-1012 Development files for lammpi package
ii
Dave,
FYI, I checked the current packages that use lammpi in fink 10.4 unstable.
In gromacs-mpi-lammpi-dev we have...
otool -L /sw/lib/libgmx_mpi.dylib | grep 77
/sw/lib/lammpi/liblamf77mpi.0.dylib (compatibility version 1.0.0,
current version 1.0.0)
The apbs-mpi-lammpi package is
11 matches
Mail list logo
