Attached please find the output info when I ran configure with -m32 option. Because I am building 64-bit libraries, the log files cannot be obtained now.<div><br></div><div>- Clara<br><br><div class="gmail_quote">On Sat, Jun 25, 2011 at 10:28 AM, Pavan Balaji <span dir="ltr"><<a href="mailto:balaji@mcs.anl.gov">balaji@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Can you send us the log files are described in the README? Please compress them as they can be huge.<br>
<br>
-- Pavan<div class="im"><br>
<br>
On 06/25/2011 09:12 AM, clara wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Thanks, but now I get the below error:<br>
configure: error: Could not determine a way to link a Fortran test program!<br>
<br>
<br>
On Sat, Jun 25, 2011 at 9:59 AM, Pavan Balaji <<a href="mailto:balaji@mcs.anl.gov" target="_blank">balaji@mcs.anl.gov</a><br></div><div class="im">
<mailto:<a href="mailto:balaji@mcs.anl.gov" target="_blank">balaji@mcs.anl.gov</a>>> wrote:<br>
<br>
<br></div><div class="im">
It's "CFLAGS", not "CFLAG".<br>
<br>
-- Pavan<br>
<br>
<br>
On 06/25/2011 08:42 AM, clara wrote:<br>
<br>
I executed the following command:<br>
./configure --prefix=/mnt/lux/git/pios/xc/<u></u>__mpich2-32<br>
--with-pm=gforker<br>
--disable-faster CFLAG=-m32 CXXFLAGS=-m32 FFLAGS=-m32 FCFLAGS=-m32<br>
<br>
and got the below errors:<br>
configure: error: **** Incompatible Fortran and C Object File<br>
Types! ****<br>
F77 Object File Type produced by "gfortran -m32 " is : : ELF<br>
32-bit LSB<br>
relocatable, Intel 80386, version 1 (SYSV), not stripped.<br>
C Object File Type produced by "gcc -O2" is : : ELF 64-bit LSB<br>
relocatable, x86-64, version 1 (SYSV), not stripped.<br>
<br>
Is there any simple way setting -m32 in order to build 32-bit<br>
libraries<br>
on 64-bit system?<br>
<br>
- Clara<br>
<br>
On Fri, Jun 24, 2011 at 11:53 AM, Anthony Chan <<a href="mailto:chan@mcs.anl.gov" target="_blank">chan@mcs.anl.gov</a><br>
<mailto:<a href="mailto:chan@mcs.anl.gov" target="_blank">chan@mcs.anl.gov</a>><br></div><div><div></div><div class="h5">
<mailto:<a href="mailto:chan@mcs.anl.gov" target="_blank">chan@mcs.anl.gov</a> <mailto:<a href="mailto:chan@mcs.anl.gov" target="_blank">chan@mcs.anl.gov</a>>>> wrote:<br>
<br>
<br>
You need to rebuild mpich2 for 32bit. Set<br>
CFLAGS/CXXFLAGS/FFLAGS/FCFLAGS<br>
to -m32 (assume your system has the 32bit support).<br>
<br>
BTW, your install of 1.2.1p1 mpich2 is old, please upgrade<br>
if possible<br>
(the latest stable release is 1.4)<br>
<br>
A.Chan<br>
<br>
----- Original Message -----<br>
> I think the default installed mpich2 in 64-bit ubuntu is in<br>
x86_64<br>
> mode.<br>
> When I try to compile/link an MPI program in 32-bit mode,<br>
there is an<br>
> error<br>
> below:<br>
> /usr/lib/libmpich.so: file not recognized: File format not<br>
recognized<br>
><br>
> How can I configure the compile/link flags? Do I need to rebuild<br>
> mpich2 to<br>
> get a 32-bit libraries? Or is there any 32-bit libraries<br>
coexisted<br>
> with<br>
> 64-bit libraries? Thanks.<br>
><br>
> Below is the output version information of the default installed<br>
> MPICH2:<br>
> MPICH2 Version: 1.2.1p1<br>
> MPICH2 Release date: Unknown, built on Tue Apr 27 15:06:31<br>
UTC 2010<br>
> MPICH2 Device: ch3:nemesis<br>
> MPICH2 configure: --build=x86_64-linux-gnu --prefix=/usr<br>
> --includedir=${prefix}/include --mandir=${prefix}/share/man<br>
> --infodir=${prefix}/share/info --sysconfdir=/etc<br>
--localstatedir=/var<br>
> --libexecdir=${prefix}/lib/__<u></u>mpich2 --disable-maintainer-mode<br>
> --disable-dependency-tracking --disable-silent-rules --srcdir=.<br>
> --enable-sharedlibs=gcc --prefix=/usr --enable-f90<br>
> --sysconfdir=/etc/mpich2<br>
> --includedir=/usr/include/__<u></u>mpich2 --docdir=/usr/share/doc/mpich2<br>
> MPICH2 CC: gcc -g -O2 -g -Wall -O2 -O2<br>
> MPICH2 CXX: c++ -g -O2 -g -Wall -O2 -O2<br>
> MPICH2 F77: gfortran -g -O2 -O2<br>
> MPICH2 F90: f95 -O2<br>
><br>
> - Clara<br>
><br>
> On Fri, Jun 24, 2011 at 12:08 AM, Pavan Balaji<br>
<<a href="mailto:balaji@mcs.anl.gov" target="_blank">balaji@mcs.anl.gov</a> <mailto:<a href="mailto:balaji@mcs.anl.gov" target="_blank">balaji@mcs.anl.gov</a>><br></div></div>
<mailto:<a href="mailto:balaji@mcs.anl.gov" target="_blank">balaji@mcs.anl.gov</a> <mailto:<a href="mailto:balaji@mcs.anl.gov" target="_blank">balaji@mcs.anl.gov</a>>>><div><div></div><div class="h5">
<br>
<br>
> wrote:<br>
><br>
> > Clara,<br>
> ><br>
> ><br>
> > On 06/23/2011 10:53 PM, clara wrote:<br>
> ><br>
> >> If I only use shared memory communication among processes on a<br>
> >> single<br>
> >> node, how can I configure the mpich2.1.4 (except<br>
--with-pm=gforker)<br>
> >> in<br>
> >> order to link libraries as little as possible?<br>
> >><br>
> ><br>
> > Shared memory communication support comes by default in<br>
MPICH2. You<br>
> > don't<br>
> > need to pass any special configure options; not even<br>
> > --with-pm=gforker.<br>
> > Unfortunately, all libraries are still required to be<br>
linked with<br>
> > even when<br>
> > only shared memory support is needed.<br>
> ><br>
> > -- Pavan<br>
> ><br>
> ><br>
> > --<br>
> > Pavan Balaji<br>
> > <a href="http://www.mcs.anl.gov/~balaji" target="_blank">http://www.mcs.anl.gov/~balaji</a><br>
> ><br>
><br>
> ______________________________<u></u>___________________<br>
> mpich-discuss mailing list<br>
> <a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a> <mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
<br>
> <a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
______________________________<u></u>___________________<br>
mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a> <mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl." target="_blank">mpich-discuss@mcs.anl.</a><u></u>__gov<br>
<mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>>><br>
<br>
<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br>
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<br>
<br>
<br>
<br>
______________________________<u></u>___________________<br>
mpich-discuss mailing list<br>
<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.gov</a> <mailto:<a href="mailto:mpich-discuss@mcs.anl.gov" target="_blank">mpich-discuss@mcs.anl.<u></u>gov</a>><br>
<a href="https://lists.mcs.anl.gov/__mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/__<u></u>mailman/listinfo/mpich-discuss</a><br></div></div><div class="im">
<<a href="https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss" target="_blank">https://lists.mcs.anl.gov/<u></u>mailman/listinfo/mpich-discuss</a><u></u>><br>
<br>
<br>
--<br>
Pavan Balaji<br>
<a href="http://www.mcs.anl.gov/~balaji" target="_blank">http://www.mcs.anl.gov/~balaji</a><br>
<br>
<br>
</div></blockquote>
<br>
-- <br><div><div></div><div class="h5">
Pavan Balaji<br>
<a href="http://www.mcs.anl.gov/~balaji" target="_blank">http://www.mcs.anl.gov/~balaji</a><br>
</div></div></blockquote></div><br></div>