Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "Neri, Ricardo" <ricardo.neri@intel.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: ovmf fails to build with musl (was: Re: [PATCH 5/6] musl: Update to latest)
Date: Tue, 21 Mar 2017 09:54:05 +0100	[thread overview]
Message-ID: <1490086445.6396.214.camel@intel.com> (raw)
In-Reply-To: <1490043755.6396.211.camel@intel.com>

On Mon, 2017-03-20 at 22:02 +0100, Patrick Ohly wrote:
> However, TARGET_PREFIX is empty in ovmf-native. So instead of
> i586-poky-linux-musl-gcc or i586-poky-linux-musl-gcc-ar we end up
> building with gcc and gcc-ar from the host, which probably wasn't the
> intention.
> 
> Below a patch which compiles for me using the right tools. More testing
> has to wait until tomorrow.

I've cleaned up the patch a bit more and tested it successfully with
refkit on intel-corei7-64. Building for musl on qemux86 also worked,
using i586-poky-linux-musl-gcc.

I propose that we include the patch (will send as reply) in master-next
to check whether it also fixes the problem on the AB.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-03-21  8:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 23:35 [PATCH 0/6] mesa/go/binutils fixes Khem Raj
2017-03-14 23:35 ` [PATCH 1/6] mesa: Contain configure search for llvm Khem Raj
2017-03-14 23:35 ` [PATCH 2/6] mesa-gl: Drop MESA_CRYPTO from PACKAGECONFIG Khem Raj
2017-03-14 23:35 ` [PATCH 3/6] go: Fix packaging for target go Khem Raj
2017-03-14 23:35 ` [PATCH 4/6] binutils: Enable threading when gold is enabled and is not default linker Khem Raj
2017-03-20 12:22   ` Burton, Ross
2017-03-14 23:35 ` [PATCH 5/6] musl: Update to latest Khem Raj
2017-03-20  8:32   ` Jussi Kukkonen
2017-03-20  9:57     ` Patrick Ohly
2017-03-20 14:43     ` Khem Raj
2017-03-20 21:02       ` ovmf fails to build with musl (was: Re: [PATCH 5/6] musl: Update to latest) Patrick Ohly
2017-03-21  8:54         ` Patrick Ohly [this message]
2017-03-21  8:56           ` [PATCH] ovmf: fix toolchain selection Patrick Ohly
2017-03-21 15:26             ` Khem Raj
2017-03-14 23:35 ` [PATCH 6/6] xserver-xf86-config: Remove X server module preload Khem Raj

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=1490086445.6396.214.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ricardo.neri@intel.com \
    /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