From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [calxeda:ubuntu-quantal 99/299] make[4]: *** No rule to make target `ubuntu/include/linux/aufs_type.
Date: Sat, 29 Sep 2012 11:35:27 +0000 [thread overview]
Message-ID: <20120929113527.GB8674@localhost> (raw)
Hi Andy,
FYI, kernel build failed on
tree: git://sources.calxeda.com/kernel/linux.git ubuntu-quantal
head: c07f1571f9b6e609109d50bd6ba2b2547e873614
commit: 41f493c5f0028c3268a9c92916305e0cf48048c9 [99/299] UBUNTU: ubuntu: AUFS -- include the aufs_types.h file in linux-libc-headers
config: x86_64-allmodconfig
These errors are then fixed by some later commit and only hurts bisectability.
If you don't care about bisectability of your tree, please let me know. Thanks!
All error/warnings:
make[4]: *** No rule to make target `ubuntu/include/linux/aufs_type.h', needed by `usr/include/linux/.install'.
make[4]: Target `__headersinst' not remade because of errors.
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-09-29 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120929113527.GB8674@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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.