Re: [OMPI devel] Tarball distribution

.1 (for the v1.5 > series) may be tolerable. I'll check it out. > > > > On Jun 27, 2011, at 2:09 AM, Ralf Wildenhues wrote: > > > Hi John, > > > > * John Esmet wrote on Sun, Jun 26, 2011 at 06:41:48AM CEST: > >> I went to untar the source code and t

Re: [OMPI devel] Tarball distribution

Hi John, * John Esmet wrote on Sun, Jun 26, 2011 at 06:41:48AM CEST: > I went to untar the source code and the folders are mode 777. Call me OCD, > but I find this a little strange. What's up? Newer Automake releases should have that fixed:

Re: [OMPI devel] Compiling problem in trunk?

Hello, * Xin He wrote on Thu, Jun 23, 2011 at 01:23:53PM CEST: > make[3]: Entering directory `/home/ehhexxn/git/ompi/ompi/include' > FC mpif90-ext.lo > libtool: compile: unrecognized option `-c' > libtool: compile: Try `libtool --help' for more information. > make[3]: *** [mpif90-ext.lo]

Re: [OMPI devel] "make check" (libtool) failure on Linux/ppc w/ XLC (1.5rc5 and 1.4.3rc1)

h the requested files off-list. > -Paul > > > Ralf Wildenhues wrote: > >* Paul H. Hargrove wrote on Fri, Aug 27, 2010 at 03:54:54AM CEST: > >>>I am now looking at using IBM's XLC compilers for ILP32 builds on > >>>the same Linux/PPC64 platform for which I'

Re: [OMPI devel] Failure (libtool?) to build F90 bindings w/ XLC/PPC64 (1.5rc5 and 1.4.3rc1)

[ http://www.open-mpi.org/community/lists/devel/2010/08/8398.php ] Hello Paul, sorry for the late reply. This issue you reported is valid; it is already fixed in upstream Libtool 2.2.8, with commit v2.2.6-201-g519bf91:

Re: [OMPI devel] update configury for Autoconf 2.68

* Jeff Squyres wrote on Fri, Sep 24, 2010 at 03:26:46PM CEST: > On Sep 23, 2010, at 2:15 PM, Ralf Wildenhues wrote: > >> Is the silent-rules clause in AM_INIT_AUTOMAKE exactly equivalent to > >> calling AM_SILENT_RULES? > > > > Yes. > > Weird -- when I do t

Re: [OMPI devel] Setting AUTOMAKE_JOBS

Hello Ralph, wow, that's not good to hear. I knew the perl ithreads implementation wasn't all that efficient, but causing a deadlock sounds like you have more trouble than just perl; at least I hope so. For reference, can you send 'perl -V' output (if you like, to the bug-automake at gnu.org

Re: [OMPI devel] update configury for Autoconf 2.68

* Jeff Squyres wrote on Thu, Sep 23, 2010 at 08:11:41PM CEST: > On Sep 23, 2010, at 2:03 PM, Ralf Wildenhues wrote: > > >> Is the call to AM_SILENT_RULES now moot because it's listed in > >> AM_INIT_AUTOMAKE? > > > > Oh, just drop that hunk, that wa

Re: [OMPI devel] update configury for Autoconf 2.68

Hi Jeff, * Jeff Squyres wrote on Thu, Sep 23, 2010 at 03:31:32PM CEST: > One very minor question: I notice you added silent-rules to > AM_INIT_AUTOMAKE (and bumped the required version, too), but still > left in the call to AM_SILENT_RULES: > > -AM_INIT_AUTOMAKE([foreign dist-bzip2

[OMPI devel] update configury for Autoconf 2.68

Hello OpenMPI developers, just-released Autoconf 2.68 contains more stringent checks and warnings about stuff passed to AC_{COMPILE,LINK,RUN}_IFELSE and AC_TRY_* macros. Specifically, it will warn if C or C++ programs are not generated with AC_LANG_SOURCE or AC_LANG_PROGRAM, in order to avoid

Re: [OMPI devel] Setting AUTOMAKE_JOBS

Hi Jeff, adding bug-automake in Cc: (non-subscribers can't post to the Open MPI list, so please remove that Cc: in case) * Jeff Squyres wrote on Wed, Sep 22, 2010 at 03:50:19PM CEST: > $AUTOMAKE_JOBS Total wall time > valueof autogen.pl > 8

Re: [OMPI devel] AS_VAR_COPY failure (Re: === CREATE FAILURE (v1.4) ===)

> > It seems that the execution of "autoconf" has failed. See above for > > the specific error message that caused it to abort. > > - > > &

Re: [OMPI devel] "make check" (libtool) failure on Linux/ppc w/ XLC (1.5rc5 and 1.4.3rc1)

* Paul H. Hargrove wrote on Fri, Aug 27, 2010 at 03:54:54AM CEST: > >I am now looking at using IBM's XLC compilers for ILP32 builds on > >the same Linux/PPC64 platform for which I've reported some > >XLC/LP64 bugs. > > > >What I find now is that "make check" is failing with the loader > >unable to

Re: [OMPI devel] "make check" (libtool?) failure on Solaris/SPARC (1.5rc5 and 1.4.3rc1)

* Paul H. Hargrove wrote on Thu, Aug 26, 2010 at 10:14:22PM CEST: > I just had a thought on this one: In my environment on this > platform I have LD_LIBRARY_PATH_32 and LD_LIBRARY_PATH_64 set. It > seems possible to me that this is causing the loader to ignore the > LD_LIBRARY_PATH setting that

Re: [OMPI devel] "make check" (libtool?) failure on Solaris/SPARC (1.5rc5 and 1.4.3rc1)

Hello Paul, * Paul H. Hargrove wrote on Thu, Aug 26, 2010 at 01:58:11AM CEST: > I have been able to configure and build both 1.5rc5 and 1.4.3rc1 on > Solaris 10 for SPARC, using Sun C 5.10. > I have also build 1.5rc5 w/ gcc-3.3.2 (and expect 1.4.3rc1 to build > w/ gcc as well, once I have time) >

Re: [OMPI devel] Fixes to OpenMPI-1.4.2 for PGI compilers

and fixes to the developers of the code I use. I really have > to leave it up to them to decide whether to pass them on to their > upstream providers. > > Larry Baker > US Geological Survey > 650-329-5608 > ba...@usgs.gov > > On Aug 20, 2010, at 8:24 AM, Jeff Sq

Re: [OMPI devel] v1.5 .so version numbers

Hi Jeff, * Jeff Squyres wrote on Thu, Jun 03, 2010 at 09:34:16PM CEST: > SHORT VERSION: We broke ABI from the 1.4 series to the v1.5 series. I > propose changing all the libtool .so version numbers as shown below to > enforce that break. Can someone sanity check this? Looks sane to me, with

Re: [OMPI devel] The" Missing Symbol" issue and OpenMPI on NetBSD

Hello Kevin, * kevin.buck...@ecs.vuw.ac.nz wrote on Tue, May 11, 2010 at 06:42:01AM CEST: > That is a file that gets patched in the NetBSD build as follows > > $diff opal/mca/base/mca_base_component_find.c{.orig,} > 44,46d43 > < #ifndef __WINDOWS__ > < #include "opal/libltdl/ltdl.h" > <

Re: [OMPI devel] bug with /bin/sh and /bin/ksh

Hello, * Jeff Squyres wrote on Mon, May 03, 2010 at 04:04:59PM CEST: > > On Apr 29, 2010, at 11:24 AM, Jonathan Vincent wrote: > > > > > sh -c '/usr/bin/env FOO=bar (echo hello)' > > > ksh -c '/usr/bin/env FOO=bar (echo hello)' > > > > > > is not valid > > > sh -c '/usr/bin/env FOO=bar echo

Re: [OMPI devel] Porting OpenMPI to a new system

Hello Ioannis, * Ioannis E. Venetis wrote on Wed, Apr 28, 2010 at 05:34:47PM CEST: > b) The cross-compilation environment should be run on a Linux x86_64 > system. The cross-compiler, libraries, etc are already working, which > means that only OpenMPI needs to be ported right now. We use this >

Re: [OMPI devel] 答复: 答复: Migrate the OpenMPI to VxWorks

* 张晶 wrote on Fri, Apr 16, 2010 at 04:50:21PM CEST: > I think I should switch the host now in the windows to the linux ,or I will > have little chance to build the autotool, Thank you for your advice ! autotools work just fine under Windows. For example, Cygwin or MinGW ship pre-built autotools

Re: [OMPI devel] Migrate the OpenMPI to VxWorks

* Ralph Castain wrote on Fri, Apr 16, 2010 at 05:35:37AM CEST: > I have not personally tried, but I am pretty sure that you can install > the autotools under VxWorks - have you tried to download the latest > autotool tarballs and build them? I don't know if that works well out of the box, but if

Re: [OMPI devel] RFC: ABI break between 1.4 and 1.5 / .so versioning

* Jeff Squyres wrote on Wed, Feb 17, 2010 at 11:51:42PM CET: > On Feb 17, 2010, at 3:05 PM, Ralf Wildenhues wrote: > > > > The issue is that if the user has to specify -static to their linker, > > > they *also* have to specify --ompi:static, or Bad Things will happen.

Re: [OMPI devel] configure question

Hello Greg, * Greg Watson wrote on Tue, Feb 16, 2010 at 07:03:30PM CET: > When I run configure under Snow Leopard (this is OMPI 1.3.4), I get the > following: > > checking if C and Fortran 77 are link compatible... no > ** > It

Re: [OMPI devel] RFC: Adding -DOPEN_MPI=1 to mpif77 and mpif90

* Jeff Squyres wrote on Thu, Feb 11, 2010 at 12:41:15PM CET: > On Feb 11, 2010, at 1:00 AM, Ralf Wildenhues wrote: > > * Jeff Squyres wrote on Wed, Feb 10, 2010 at 10:02:27PM CET: > > > WHAT: Add -DOPEN_MPI=1 to the mpif77 and mpif90 command lines > > > > It won't

Re: [OMPI devel] RFC: Adding -DOPEN_MPI=1 to mpif77 and mpif90

Hi Jeff, * Jeff Squyres wrote on Wed, Feb 10, 2010 at 10:02:27PM CET: > WHAT: Add -DOPEN_MPI=1 to the mpif77 and mpif90 command lines > But we can put -DOPEN_MPI=1 in the argv that the wrapper adds. This > seems like a safe way to add it; it makes no difference whether the > Fortran file is set

Re: [OMPI devel] Dynamic languages, dlopen() issues, and symbol visibility of libtool ltdl API in current trunk

As a workaround, Lisandro could just pre-seed the cache variables of the respective configure tests that come out wrong. ./configure lt_cv_dlopen_self=yes lt_cv_dlopen_self_static=yes HTH. Cheers, Ralf * Jeff Squyres wrote on Mon, Sep 21, 2009 at 02:45:28PM CEST: > Ick; I appreciate

Re: [OMPI devel] libtool issue with crs/self

Hello, * Josh Hursey wrote on Wed, Aug 05, 2009 at 04:51:59PM CEST: > I noticed that the "-fvisibility=hidden" option when passed to > libltdl will cause it to fail in its configure test for: > "checking whether a program can dlopen itself" > This is because the symbol they are trying to look

Re: [OMPI devel] trunk borked -- my fault

not bracket the AC_PROG_F77 call, as they should. What you should do is move these lines to the required macro as well. The patch below ought to fix up these issues, as well as the scope push macro for C++. For clarity, you could also put that in another, separate macro, and AC_REQUIRE that.

Re: [OMPI devel] Shared library versioning

* Jeff Squyres wrote on Sat, Jul 25, 2009 at 07:59:25PM CEST: > On Jul 25, 2009, at 12:59 PM, Iain Bason wrote: > >> We have talked many times about doing proper versioning for > >> OMPI's .so libraries (e.g., libmpi.so -- *not* our component DSOs). > > > >Forgive me if this has been hashed out,

[OMPI devel] faster autogen.sh

As part of a shameless advertising move I suggest this patch. While it won't make autogen.sh exactly fast, for me it shaves half a minute off its runtime. Cheers, Ralf HACKING: recommend parallel automake 1.11 execution. Index: HACKING

Re: [OMPI devel] Build failures on trunk? r21235

Hi Brian, * Brian W. Barrett wrote on Thu, May 14, 2009 at 08:22:58PM CEST: > > Actually, I think that was something else. Today, libopen-rte.la lists > libopen-pal.la as a dependency and libmpi.la lists libopen-rte.la. I had > removed the dependency of libmpi.la on libopen-pal.la because it

Re: [OMPI devel] Build failures on trunk? r21235

Hello, * Jeff Squyres wrote on Thu, May 14, 2009 at 07:56:24PM CEST: > On May 14, 2009, at 1:46 PM, Ralf Wildenhues wrote: > >> A more permanent workaround could be in OpenMPI to list each library >> that is used *directly* by some other library as a dependency. Sigh. > >

Re: [OMPI devel] Build failures on trunk? r21235

Hello, Ashley, did you rebootstrap with Debian's Libtool? They enable link_all_deplibs=no in their Libtool which changes some things and can cause issues like this. Can't hurt to open a Debian bug report about it (targeted against libtool) so they know this issue exists. Can you try working

Re: [OMPI devel] Fwd: RFC: proposed GPLv3 license exception draft

Hello Ralph, * Ralph Castain wrote on Sat, Apr 25, 2009 at 05:09:01PM CEST: > Just to be clear, Ralf - I'm not advocating that we change build > systems. I agree it has been a good relationship, and your participation > has been welcome and extremely helpful. Understood; and thanks! > My

Re: [OMPI devel] Fwd: RFC: proposed GPLv3 license exception draft

Hi Jeff, * Jeff Squyres wrote on Sat, Apr 25, 2009 at 01:27:24PM CEST: > We OMPI developers ask people to send the stdout/stderr of configure and > their config.log to us to help figure out problems > (http://www.open-mpi.org/community/help/). As I understand your > explanations, this is

Re: [OMPI devel] Fwd: RFC: proposed GPLv3 license exception draft

ave a problem when configure.ac and acinclude.m4 are from a non-GPL > project such as OMPI. > Ralf Wildenhues, > While I believe Jeff is the one that brought this discussion to > ompi-devel, I know you've posted on ompi-devel in the past. Are you > seeing this? Yes, I am casually reading th

Re: [OMPI devel] [OMPI svn-full] svn:open-mpi r20568

Hello, * Jeff Squyres wrote on Tue, Feb 17, 2009 at 07:01:01PM CET: > On Feb 17, 2009, at 11:18 AM, George Bosilca wrote: > >> I guess that if the free function supports the NULL pointer we should >> do the same... > > I'll agree with that if we know for sure that free(NULL) is universally >

Re: [OMPI devel] [Pkg-openmpi-maintainers] Building with rpath disabled

Hello Jeff, * Jeff Squyres wrote on Tue, Jan 13, 2009 at 03:39:28PM CET: > On Jan 13, 2009, at 4:54 AM, Manuel Prinz wrote: >> >> You have to pass --disable-rpath explicitely. Building with rpath is >> still the default. I verified by building without passing any option >> to configure and the

Re: [OMPI devel] make dependency problem?

Hello Eugene, Jeff, the interesting data points here would be the dependency tracking scheme selected by automake (CCDEPMODE in ompi/mca/bml/r2/Makefile), with and without --enable-dependency-tracking passed to configure. Also, the contents of ompi/mca/bml/r2/.deps/bml_r2.Plo, after ensuring

Re: [OMPI devel] Forwarding SIGTSTP and SIGCONT

Hello Rolf, * Rolf Vandevaart wrote on Fri, Dec 05, 2008 at 08:00:42PM CET: > > One problem is that with SIGTSTP no longer delivering a stop signal to > mpirun, one cannot CTRL-Z at their terminal to stop mpirun. I am trying > to figure out how big a problem that is. Why not first deal with

Re: [OMPI devel] RFC: Add SunStudio/Libtool helper script for post-configure

Hello Ralph, * Ralph Castain wrote on Mon, Nov 24, 2008 at 02:39:13PM CET: > On Nov 23, 2008, at 1:19 AM, Ralf Wildenhues wrote: >> >> While I suppose your patch works, I think in similar situations, >> OpenMPI has resorted to patching input files to configure (like >&

Re: [OMPI devel] RFC: Add SunStudio/Libtool helper script for post-configure

* Ethan Mallove wrote on Fri, Nov 21, 2008 at 09:01:56PM CET: > On Fri, Nov/21/2008 01:02:12PM, Ralf Wildenhues wrote: > > IMHO OpenMPI can use > > the solaris_use_stlport4=yes until such a functionality is in place. > > Nice. This workaround works. I don't suppose there's a

Re: [OMPI devel] RFC: Add SunStudio/Libtool helper script for post-configure

Hello Ethan, all, * Ethan Mallove wrote on Thu, Nov 20, 2008 at 10:33:08PM CET: > On Thu, Nov/20/2008 07:00:31PM, Ralf Wildenhues wrote: > > > > Ah, ok. Please try the patch below instead of yours, thanks. > > Your patch seems to work, though I get this: > >libt

Re: [OMPI devel] RFC: Add SunStudio/Libtool helper script for post-configure

Our previous mails overlapped, sorry about that. * Ethan Mallove wrote on Thu, Nov 20, 2008 at 06:52:09PM CET: > > The above appears to be looking for a Fortran version string from the > C compiler, but it wouldn't match our version string anyway: > > $ f90 -V > f90: Sun Ceres Fortran 95

Re: [OMPI devel] RFC: Add SunStudio/Libtool helper script for post-configure

Hello Ethan, * Ethan Mallove wrote on Wed, Nov 19, 2008 at 09:24:16PM CET: > > I'm seeing the same issue with the faulty "wl" Libtool > variable in 2.2.6 with Linux SunStudio: That's really weird, because this change should have fixed that:

Re: [OMPI devel] RFC: merge windows branch into trunk

I'm probably going to come across as ignorant, and I'm obviously biased on this matter, but: * Tim Mattox wrote on Thu, Nov 20, 2008 at 02:53:13PM CET: > > Although I don't use windows myself, I appreciate your > and others' efforts to expand the number of platforms > we can run on. Great work!

Re: [OMPI devel] RFC: Add SunStudio/Libtool helper script for post-configure

Hello Ethan, * Ethan Mallove wrote on Wed, Nov 19, 2008 at 04:11:23PM CET: > There are a couple issues with SunStudio and Libtool: Which Libtool version are you using? If not 2.2.2 or newer, then please retry with 2.2.6. If the problem persists, then we should fix Libtool rather than patching

Re: [OMPI devel] RFC: libopen-rte --> libompi-rte

* Jeff Squyres wrote on Thu, Nov 06, 2008 at 08:48:44PM CET: > On Nov 6, 2008, at 2:42 PM, Ralf Wildenhues wrote: > >> Hmm, OpenMPI seems not to use versioning for its shared libraries. > > That was on the to-do list for this release, but it just didn't happen. > :-\ Oh

Re: [OMPI devel] RFC: libopen-rte --> libompi-rte

Hello, * Jeff Squyres wrote on Thu, Nov 06, 2008 at 07:49:23PM CET: > On Nov 6, 2008, at 1:13 PM, Brian W. Barrett wrote: > >>> WHY: ORTE is really quite specific to OMPI. We decided long ago >>> that ORTE would not split off from OMPI, and it has been >>> specifically tailored for OMPI.

Re: [OMPI devel] adding new functions to a BTL

Hello Jeff, Eugene, > Jeff Squyres wrote: > >> We use lt_dlopen() to open the plugins (Libtool's wrapper for a >> portable dlopen). It opens all plugins (DSOs) in a private scope. >> That private scope is kept deep in the OPAL MCA base and not exposed >> elsewhere in the code base. So

Re: [OMPI devel] Should visibility and memchecker abort configure?

Hello, if you allow me my 2 cents: At configure time, it is possible to distinguish between several different user inputs: - the user typed --enable-foo, - the user typed --disable-foo or --enable-foo=no, - the user typed --enable-foo=ARG (ARG is available for further inspection), - the user

Re: [OMPI devel] gdb libmpi.dylib on Leopard

* Aurélien Bouteiller wrote on Fri, Sep 19, 2008 at 08:02:40PM CEST: > Thanks Ralf for the support. I upgraded to libtool 2.2.6 and it didn't > solved the problem though. Still looking for somebody to confirm that > its working or not working on their Mac. Did you rerun autogen.sh? All I

Re: [OMPI devel] Upgrade GNU auto tools?

Hello OpenMPI developers, on Darwin/OS X, recent Libtool has some debugging symbols issue fixed. I think that was even raised on this list a short while ago. Also, an issue with recent Intel compilers on Linux has been fixed. Absoft support is not yet in Libtool, but Lahey is. Hope that helps.

Re: [OMPI devel] gdb libmpi.dylib on Leopard

Hello Aurélien, * Aurélien Bouteiller wrote on Wed, Sep 17, 2008 at 06:32:11PM CEST: > I have been facing a weird problem for several month now (I guess since I > upgraded from Tiger to Leopard). I am unable to debug Open MPI using gdb > on my mac. The problem comes from gdb not being able to

Re: [OMPI devel] MPI ABI on Linux

* Jeff Squyres wrote on Tue, Sep 09, 2008 at 03:07:24PM CEST: >> On Sep 9, 2008, at 6:23 AM, Jeff Squyres wrote: >>> On Sep 9, 2008, at 2:45 AM, Ralf Wildenhues wrote: >>> >>>> An MPI ABI will have to be versioned in >>>> the same way that th

Re: [OMPI devel] MPI ABI on Linux

Hello Jeff, all, if you allow me my two cents, * Jeff Squyres wrote on Mon, Sep 08, 2008 at 08:44:28PM CEST: > > At the MPI Forum meeting in Dublin, the MPI ABI meeting was... er... > shall we say, "spirited." :-) Both the benefits and drawbacks of an > MPI ABI are widely contended (it's a

Re: [OMPI devel] TRUNK error ( MAN page ) since r19120

* Tim Mattox wrote on Mon, Aug 04, 2008 at 03:11:20PM CEST: > As this thread is making clear, not everyone saw and/or heeded the > note that we were upgrading the GNU autotools used for building Open MPI's > nightly tarballs. See http://www.open-mpi.org/svn/building.php the the > version >

[OMPI devel] some configury nits

Hello, I tried to build OpenMPI trunk on my Debian stable/testing mix, and to make things more interesting, today my /bin/sh is dash, and while gcc is version 4.3.1, g++ remained at 4.1.3. I needed the following patch in order to get configure to finish ("test ... == ..." is a bash extension).

Re: [OMPI devel] Need v1.3 RM ruling (was: Help on building openmpi with "-Wl, --as-needed -Wl, --no-undefined")

* George Bosilca wrote on Thu, Jul 24, 2008 at 02:44:04PM CEST: > I was hoping we can get some hints/help from Ralf, but unfortunately his > email address is not CC to the emails and I don't know if he's reading > the devel mailing list. I'll resend my email with. I read the list, but reading

Re: [OMPI devel] Need v1.3 RM ruling (was: Help on building openmpi with "-Wl, --as-needed -Wl, --no-undefined")

* Brian Barrett wrote on Thu, Jul 24, 2008 at 02:28:45PM CEST: > When I looked at the same problem in LAM, I couldn't get the > dependencies right between libraries when only one makefile was used. It > worked up until I would do a parallel build, then would die because the > libraries weren't

Re: [OMPI devel] Help on building openmpi with "-Wl, --as-needed -Wl, --no-undefined"

Hi Jeff, * Jeff Squyres wrote on Wed, Jul 23, 2008 at 03:54:50PM CEST: > > Is the attached patch what you're talking about? > > If so, I'll commit to trunk, v1.2, and v1.3. Can you verify that it work with a pristine build? The dependencies as such look sane to me, also the cruft removal, but I

Re: [OMPI devel] Help on building openmpi with "-Wl, --as-needed -Wl, --no-undefined"

* Funda Wang wrote on Sun, Jul 20, 2008 at 05:29:57AM CEST: > I'm currently building openmpi 1.2.6 under Mandriva cooker, and its > default LDFLAGS is "-Wl,--as-needed -Wl,--no-undefined". > > But openmpi 1.2.6 builds failed with: > libtool: link: g++ -shared -nostdlib >

Re: [OMPI devel] autogen error

Hello Leonardo, * Leonardo Fialho wrote on Thu, Jun 19, 2008 at 04:29:30PM CEST: > [Running] aclocal -I config > /usr/local/bin/m4:config/mca_no_configure_components.m4:9: ERROR: end of > file in string > autom4te: /usr/local/bin/m4 failed with exit status: 1 > aclocal: autom4te failed with

Re: [OMPI devel] libdir not propagated to contrib/vt/vt ??

Hello, * David Daniel wrote on Wed, Jun 11, 2008 at 11:34:23PM CEST: > Building against recent heads (r18643) it appears that libdir (as set > by ./configure --prefix=$PREFIX --libdir=$PREFIX/lib64 for example) is > not propagated to ompi-trunk/contrib/vt/vt. ompi/contrib/vt/configure.m4 is

Re: [OMPI devel] some Makefile.am questions

* Jeff Squyres wrote on Fri, Jun 06, 2008 at 03:21:03AM CEST: > On Jun 4, 2008, at 5:15 PM, Ralf Wildenhues wrote: > > 1) This is from test/Makefile.am: > > > > --- snip --- > > # This should be libsupport.a, not libsupport.la. Automake doesn't > > # support chec

Re: [OMPI devel] parallel make install

Hello Ralph, * Ralph Castain wrote on Tue, Jun 03, 2008 at 11:59:07PM CEST: > Very interesting. Don't know if it's the same problem, but I noted an issue > quite a while ago where make -jN all/install would fail when traversing > opal. I built a workaround that was just a script that does make

Re: [OMPI devel] parallel make install

Hi Jeff, * Jeff Squyres wrote on Tue, Jun 03, 2008 at 11:11:32PM CEST: > ERROR: Command returned a non-zero exist status >make -j 4 distcheck [...] > Making install in etc > make[3]: Entering directory >

[OMPI devel] parallel make install

Hello there, a change recently mentions this: | r18552 | timattox | 2008-05-30 06:39:48 +0200 (Fri, 30 May 2008) | 4 lines | Changed paths: |M /trunk/contrib/nightly/create_tarball.sh | | Apparently "make -j 4 distcheck" has a race condition when "installing" in | parallel. Remove the "-j

Re: [OMPI devel] r18551 - brakes ob1 compilation on Sles10

* Pavel Shamis (Pasha) wrote on Mon, Jun 02, 2008 at 02:25:13PM CEST: > r18551 brakes ompi compilation on SLES10 gcc 4.1.0. > > I got follow error on my systems > (http://www.open-mpi.org/mtt/index.php?do_redir=672 ): [...] >

Re: [OMPI devel] Fix for XLC + libtool issue

* Jeff Squyres wrote on Fri, Apr 25, 2008 at 01:54:39PM CEST: > On Apr 25, 2008, at 7:40 AM, Ralf Wildenhues wrote: > > > <http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/3985> > Wow -- those timings are impressive! Quoting that URL (OMPI is [1]): >

[OMPI devel] 3 test failures

Hello, I've just stumbled over three testsuite failures on GNU/Linux x86, with an out-of-tree build (mkdir build; cd build; ../ompi_trunk/configure -C). Hope I'm not completely off-topic here... Cheers, Ralf PASS: ompi_bitmap

[OMPI devel] getting config.guess/config.sub from upstream

Hello, Please note that the CVS repo for config.guess and config.sub is outdated, development has moved to use git. ompi_trunk/config/distscript.csh could be adjusted to pull from and likewise for config.sub.

Re: [OMPI devel] more vt woes

Hallo Matthias, * Matthias Jurenz wrote on Wed, Feb 13, 2008 at 01:49:41PM CET: > On Di, 2008-02-12 at 11:27 -0500, George Bosilca wrote: > > > I keep getting some warnings when I compile with gcc-4.2 on MAC OS X. > > > > tools/compwrap/Makefile.am:38: `CXXFLAGS' is a user variable, you > >

[OMPI devel] Fixlet for config/ompi_contrib.m4

Hello, please apply this patch, to make future contrib integration just a tad bit easier. I verified that the generated configure script is identical, minus whitespace and comments. Cheers, Ralf 2008-02-11 Ralf Wildenhues <ralf.wildenh...@gmx.de> * config/ompi_cont

Re: [OMPI devel] VT integration: make distclean problem

* Josh Hursey wrote on Mon, Feb 11, 2008 at 07:31:25PM CET: > I've been noticing another problem with the VT integration. If you do > a "./configure --enable-contrib-no-build=vt" a subsequent 'make > distclean' will fail in contrib/vt. The 'make distclean' will succeed > with VT enabled

Re: [OMPI devel] More VT warnings

* Tim Prins wrote on Fri, Feb 01, 2008 at 04:09:31PM CET: > > Note that this indicates that the file vt_metric_papi.c is being > compiled *3* times. I am not using a parallel make here. Any ideas why > it is compiling 3 times? The file is listed as source file to four different libraries, and

Re: [OMPI devel] vt compiler warnings and errors

* Jeff Squyres wrote on Thu, Jan 31, 2008 at 07:10:36PM CET: > Ah -- I didn't notice this before -- do you have a configure script > committed to SVN? If so, this could be the problem. > > On Do, 2008-01-31 at 08:09 -0500, Tim Prins wrote: [...] > >> [tprins@sif test]$ make clean > >> > >>

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

Hello, * Brian W. Barrett wrote on Thu, Jan 24, 2008 at 09:43:12PM CET: > Automake forces v7 mode so that Solaris tar can untar the tarball, IIRC. You can choose how it should behave:

Re: [OMPI devel] configure patch

* Jeff Squyres wrote on Sat, Jan 19, 2008 at 02:03:02AM CET: > On Jan 8, 2008, at 6:53 PM, Elan Ruusamäe wrote: > > > > please consider applying this patch > > http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES/openmpi-ksh.patch > > > > fixes build process when /bin/sh is not bash (for example

Re: [OMPI devel] small configure cache variable bug

* Ralf Wildenhues wrote on Thu, Oct 11, 2007 at 11:36:53PM CEST: > > * config/ompi_check_visibility.m4 (OMPI_CHECK_VISIBILITY): > Rename ompi_cv_cc_fvisibility to ompi_vc_cc_fvisibility, so > that it will be cached. Of course then I get it wrong myself. I me

[OMPI devel] small configure cache variable bug

Hello Open MPI Developers, Here's a small patch to fix a misnamed cache variable. The next Autoconf version will issue a warning for typos like these, which is how I found this. Cheers, Ralf * config/ompi_check_visibility.m4 (OMPI_CHECK_VISIBILITY): Rename

Re: [OMPI devel] FreeBSD Support?

Hello Karol, * Karol Mroz wrote on Wed, Sep 19, 2007 at 07:23:50PM CEST: > When running the autogen.sh script as non-root, I see the following error: [...] > autom4te-2.61: cannot open configure: Permission denied [...] > After some searching, it would appear that this is an autoconf issue

Re: [OMPI devel] [RFC] Upgrade to newer libtool 2.1 snapshot

Hi Jeff, * Jeff Squyres wrote on Fri, Aug 03, 2007 at 10:33:51PM CEST: > WHAT: Upgrade to a newer Libtool 2.1 nightly snapshot (we are > currently using 1.2362 2007/01/23) for making OMPI tarballs. > > WHY: https://svn.open-mpi.org/trac/ompi/ticket/982 is fixed by newer > Libtool snapshots

Re: [OMPI devel] Multi-environment builds

* Jeff Squyres wrote on Tue, Jul 10, 2007 at 01:28:40PM CEST: > On Jul 10, 2007, at 2:42 AM, Ralf Wildenhues wrote: > > >> 1. The most obvious one (to me, at least) is to require that > >> people provide > >> "--with-xx" when they build the system.

Re: [OMPI devel] Multi-environment builds

Hello Ralph, * Ralph Castain wrote on Tue, Jul 10, 2007 at 03:51:06AM CEST: > > The problem is that our Open MPI build system automatically detects the > presence of those libraries, builds the corresponding components, and then > links those libraries into our system. Unfortunately, this causes

Re: [OMPI devel] Build system changes

* Ralph Castain wrote on Thu, Nov 30, 2006 at 04:12:16PM CET: > That could be the problem. I had to update automake, and unfortunately > Darwin Ports hasn't reached that level yet. So I had to build and install > automake by hand under my own bin directory. But libtool etc are all in > /usr/bin.

Re: [OMPI devel] Build system changes

> * Ralph Castain wrote on Thu, Nov 30, 2006 at 03:55:05PM CET: > > > > configure.in:1994: warning: macro `AM_PROG_LIBTOOL' not found in library > > [Running] autoheader > > [Running] autoconf > > configure.in:1997: error: possibly undefined macro: AM_PROG_LIBTOOL > > If this token and

Re: [OMPI devel] Build system changes

* Ralph Castain wrote on Thu, Nov 30, 2006 at 03:55:05PM CET: > > I updated this morning and hit a few problems. I found I was using autoconf > 2.60, so I had to update to automake 1.10 as you indicated. However, once I > did that, I still couldn't build due to the following errors: > >

[OMPI devel] help config.status to not mess up substitutions

. :-) In unrelated news, I tested Automake 1.10 with OpenMPI, and it saves about 15s of config.status time, and about half a minute of `make dist' time on my system. Some pending Fortran changes have only made it into Automake after 1.10 was released. Cheers, Ralf 2006-10-23 Ralf Wildenhues

Re: [OMPI devel] Issues with 1.2 and intel/portland compilers

Hello Orion, * Orion Poplawski wrote on Thu, Oct 12, 2006 at 06:57:04PM CEST: > I've been trying to build the openmpi 1.2 branch with the Intel and > Portland Fortran compilers and was having trouble using their > -i-static/-Bstatic_pgi options. Your report touches several issues: > I'm not

Re: [OMPI devel] [Open MPI] #334: Building with Libtool 2.1a fails to run OpenIB BTL

Hello, * Open MPI wrote on Wed, Sep 06, 2006 at 01:00:00PM CEST: > #334: Building with Libtool 2.1a fails to run OpenIB BTL >Are you testing uninstalled or installed programs/libraries? > > Installed. > >If you are testing an uninstalled program: does libtool generate a shell >

Re: [OMPI devel] OpenMPI not conforming with the C90 spec?

* Ralph H Castain wrote on Mon, Aug 21, 2006 at 02:39:51PM CEST: > > It sounds, therefore, like we are now C99 compliant and no longer C90 > compliant at all? Well, a compiler supporting C90 plus 'long long' as an extension would still be ok. Surely, that's not "strictly C90". But from glancing

[OMPI devel] exit declaration in configure tests

Revision 11268 makes me curious: |M /trunk/config/ompi_setup_cxx.m4 | | Reorder the C++ compiler discovery stages. Check first the compiler vendor | before checking if we are able to compile the test program. This is required | for windows as the C++ conftest.c file generated by configure

Re: [OMPI devel] OpenMPI not conforming with the C90 spec?

Hello Adrian, Jonathan, * Adrian Knoth wrote on Sat, Aug 19, 2006 at 08:38:15PM CEST: > On Thu, Aug 17, 2006 at 11:48:44PM +0100, Jonathan Underwood wrote: > > > Compiling a file with the gcc options -Wall and -pedantic gives the > > following warning: > > mpi.h:147: warning: ISO C90 does not

[OMPI devel] robustify config against picky compiler flags

Autoconf has recently seen some effort to robustify configure tests against picky GCC warning settings. There is quite a way to go yet, but it may still be useful to move the OpenMPI configury in that direction, too. So below is a patch that picks some low-hanging fruit on the way to make

[OMPI devel] tests/datatype: srandomdev

Hello everyone, Currently 'make check' is failing for me in the tests/datatype directory, because my system (GNU/Linux, glibc 2.3.6) doesn't provide a srandomdev function, called in checksum.c. I believe it's BSD specific; if you need it, I guess you could add a configure time check for it.

[OMPI devel] some configury update

The following patches fix two rather nasty issues with configury, and one missing bit of GCS update. All changes should be backwards compatible (in the sense that they will work with older Autoconf versions), the first two are necessary for correct functioning with Autoconf-2.59 already, but the

Re: [OMPI devel] bug in Makefile.in

* Dries Kimpe wrote on Mon, May 08, 2006 at 08:46:49PM CEST: > > 2) The $ in grep 'pvfs$' was added by me as a temporary hack to > prevent it from building pvfs along with pvfs2. > It's not a good solution anyway, because $FILE_SYSTEM contains things > as "nfs ufs pvfs pvfs2" > > Really,

Re: [OMPI devel] typo in ompi/mca/io/romio/configure.m4?

Hi Brian, Dries, * Brian Barrett wrote on Mon, May 08, 2006 at 01:43:38PM CEST: > > However, we really *should* abort configure and warn the user if -- > enable-io-romio is given and ROMIO fails to configure. I will fix > this with the LDFLAGS fix. I'll let you know when the fixes become

  1   2   >