On Fri, Sep 14, 2012 at 09:37:48AM +0200, Michael Olbrich wrote:
> On Fri, Sep 14, 2012 at 12:26:19AM +0200, Tim Sander wrote:
> > ----------------------------
> > target: systemd.extract.post
> > ----------------------------
> > 
> > pkg_patch_autogen: 'ptxdist-2012.09.0/patches/systemd-189/autogen.sh'
> > 
> > configure.ac:315: warning: macro `AM_PATH_LIBGCRYPT' not found in library
> 
> This is not the Problem. I see it too, but patches/systemd-189/autogen.sh
> explicitly does not call autoconf to avoid the dependency.
> 
> > docs/gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL
> > docs/gudev/Makefile.am:98:   `docs/gtk-doc.make' included from here
> > docs/gtk-doc.make:55: GTK_DOC_BUILD_HTML does not appear in AM_CONDITIONAL
> > docs/gudev/Makefile.am:98:   `docs/gtk-doc.make' included from here
> > docs/gtk-doc.make:60: GTK_DOC_BUILD_PDF does not appear in AM_CONDITIONAL
> > docs/gudev/Makefile.am:98:   `docs/gtk-doc.make' included from here
> > docs/gtk-doc.make:7: GTK_DOC_USE_LIBTOOL does not appear in AM_CONDITIONAL
> > docs/libudev/Makefile.am:92:   `docs/gtk-doc.make' included from here
> > docs/gtk-doc.make:55: GTK_DOC_BUILD_HTML does not appear in AM_CONDITIONAL
> > docs/libudev/Makefile.am:92:   `docs/gtk-doc.make' included from here
> > docs/gtk-doc.make:60: GTK_DOC_BUILD_PDF does not appear in AM_CONDITIONAL
> > docs/libudev/Makefile.am:92:   `docs/gtk-doc.make' included from here
> 
> This is the problem. But I don't know why this happens. These are
> include $(top_srcdir)/docs/gtk-doc.make
> And the file is part of the systemd-189 source package. Does this file not
> exist for you?

Ok, issue found and fixed. Please try the latest ptxdist git.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
[email protected]

Reply via email to