On 10/19/07, Jim Kusznir <jkusz...@gmail.com> wrote:
> I caught some of that above...I suspect rpm's build environment for
> cross-platform building "leaves much to be desired"...At this point, I
> was thinking my best option would be to set up a i386 box and build
> the .i386 libs on that.
>
Multilib installations are not trivial. However this particular
issue is a trivial issue/oversight. I haven't checked the CentOS one,
but the RHEL spec file doesn't pass any FCFLAGS argument to the
configure file. So, edit your spec file and add
FCFLAGS="$RPM_OPT_FLAGS $XFLAGS"
line in the configure script line and retry.
You wouldn't need to do this on an i386 box, though if you can do it,
it'd be just fine. However if you are on hardware/time/resource
restraint and can't do it , you should be able to do this just fine on
your x86_64 machines, but you might have to install some i386
dependencies .
thanks,
gurhan
> I must say, I'm pretty disappointed in rpm, as the x86_64 platform
> seems to "require" both 64 and 32 versions of its libs and devel
> files. Yet, on a x86_64 platform, it doesn't appear that the 32-bit
> versions can be generated reliably.
>
> Unfortunately for me, I need the binaries in rpm form, as this will be
> "mass-deployed" to a ROCKs cluster, and the installer installs rpms.
>
> --Jim
>
> On 10/18/07, Gurhan <gurhan.o...@gmail.com> wrote:
> > Hello,
> >
> > configure:33918: gcc -DNDEBUG -O2 -g -pipe -m32 -march=i386
> > -mtune=pentium4 -fno-strict-aliasing -I. -c conftest.c
> > configure:33925: $? = 0
> > configure:33935: gfortran conftestf.f90 conftest.o -o conftest
> > /usr/bin/ld: warning: i386 architecture of input file `conftest.o' is
> > incompatible with i386:x86-64 output
> > configure:33942: $? = 0
> > configure:33990: ./conftest
> > configure:33997: $? = 139
> > configure:34006: error: Could not determine size of LOGICAL
> >
> > Is this correct? We are feeding a 32-bit object file to be linked with
> > a 64-bit output executable file? When target is i386 shouldn't -m32
> > -march=i386 need to be passed on to gfortran as well on above
> > instance, unless it's for negative testing?
> >
> > Thanks,
> > gurhan
> >
> >
> > On 10/18/07, Jim Kusznir <jkusz...@gmail.com> wrote:
> > > Attached is the requested info. There's not much here, though...it
> > > dies pretty early in.
> > >
> > > --Jim
> > >
> > > On 10/17/07, Jeff Squyres <jsquy...@cisco.com> wrote:
> > > > On Oct 17, 2007, at 12:35 PM, Jim Kusznir wrote:
> > > >
> > > > > checking if Fortran 90 compiler supports LOGICAL... yes
> > > > > checking size of Fortran 90 LOGICAL... ./configure: line 34070: 7262
> > > > > Segmentation fault ./conftest 1>&5 2>&1
> > > > > configure: error: Could not determine size of LOGICAL
> > > >
> > > > Awesome! It looks like gfortran itself is seg faulting.
> > > >
> > > > Can you send all the information listed on the getting help page?
> > > >
> > > > http://www.open-mpi.org/community/help/
> > > >
> > > > That will help confirm/deny whether it's gfortran itself that is seg
> > > > faulting. If it's gfortran that's seg faulting, there's not much
> > > > that Open MPI can do...
> > > >
> > > > --
> > > > Jeff Squyres
> > > > Cisco Systems
> > > >
> > > > _______________________________________________
> > > > users mailing list
> > > > us...@open-mpi.org
> > > > http://www.open-mpi.org/mailman/listinfo.cgi/users
> > > >
> > >
> > > _______________________________________________
> > > users mailing list
> > > us...@open-mpi.org
> > > http://www.open-mpi.org/mailman/listinfo.cgi/users
> > >
> > >
> > _______________________________________________
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
> >
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
