Open MPI logo

PLPA Users' Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all PLPA Users mailing list

Subject: Re: [PLPA users] plpa in included mode
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-03-21 15:36:54


On Mar 21, 2008, at 3:14 PM, Bert Wesarg wrote:

>> Can you give it a whirl?
> Sure, I did, the warning is gone, but this message is still there,
> just shorter:
>
> configure.ac:17: required file `plpa/src/libplpa/plpa_config.h.in'
> not found
>
> it prevents the generation of plpa/src/libplpa/Makefile.in

With your test2, if I replace the svn co with the trunk (instead of
the v1.1 branch), I can replicate the error. Hmm.

Digging into this, I think I understand what's going on, but am unsure
of the Right way to fix it.

1. Sidenote: You might want to update your PLPA_INIT call to be:

    PLPA_INIT(plpa-v1.1, plpa_happy=yes, plpa_happy=no)

Note the new first argument.

2. Sidenote: I think you need something about libtool in your
configure.ac; I get errors (but didn't investigate).

3. The plpa_config.h.in exists in PLPA tarballs because tarballs are
SVN+bootstrapping.

4. plpa_config.h.in exists in OMPI's SVN because I embedded the PLPA
tarball, not via svn:external. As an embedded tarball, it's
appropriate to keep the tarball bootstrapping around (such as
plpa_config.h.in).

5. The plpa_config.h.in file does *not* exist in SVN because it is a
generated file (by autoheader), and is therefore not appropriate.

Hence, by #5, you can see why automake is failing. So what's the
right answer? I'm not sure:

- running PLPA's autogen.sh from the svn checkout/export seems to be
overkill (but it works)
- putting plpa_config.h.in in PLPA's SVN doesn't seem right

I guess it really comes down to the fact that I had envisioned
embedding tarballs, not via svn:external. What do other projects do
that both use the GNU autotools and allow embedding via svn:external?

-- 
Jeff Squyres
Cisco Systems