Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Crowe <mac@mcrowe.com>, openembedded-core@lists.openembedded.org
Subject: Re: Building and using a second toolchain
Date: Thu, 07 Sep 2017 13:21:09 +0100	[thread overview]
Message-ID: <1504786869.726.13.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170907111347.u4bixwf2q7mabuy3@mcrowe.com>

On Thu, 2017-09-07 at 12:13 +0100, Mike Crowe wrote:
> It thought that the simplest path to making this work would be to ensure
> that the manifest files generated during the build have the names that all
> other recipes will expect, but this means using the wrong TARGET_ARCH in my
> binutils-cross-arm and gcc-cross-initial-arm recipes which I can't do
> without also overriding TARGET_SYS and PN at least which definitely isn't
> pretty.
> 
> I remember reading posts about doing this on the list in the past, but my
> search engine skills aren't up to the job of finding anything. Am I missing
> an easier way to make this work?

Have you considered using multilib? You could have a 32 bit multilib
defined for the 64 bit system, then just use its 32 bit compiler?

Cheers,

Richard


  reply	other threads:[~2017-09-07 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 11:13 Building and using a second toolchain Mike Crowe
2017-09-07 12:21 ` Richard Purdie [this message]
2017-09-07 17:00   ` Mike Crowe
2017-09-07 21:28     ` Richard Purdie
2017-09-08  6:04       ` Mike Crowe
2017-09-08  6:53         ` Richard Purdie
2017-10-05 17:12           ` Mike Crowe

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=1504786869.726.13.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mac@mcrowe.com \
    --cc=openembedded-core@lists.openembedded.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