Can you try to build without specifying the --build, --host, and --target
options and just specifying the various FLAGS options as either -m32 or
-m64 as appropriate?  If that doesn't clean things up, can you include all
the information requested here:

  http://www.open-mpi.org/community/help/

Thanks,

Brian

On 8/24/11 1:15 PM, "Dmitry N. Mikushin" <maemar...@gmail.com> wrote:

>Thanks, Brian,
>
>I'm trying to follow the guide for 1.5.4, not yet clear what's wrong:
>
>[marcusmae@zacate build32]$ ../configure
>--prefix=/opt/openmpi_kgen-1.5.4
>--includedir=/opt/openmpi_kgen-1.5.4/include/32
>--libdir=/opt/openmpi_kgen-1.5.4/lib32 --build=x86_64-unknown-linux
>--host=x86_64-unknown-linux --target=i686-unknown-linux
>--disable-binaries
>
>...
>
>configure: WARNING: *** The Open MPI configure script does not support
>--program-prefix, --program-suffix or --program-transform-name. Users
>are recommended to instead use --prefix with a unique directory and
>make symbolic links as desired for renaming.
>configure: error: *** Cannot continue
>
>[marcusmae@zacate build32]$ ../configure
>--prefix=/opt/openmpi_kgen-1.5.4
>--includedir=/opt/openmpi_kgen-1.5.4/include/32
>--libdir=/opt/openmpi_kgen-1.5.4/lib32 --build=x86_64-unknown-linux
>--host=i686-unknown-linux --disable-binaries
>
>...
>
>checking gfortran external symbol convention... link: invalid option --
>'d'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>
>configure: error: unknown naming convention:
>
>2011/8/24 Barrett, Brian W <bwba...@sandia.gov>:
>> On 8/24/11 11:29 AM, "Dmitry N. Mikushin" <maemar...@gmail.com> wrote:
>>
>>>Quick question: is there an easy switch to compile and install both
>>>32-bit and 64-bit OpenMPI libraries into a single tree? E.g. 64-bit in
>>>/prefix/lib64 and 32-bit in /prefix/lib.
>>
>> Quick answer: not easily.
>>
>> Long answer: There's not an easy way, but there are some facilities to
>> help.  I believe Oracle uses them when building binaries for Solaris.
>> There is some documentation available on our Trac wiki:
>>
>>  https://svn.open-mpi.org/trac/ompi/wiki/MultiLib
>>  https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264
>>
>> The difficulty is that it's up to the user/admin to make sure the
>>correct
>> arguments are provided, as well as writing the wrapper script files to
>>do
>> the sharing.
>>
>> Brian
>>
>> --
>>  Brian W. Barrett
>>  Dept. 1423: Scalable System Software
>>  Sandia National Laboratories
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>
>


-- 
  Brian W. Barrett
  Dept. 1423: Scalable System Software
  Sandia National Laboratories






Reply via email to