From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] kvmtool: bump to f77d646ba0
Date: Sun, 3 Dec 2017 14:54:07 +0100 [thread overview]
Message-ID: <20171203145407.78bab7c2@windsurf.home> (raw)
In-Reply-To: <20171203033321.13460-2-matthew.weber@rockwellcollins.com>
Hello,
On Sat, 2 Dec 2017 21:33:21 -0600, Matt Weber wrote:
> Commit used:
> 2017-11-03 16:19:58 +0000
> irq.h: fix compilation error due to missing bool type
>
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
This breaks the build:
LINK lkvm
x86_64-amd-linux-gnu-gcc: error: elf_x86_64: No such file or directory
x86_64-amd-linux-gnu-gcc: error: unrecognized command line option '-m'
make[2]: *** [Makefile:384: lkvm] Error 1
make[1]: *** [package/pkg-generic.mk:250: /home/thomas/projets/buildroot/output/build/kvmtool-f77d646ba01d04be5aad9449ac00719c043fe36e/.stamp_built] Error 2
make: *** [Makefile:79: _all] Error 2
With the following defconfig:
BR2_x86_64=y
BR2_x86_steamroller=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_KVMTOOL=y
# BR2_TARGET_ROOTFS_TAR is not set
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-03 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 3:33 [Buildroot] [PATCH 1/2] kvm-unit-tests: bump to kvm-unit-tests-20171020 Matt Weber
2017-12-03 3:33 ` [Buildroot] [PATCH 2/2] kvmtool: bump to f77d646ba0 Matt Weber
2017-12-03 13:54 ` Thomas Petazzoni [this message]
2017-12-03 14:05 ` Matthew Weber
2017-12-03 14:15 ` Thomas Petazzoni
2017-12-06 2:05 ` Matthew Weber
2017-12-06 7:59 ` Thomas Petazzoni
2017-12-06 13:46 ` Matthew Weber
2017-12-06 14:29 ` Matthew Weber
2017-12-07 4:22 ` Matthew Weber
2017-12-03 13:50 ` [Buildroot] [PATCH 1/2] kvm-unit-tests: bump to kvm-unit-tests-20171020 Thomas Petazzoni
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=20171203145407.78bab7c2@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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