Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/kvm-unit-tests: new package
Date: Fri, 23 Sep 2016 08:12:16 +0200	[thread overview]
Message-ID: <20160923081216.6f580f50@free-electrons.com> (raw)
In-Reply-To: <1474610816.2482.14.camel@gmail.com>

Hello,

On Fri, 23 Sep 2016 16:06:56 +1000, Cyril Bur wrote:

> So the i686 problem is actually fixed upstream so I've sent a patch to
> bump the version.
> 
> I tried select BR2_HOSTARCH_NEEDS_IA32_COMPILER for x86_64 but didn't
> seem to solve the problem. I know almost nothing about x86 asm so I'm
> at a bit of a loss, it looks like gcc is generating instructions from C
> that should be 16bit but then later it realises it messed up?
> 
> Still chasing but having BR2_HOSTARCH_NEEDS_IA32_COMPILER=y didn't
> solve.

No, you need this *and* use the host compiler when building
kvm-unit-tests on x86_64. By using the host compiler, you use a
compiler that can generate 32 bits code.

See syslinux and grub, like Peter suggested.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-23  6:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 23:02 [Buildroot] [PATCH] package/kvm-unit-tests: new package Cyril Bur
2016-09-19 14:48 ` Thomas Petazzoni
2016-09-19 21:07   ` Peter Korsgaard
2016-09-19 23:12   ` Cyril Bur
2016-09-21  7:24 ` Thomas Petazzoni
2016-09-22  0:01   ` Cyril Bur
2016-09-22  5:18     ` Peter Korsgaard
2016-09-22  9:34       ` Thomas Petazzoni
2016-09-22  9:42         ` Peter Korsgaard
2016-09-23  6:06       ` Cyril Bur
2016-09-23  6:12         ` Thomas Petazzoni [this message]
2016-09-23  6:14           ` Cyril Bur

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=20160923081216.6f580f50@free-electrons.com \
    --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