On Fri, Mar 21, 2008 at 8:36 PM, Jeff Squyres <jsquyres_at_[hidden]> wrote:
> 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).
I attached my current configure.ac (now test3) which uses trunk and
libtool and the 3-argument version of PLPA_INIT() + the 1-argument
version of PLPA_INCLUDED, but with this I get the deprecated warning,
I will switch back to the 0-argument version.
>
> 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.
I would expect that autoheader dive into SUBDIRS.
>
> 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)
I had the same idea, see the commented line to run autogen.sh inside
plpa-1.1 inside the topdir autogen.sh
> - putting plpa_config.h.in in PLPA's SVN doesn't seem right
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?
Don't know, is my first experience with svn:externals. I thought it
would be easer to keep it up-to-date with upstream plpa
Bert
>
>
>
> --
> Jeff Squyres
> Cisco Systems
|