From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: more fixes for out of tree builds
Date: Mon, 09 Nov 2009 23:13:17 +0000 [thread overview]
Message-ID: <20091109231316.GS5610@nb.net.home> (raw)
In-Reply-To: <20091109034609.GA28618@bongo.bofh.it>
On Mon, Nov 09, 2009 at 03:19:09PM +0100, Marco d'Itri wrote:
> On Nov 09, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > On Mon, Nov 9, 2009 at 04:46, Marco d'Itri <md@linux.it> wrote:
> > > These are needed to support out of tree builds,
> > Why isn't "make distcheck" failing then?
> Did you try it with a read only source tree?
Yes, be careful with "make distcheck", it does not check for all
problems. Don't forget that "make distcheck" works with
source code from tarball and for example gtk-doc by default add many
generated files to the tarball. The best test is:
git clean -xfd
./autogen.sh
mkdir -p ../build
cd ../build
./configure
make
.. and try "ls -la ../udev/libudev/docs/ | wc -l" before and after the
make command :-)
> > Hmm, that looks a bit too weird, doesn't it?
> > > +srcdir := $(builddir)
> Maybe, but without something like that the building process will create
> files in the source tree.
> Ubuntu uses a similar workaround, this is a known gtk-doc bug.
:-(
The number of non-gtk libraries is slowly growing. It would be nice
to found a real solution... fix gtk-doc or found something better
than gtk-doc.
Karel
--
Karel Zak <kzak@redhat.com>
next prev parent reply other threads:[~2009-11-09 23:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 3:46 more fixes for out of tree builds Marco d'Itri
2009-11-09 11:18 ` Kay Sievers
2009-11-09 14:03 ` Dan Nicholson
2009-11-09 14:19 ` Marco d'Itri
2009-11-09 22:43 ` Karel Zak
2009-11-09 23:13 ` Karel Zak [this message]
2009-11-10 5:40 ` Kay Sievers
2009-11-10 9:01 ` Martin Pitt
2009-11-10 10:36 ` Karel Zak
2009-11-10 11:12 ` Martin Pitt
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=20091109231316.GS5610@nb.net.home \
--to=kzak@redhat.com \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.