Firefly and PC GAMESS-related discussion club


 
Learn how to ask questions correctly  
 
 
We are NATO-free zone
 



Re^2: Firefly v. 8.0.0 RC 33 build # 7420 is available for testing

Alex Granovsky
gran@classic.chem.msu.su


Hello Denis!

That's really strange! I cannot reproduce this.

As Firefly was linked with MPICH2 1.4, I decided to check it with mpich2 v. 1.5.

To check, I have compiled mpich2 1.5 on one of our CentOS boxes
(it's rather old system so the kernel version is patched 2.6.18).
I have picked up the latest mpich2 1.5 source code from official
site (the tarball is dated October 8, 2012). I have compiled it
using:


./configure --prefix=/opt/mpich2-1.5-gcc32 CFLAGS=-m32 CXXFLAGS=-m32 FFLAGS=-m32 FCFLAGS=-m32 --enable-shared

make; make install

The compiler was gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
(as C++ and Fortran libraries are not used by Firefly, this is the
only relevant compiler).

I have got a lot of libraries in /opt/mpich2-1.5-gcc32/lib
There was no libmpich.so.3 library so I created it as a symbolic
link to libmpich.so.8  

Then I ran Firefly using /opt/mpich2-1.5-gcc32/bin/mpiexec and got it running perfectly.  

Could it be the case there is some library conflict with
your installation of mpich2? Did you perhaps get some part
of the output in the file or there were no output at all?
What is the output of

./firefly -nompi

command?

Kind regards,
Alex



On Mon Oct 22 '12 4:13pm, Denis Zavelev wrote
---------------------------------------------
>Hello, Alex!

>Just tried to run firefly8.mpich2.ex from rc33 (with the same mpich2-1.5 built from sources with all 32-bit options) and got segmentation fault.
>===================================================================================
>=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
>=   EXIT CODE: 139
>=   CLEANING UP REMAINING PROCESSES
>=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
>===================================================================================
>YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)

>ldd firefly8.mpich2.ex
>gives:
>     linux-gate.so.1 =>  (0xf774e000)
>     libmpich.so.3 => /home/metalian/mpich2-install/lib/libmpich.so.3 (0xf74eb000)
>     libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf749e000)
>     libopa.so.1 => /home/metalian/mpich2-install/lib/libopa.so.1 (0xf749a000)
>     libmpl.so.1 => /home/metalian/mpich2-install/lib/libmpl.so.1 (0xf7494000)
>     librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf748b000)
>     libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7470000)
>     libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf746b000)
>     libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf72c0000)
>     libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf72a2000)
>     /lib/ld-linux.so.2 (0xf774f000)

>I'm using Ubuntu 12.04 64-bit with all latest updates, kernel version is 3.2.0-32-generic.

>Execution strings used (no difference between results):
>mpiexec -n 2 ./firefly8.mpich2.ex -r -f -p -o $inpfile.out -t scratch -b ./metalian.lib
>mpiexec -n 2 /home/metalian/Quant/ff8rc33_mpich2_linux/firefly8.mpich2.ex -r -f -p -o /home/metalian/Quant/ff8rc33_mpich2_linux/$inpfile.out -t /home/metalian/Quant/ff8rc33_mpich2_linux/scratch  -b /home/metalian/Quant/ff8rc33_mpich2_linux/metalian.lib

>I've also tried to use:
>./firefly8.mpich2.ex -f -p -o inptest.out -ex . -t scratch -p4pg procgrp
>In this case I'm getting only "Segmentation fault" message and nothing more.

>System is based upon AMD Athlon(tm) 64 X2 Dual Core Processor 6000+.


[ Previous ] [ Next ] [ Index ]           Tue Oct 23 '12 5:41pm
[ Reply ] [ Edit ] [ Delete ]           This message read 1091 times