From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: Re: build-sys: minor issues
Date: Mon, 2 Jun 2014 02:33:38 +0200 [thread overview]
Message-ID: <201406020233.39094.sweet_f_a@gmx.de> (raw)
In-Reply-To: <201406020056.17074.sweet_f_a@gmx.de>
On Monday 02 June 2014, Ruediger Meier wrote:
> I have two minor issues with our build-sys:
Another issue:
3. --enable-gtk-doc does not work in out-of-tree build:
$ mkdir build
$ cd build
$ ../configure --enable-gtk-doc
$ make V=1
[...]
gtkdoc-mkhtml --path="/home/rudi/devel/util-linux/build/libmount/docs:/home/rudi/devel/util-linux/build/libmount/docs/xml:/home/rudi/devel/util-linux/build/../libmount/docs"
\
\
libmount \
/home/rudi/devel/util-linux/build/../libmount/docs/libmount-docs.xml
/home/rudi/devel/util-linux/build/libmount/docs/version.xml:1: parser
error : Start tag expected, '<' not found
2.24.900-7afc22
^
/home/rudi/devel/util-linux/build/../libmount/docs/libmount-docs.xml:59:
element include: XInclude error : could not
load /home/rudi/devel/util-linux/libmount/docs/xml/version.xml, and no
fallback was found
make[2]: *** [html-build.stamp] Error 6
make[2]: Leaving directory
`/home/rudi/devel/util-linux/build/libmount/docs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/rudi/devel/util-linux/build'
make: *** [all] Error 2
BTW maybe we could consider about adding these docs to dist tarball to
not bother users with gtk-doc deps? (But I know then it's even more
complicated to rebuild cleanly in builddir when the existing one in
dist srcdir is outdated.)
cu,
Rudi
next prev parent reply other threads:[~2014-06-02 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 22:56 build-sys: minor issues Ruediger Meier
2014-06-02 0:33 ` Ruediger Meier [this message]
2014-06-02 9:48 ` Karel Zak
2014-06-02 11:05 ` Ruediger Meier
2014-06-03 10:42 ` Karel Zak
2014-06-04 9:33 ` Ruediger Meier
2014-06-02 9:42 ` Karel Zak
2014-06-02 10:33 ` Ruediger Meier
2014-06-03 11:27 ` Karel Zak
2014-06-03 19:46 ` Benno Schulenberg
2014-06-04 8:38 ` Karel Zak
2014-06-03 13:09 ` Ruediger Meier
2014-06-04 9:26 ` Karel Zak
2014-06-04 9:48 ` Ruediger Meier
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=201406020233.39094.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.org \
/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