From: Sean Fu <fxinrong@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Fail to build tools/all
Date: Tue, 3 May 2016 12:03:27 +0800 [thread overview]
Message-ID: <20160503040317.GA6274@linux-dunz.site> (raw)
In-Reply-To: <1585171.cPeXrju8v9@skinner>
On Mon, May 02, 2016 at 12:20:08PM +0200, Thomas Renninger wrote:
> On Sunday, May 01, 2016 01:11:33 PM Sean Fu wrote:
> > Hi guys:
> > I encountered a build error when running "make V=1 tools/all".
> > Shall we write a patch to fix it?
>
> This is not a bug.
>
> > The following is error log.
> >
> > ================================ start ==========================
> > commit 05cf8077e54b20dddb756eaa26f3aeb5c38dd3cf
> > Merge: cf78031 db5dd0d
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date: Fri Apr 1 20:03:33 2016 -0500
> > ================================= end =========================
> >
> > ============================== start ===========================
> > mkdir -p
> > /home/sean/work/source/upstream/kernel.linus/linux/tools/power/cpupower
> > && make O=/home/sean/work/source/upstream/kernel.linus/linux
> > subdir=tools/power/cpupower --no-print-directory -C power/cpupower
> > gcc -DVERSION=\"4.6.rc1.190.g05cf80\" -DPACKAGE=\"cpupower\"
> > -DPACKAGE_BUGREPORT=\"linux-pm@vger.kernel.org\" -D_GNU_SOURCE -pipe
> > -DNLS -Wall -Wchar-subscripts -Wpointer-arith -Wsign-compare
> > -Wno-pointer-sign -Wdeclaration-after-statement -Wshadow -O1 -g -DDEBUG
> > -I./lib -I ./utils -o
> > /home/sean/work/source/upstream/kernel.linus/linux/utils/helpers/amd.o
> > -c utils/helpers/amd.c
> > utils/helpers/amd.c:7:21: fatal error: pci/pci.h: No such file or
> > directory
> > #include <pci/pci.h>
>
> You need pciutils header and library:
> ftp://ftp.kernel.org/pub/software/utils/pciutils
>
> Thomas
Thanks
prev parent reply other threads:[~2016-05-03 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 5:11 Fail to build tools/all Sean Fu
2016-05-02 10:20 ` Thomas Renninger
2016-05-03 4:03 ` Sean Fu [this message]
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=20160503040317.GA6274@linux-dunz.site \
--to=fxinrong@gmail.com \
--cc=linux-kernel@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