<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>216120</bug_id>
          
          <creation_ts>2008-04-04 00:39 0000</creation_ts>
          <short_desc>Please keyword sys-cluster/openmpi-1.2.6</short_desc>
          <delta_ts>2008-06-16 05:48:48 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>REOPENED</bug_status>
          
          
          
          <keywords>KEYWORDREQ</keywords>
          <priority>P2</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>225045</blocked>
          
          <everconfirmed>1</everconfirmed>
          <reporter>jsbronder@gentoo.org</reporter>
          <assigned_to>hp-cluster@gentoo.org</assigned_to>
          <cc>fmccor@gentoo.org</cc>
    
    <cc>hppa@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>jsbronder@gentoo.org</who>
            <bug_when>2008-04-04 00:39:45 0000</bug_when>
            <thetext>Please keyword openmpi, we really need to stop using mpich by default in virtual/mpi and this is the first step along that path.

Thanks.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>corsair@gentoo.org</who>
            <bug_when>2008-04-07 15:44:12 0000</bug_when>
            <thetext>added ~ppc64</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>klausman@gentoo.org</who>
            <bug_when>2008-04-07 18:33:24 0000</bug_when>
            <thetext>Keyworded on alpha.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jsbronder@gentoo.org</who>
            <bug_when>2008-04-16 14:47:34 0000</bug_when>
            <thetext>Adding sparc, see #217854.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2008-04-16 15:36:33 0000</bug_when>
            <thetext>Then why not add all relevant arches? I know of one...</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jsbronder@gentoo.org</who>
            <bug_when>2008-04-16 16:01:25 0000</bug_when>
            <thetext>(In reply to comment #4)
&gt; Then why not add all relevant arches? I know of one...

Glad you caught that as mpich was stabled for hppa after I filed this bug and I hadn&apos;t been monitoring that ebuild. ;)
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>fmccor@gentoo.org</who>
            <bug_when>2008-04-16 16:04:19 0000</bug_when>
            <thetext>Added ~sparc.  ompi_info works as it should.  I have used this product on sparc and know that it should work well, but I have no extensive tests close at hand.

That said, this package comes with an extensive test suite. However, for some reason &apos;FEATURES=test emerge -v openmpi&apos; does not run it.  So, I ran it by hand.  All tests pass.

Thanks, Justin, for bringing this to our attention.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2008-04-18 03:27:09 0000</bug_when>
            <thetext>Hmm, sadly openmpi has not been ported to PARISC Linux... Debian doesn&apos;t have a port either. All in all it wouldn&apos;t make sense to port a high performance app to a dying architecture, so any porting patch may not even be accepted upstream now.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jsbronder@gentoo.org</who>
            <bug_when>2008-04-18 17:14:10 0000</bug_when>
            <thetext>ppc arch team:  I have access to a ppc machine (dual G4) and have upload the results of compiling and testing to my devspace.  I don&apos;t know if it matters or what your policy on keywording is, but maybe this could help move things along?
http://dev.gentoo.org/~jsbronder/ppc-openmpi-1.2.5-logs.tar.bz2

(In reply to comment #6)
&gt; That said, this package comes with an extensive test suite. However, for some
&gt; reason &apos;FEATURES=test emerge -v openmpi&apos; does not run it.  So, I ran it by
&gt; hand.  All tests pass.

Sorry about that.  Luckily 1.2.6 is out, so I&apos;ll be sure to check this functionality before commiting.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nixnut@gentoo.org</who>
            <bug_when>2008-04-18 20:18:11 0000</bug_when>
            <thetext>(In reply to comment #8)
&gt; ppc arch team:  I have access to a ppc machine (dual G4) and have upload the
&gt; results of compiling and testing to my devspace.  I don&apos;t know if it matters or
&gt; what your policy on keywording is, but maybe this could help move things along?
&gt; http://dev.gentoo.org/~jsbronder/ppc-openmpi-1.2.5-logs.tar.bz2

Feel free to keyword it. In general if you can test it on ppc hardware, you can add ~ppc keywords. When in doubt, just poke on of us. And thanks for testing :-)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jsbronder@gentoo.org</who>
            <bug_when>2008-04-18 20:35:23 0000</bug_when>
            <thetext>added ~ppc.

I think we&apos;re done unless you want to keep this open for hppa Jeroen?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2008-04-19 16:39:48 0000</bug_when>
            <thetext>Er, well I stated there are issues, but I am not Gentoo&apos;s contact to $UPSTREAM so suppose if they have a lingering patch that could provide hppa support, then I am not the one to go find out. :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jsbronder@gentoo.org</who>
            <bug_when>2008-04-21 14:19:44 0000</bug_when>
            <thetext>Closing as I have no access to hppa stuff ;)

Also, I just put 1.2.6 in the tree which fixes the missing src_test() stuff.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2008-06-06 14:02:24 0000</bug_when>
            <thetext>dev-libs/boost-1.35.0-r1 now depends on some mpi. mpich is too old, mpich2 depends on Java, which hppa doesn&apos;t currently do, which leaves openmpi.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2008-06-16 05:48:48 0000</bug_when>
            <thetext>Created an attachment (id=157045)
gentoo-x86/sys-cluster/openmpi/files/openmpi-1.2.6-hppa.patch

Something like this ought to work. It passes the point where it failed before:

checking for asssembly architecture... HPPA
checking for perl... perl
checking for pre-built assembly file... no (not in asm-data)
checking whether possible to generate assembly file... failed
configure: WARNING: Could not build atomic operations assembly file.
configure: WARNING: There will be no atomic operations for this build.
checking for atomic assembly filename... none

*** Fortran 77 compiler
[...]

But then it fails further on in econf:

*** Libtool configuration
checking for a sed that does not truncate output... /bin/sed
checking for ld used by hppa2.0-unknown-linux-gnu-gcc... /usr/hppa2.0-unknown-linux-gnu/bin/ld
checking if the linker (/usr/hppa2.0-unknown-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/hppa2.0-unknown-linux-gnu/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for dlfcn.h... (cached) yes
checking how to run the C++ preprocessor... hppa2.0-unknown-linux-gnu-g++ -E
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from hppa2.0-unknown-linux-gnu-gcc object... ok
checking for objdir... .libs
checking for hppa2.0-unknown-linux-gnu-ar... hppa2.0-unknown-linux-gnu-ar
checking for hppa2.0-unknown-linux-gnu-ranlib... hppa2.0-unknown-linux-gnu-ranlib
checking for hppa2.0-unknown-linux-gnu-strip... hppa2.0-unknown-linux-gnu-strip
checking for correct ltmain.sh version... no
configure: error:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.26, ltmain.sh = 2.1a) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

make: *** [config.status] Error 1</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>157045</attachid>
            <date>2008-06-16 05:48 0000</date>
            <desc>gentoo-x86/sys-cluster/openmpi/files/openmpi-1.2.6-hppa.patch</desc>
            <filename>openmpi-1.2.6-hppa.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIGNvbmZpZ3VyZS4JMjAwOC0wMy0yNSAxMzo0MzoxNC4wMDAwMDAwMDAgKzAxMDAKKysrIGNv
bmZpZ3VyZQkyMDA4LTA2LTE2IDA3OjE0OjU5LjA4Mzg5OTgzMCArMDIwMApAQCAtMjU1NzQsNiAr
MjU1NzQsMTEgQEAKICAgICAgICAgICAgIGZpCiAgICAgICAgICAgICBPTVBJX0dDQ19JTkxJTkVf
QVNTSUdOPScibW92IDAsJTAiIDogIj0mciIocmV0KScKICAgICAgICAgICAgIDs7CisgICAgICAg
IGhwcGEqKQorICAgICAgICAgICAgb21waV9jdl9hc21fYXJjaD0iSFBQQSIKKyAgICAgICAgICAg
IE9NUElfQVNNX1NVUFBPUlRfNjRCSVQ9MQorICAgICAgICAgICAgT01QSV9HQ0NfSU5MSU5FX0FT
U0lHTj0nIm1vdiAlMD1yMFxuOztcbiIgOiAiPSZyIihyZXQpJworICAgICAgICAgICAgOzsKIAog
ICAgICAgICAqKQogICAgICAgICAgICAgeyB7IGVjaG8gIiRhc19tZTokTElORU5POiBlcnJvcjog
Tm8gYXRvbWljIHByaW1pdGl2ZXMgYXZhaWxhYmxlIGZvciAkaG9zdCIgPiY1Cg==
</data>        

          </attachment>
    </bug>

</bugzilla>