Peter,
I have verified that the current gromacs-mpi packaging for 3.3-1 in
fink tracking builds fine against the lam-7.0.6-11 currently in unstable.
The problem seems to be specific to lam-7.1.1. With the lam-7.1.1-1
package installed (which was built with MACOSX_DEPLOYMENT_TARGET 10.2),
I find that the gromacs-mpi 3.3-1 build fails with the error...
-force_flat_namespace not allowed with -dynamiclib
I assume this is because mpicc is dragging in the offending
-force_flat_namespace. I tried manually removing the -force_flat_namespace
from the call to libtool on the command line and I still got that
error so it must be from mpicc indirectly. If I just checkin the new
fftw3 and gromacs/gromacs-mpi packages everything will be okay. However
the most recent lam 7.1.1 release appears to only build correctly
(ie lamboot actually runs) under gcc-4.0/g++-4.0 and MACOS_DEPLOYMENT_TARGET
>= 10.3.
Could you download the lammpi-7.1.1-1 and gromacs/gromacs-mpi-3.3-1
files from fink tracking and try building them. If you remove the
SetMACOSX_DEPLOYMENT_TARGET: 10.2
from the lammpi.info file you will find that while lammpi builds, when
you execute 'lamboot -v lamhosts', the test will fail.
Jack
ps When do we ever get the 10.4 branch so we can chuck all this gcc-3.3
crap. As far as I am concerned most of the problem is that upstream is
worried about a clean gcc-3.3 or gcc-4.0 and not some mutant combo.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel
