From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: more fixes for out of tree builds
Date: Mon, 09 Nov 2009 14:19:09 +0000 [thread overview]
Message-ID: <20091109141909.GA13453@bongo.bofh.it> (raw)
In-Reply-To: <20091109034609.GA28618@bongo.bofh.it>
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?
> 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.
--
ciao,
Marco
next prev parent reply other threads:[~2009-11-09 14:19 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 [this message]
2009-11-09 22:43 ` Karel Zak
2009-11-09 23:13 ` Karel Zak
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=20091109141909.GA13453@bongo.bofh.it \
--to=md@linux.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).