From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] kvmtool: bump to f77d646ba0
Date: Wed, 6 Dec 2017 08:59:58 +0100 [thread overview]
Message-ID: <20171206085958.3671c8a1@windsurf.lan> (raw)
In-Reply-To: <CANQCQpZF8+b7PyYLmw6ZZCX=CTv=rQQmtkJj0ogF3wdPF+unTw@mail.gmail.com>
Hello,
On Tue, 5 Dec 2017 20:05:42 -0600, Matthew Weber wrote:
> Gustavo, the latest kvmtool switched to doing the final link with gcc
> vs originally ld. I believe this is the right fix.
>
> 3 --- a/package/kvmtool/kvmtool.mk
> 4 +++ b/package/kvmtool/kvmtool.mk
> 5 @@ -33,7 +33,7 @@ KVMTOOL_LICENSE_FILES = COPYING
> 6 # If more packages need this (unlikely) an ld wrapper might be a better
> 7 # solution, using gcc -dumpspecs information.
> 8 KVMTOOL_EXTRA_LDFLAGS = \
> 9 - $(if $(BR2_x86_64),-m elf_x86_64)
> 10 + $(if $(BR2_x86_64),-m64)
If kvmtool is now building with gcc, do we need -m64 at all ?
Also Matt: I wouldn't expect much feedback from Gustavo, he has stopped
contributing to Buildroot earlier this year, and has removed himself
from the DEVELOPERS file.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-06 7:59 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
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 [this message]
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=20171206085958.3671c8a1@windsurf.lan \
--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