On Thu, May 26, 2016 at 10:12 AM, <[email protected]> wrote: > Thank you for the reply. Will configure libmesh with METHOD=devel and > --disable_static. > > I am installing libmesh on a new cluster with developed compliers, so I > used AR .. > > The link of my code using libmesh is the follows, I can not find related > things about libstdc++.so in the Makefile. > > mpiCC two_phase_ch_ns.alpha-unknown-none.opt.o > update_rel_vel.alpha-unknown-none.opt.o > wall_velocity.alpha-unknown-none.opt.o -o two_phase_ch_ns -Wl,-rpath > -Wl,/home/export/online1/systest/swsiat/luoli/petsc-3.4/64bit-opt/lib > -Wl,-rpath -Wl,/home/export/online1/systest/swsiat/lapack-3.4.1 -Wl,-rpath > -Wl,/home/export/online1/systest/swsiat/luoli/libmesh-0.9.3/install-debug/lib > -L/home/export/online1/systest/swsiat/luoli/petsc-3.4/64bit-opt/lib > -L/home/export/online1/systest/swsiat/lapack-3.4.1 > -L/usr/sw-mpp/swcc/swgcc-binary/lib > -L/usr/sw-mpp/swcc/lib/gcc-lib/alpha-swcc-linux/5.421-sw-437/lib > -L/usr/sw-mpp/lib -L/usr/sw-mpp/mpi2/lib > -L/usr/sw-mpp/swcc/swgcc-binary/lib/gcc/alphaev6-unknown-linux-gnu/4.1.2 > -L/usr/sw-mpp/swcc/swgcc-binary/alphaev6-unknown-linux-gnu/lib > -L/usr/sw-mpp/swcc/sw5gcc-binary/lib/gcc/alphaev6-unknown-linux-gnu/4.1.2 > -L/usr/sw-mpp/swcc/sw5gcc-binary/lib/gcc > -L/usr/sw-mpp/swcc/sw5gcc-binary/alphaev6-unknown-linux-gnu/lib > -L/home/qh/swgcc_sw4A_alpha/gcc_build/alphaev6-unknown-linux-gnu/libstdc++-v3/src > -L/home/qh/swgcc_sw4A_alpha/gcc_build/alphaev6-unknown-linux-gnu/libstdc++-v3/src/.libs > -L/home/qh/swgcc_sw4A_alpha/gcc_build/./gcc > -L/usr/sw-mpp/swcc/swgcc-binary/alphaev6-unknown-linux-gnu/bin > -L/usr/sw-mpp/swcc/swgcc-binary/lib/gcc/alphaev6-unknown-linux-gnu/4.1.2/../../../../alphaev6-unknown-linux-gnu/lib > -lmv -lgcc_eh > -L/home/export/online1/systest/swsiat/luoli/libmesh-0.9.3/install-debug/lib > /home/export/online1/systest/swsiat/luoli/libmesh-0.9.3/install-debug/lib/libmesh_opt.a > /home/export/online1/systest/swsiat/luoli/libmesh-0.9.3/install-shared/lib/libnetcdf.a > -lpetsc -llapack -lrefblas /usr/sw-mpp/mpi2/lib/libmpifort.a > -lfortran_slave -lffio_slave -lmv_slave -lfortran -lffio -lslave -lathread > -lc_slave -lmaster /usr/sw-mpp/mpi2/lib/libmpicxx.a > /usr/sw-mpp/mpi2/lib/libmpi.a -lswtm -libverbs_wd -lrt -ldl -lpthread > -los_master_isp > /usr/sw-mpp/swcc/swgcc-binary/alphaev6-unknown-linux-gnu/lib/libstdc++.so > -lm -lc -lgcc_s -Wl,-rpath > -Wl,/usr/sw-mpp/swcc/swgcc-binary/alphaev6-unknown-linux-gnu/lib -Wl,-rpath > -Wl,/usr/sw-mpp/swcc/swgcc-binary/alphaev6-unknown-linux-gnu/lib >
I grepped briefly through your link line, but didn't find anything like "-shared" or "-dynamic", so it's possible that the mpiCC on this cluster does static linking by default. I'm not sure what the relationship between mpiCC and /usr/sw-mpp/swcc/swgcc-binary/alphaev6-unknown-linux-gnu/lib/libstdc++.so is though. It's like the latter is some non-system library that's being pulled into an otherwise static link unexpectedly, you will need to figure out what exactly is doing it. Based on its position in the link line, I'm going to guess it's mpiCC itself though. Is there an equivalent of "mpiCC -show" which will print the libraries that mpiCC is going to use to link? -- John ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
