From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: build-sys: minor issues
Date: Wed, 4 Jun 2014 11:33:14 +0200 [thread overview]
Message-ID: <201406041133.15174.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20140603104249.GQ9000@x2.net.home>
On Tuesday 03 June 2014, Karel Zak wrote:
> On Mon, Jun 02, 2014 at 02:33:38AM +0200, Ruediger Meier wrote:
> >
> > Another issue:
> >
> > 3. --enable-gtk-doc does not work in out-of-tree build:
> > [...]
>
> Fixed.
Thanks, it works.
For testing I've run it several times on travis farm from within
distcheck. Unfortunately docs still fail randomly in 1 of 10 runs.
$ make distcheck
[...]
make[1]: Entering directory
`/home/travis/build/rudimeier/util-linux/libblkid/docs'
make[1]: Circular scan-build.stamp <- libblkid-sections.txt dependency
dropped.
GEN scan-build.stamp
[...]
Making all in libblkid/docs
make[3]: Entering directory
`/home/travis/build/rudimeier/util-linux/util-linux-2.24.913-183e/_build/libblkid/docs'
gtk-doc: Preparing build
cp: cannot create regular file `./libblkid-sections.txt': Permission
denied
make[3]: *** [scan-build.stamp] Error 1
Note that this "Permission denied" also happens in successful runs.
Here full logs of good and bad run:
https://s3.amazonaws.com/archive.travis-ci.org/jobs/26722236/log.txt
https://s3.amazonaws.com/archive.travis-ci.org/jobs/26722239/log.txt
Don't know whether this happens only out-of-tree or because of parallel
build. "Permission denied" in distcheck always smells like writing to
srcdir. Maybe you have already an idea what it could be or I would just
add debug messages and watch it.
cu,
Rudi
next prev parent reply other threads:[~2014-06-04 9:33 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
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 [this message]
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=201406041133.15174.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--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