From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2012.09.0 released
Date: Fri, 14 Sep 2012 09:37:48 +0200 [thread overview]
Message-ID: <20120914073748.GF2365@pengutronix.de> (raw)
In-Reply-To: <201209140026.19915.tim01@vlsi.informatik.tu-darmstadt.de>
Hi,
On Fri, Sep 14, 2012 at 12:26:19AM +0200, Tim Sander wrote:
> I just tried to build a raspberry pi ptxdist image with not so stellar success
> with ptxdist-2012-09.0:
This is really strange.
> ----------------------------
> 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?
> make: *** [/bulk/baustelle/raspberry/OSELAS.BSP-fga-
> Raspberry-2011.11.0/platform-RaspberryPi/state/systemd.extract.post] Error 1
>
> First i thought that there's a missing dependency for libgcrypt which was not
> selected. So i targetinstalled it but the error is still there and my
> autotools foo is not sufficient and/or i am probably to tired to take a look.
You'd need host-libgcrypt but I avoided this by not calling autconf.
> There are some special rules which i will attach as also the config files.
>
> The build has been working with ptxdist-2012-07-0 so the project can't ptxdist
> project can't be to bad.
I'm pretty sure this is not caused by the ptxconfig.
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
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-09-14 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 11:55 Michael Olbrich
2012-09-13 22:26 ` Tim Sander
2012-09-14 7:37 ` Michael Olbrich [this message]
2012-09-19 8:48 ` Michael Olbrich
2012-09-14 12:44 ` Alexander Dahl
2012-09-14 13:28 ` Michael Olbrich
2012-09-15 1:48 ` Tim Sander
2012-09-16 13:21 ` Michael Olbrich
2012-09-15 1:39 ` Tim Sander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120914073748.GF2365@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox