All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Newbie questions on cross-building packages for PPC
Date: Sun, 24 Feb 2019 14:33:04 +0100	[thread overview]
Message-ID: <CANNYZj94f4d+DafeJ4pzDGFErhor3TC3vW1qx2RVJxqjU04dkw@mail.gmail.com> (raw)
In-Reply-To: <3DFF1337-2E58-45DF-80D6-303934B303B8@redfish-solutions.com>

On Sat, 23 Feb 2019 at 22:18, Philip Prindeville
<philipp_subx@redfish-solutions.com> wrote:
> I’ve worked on a lot of embedded projects involving cross-building (like AstLinux and OpenWrt), but I’m new to Yocto so please bear with the noob questions.
>
> I’d like to build packages (mostly RPM’s, plus a Linux kernel or three) on an x86_64 (AMD64) Linux (CentOS 7.6) platform, but for e500v2 and 85xxDP PPC targets.
>
> What do I need to do to set up a toolchain and environment to be able to do that?

First, you need to figure out which BSP layer provides support for
your targets. What boards are you targeting?

> Ideally, I’d also like to set up an RPM target so I could use “rpmbuild --target e500v2-unknown-linux” (or whatever) and it would use the correct compiler, linker, archiver, sysheaders, etc.
>
> Advice on both of these, or just pointers to instructions on how to set it all up, would be great.

I'd suggest you start with the yocto quickstart guide, so you'll know
the basic procedures.
https://www.yoctoproject.org/docs/latest/brief-yoctoprojectqs/brief-yoctoprojectqs.html

> For instance, do I need one compiler only that can handle multiple processor variants via the --march= flag, or is this not the right way to go?  And similarly, since the linker can rewrite code (shortening branch offsets, peep-hole optimization, unreachable code removal, etc.) do I need different linker versions for the 2 PPC variants?

This is what BSP layers do, they define a target machine (which
includes compiler and linker settings), and give it a name. Then you
place that name in your configuration file, and the target build
process will sort itself out.

Alex


      reply	other threads:[~2019-02-24 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 21:14 Newbie questions on cross-building packages for PPC Philip Prindeville
2019-02-24 13:33 ` Alexander Kanavin [this message]

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=CANNYZj94f4d+DafeJ4pzDGFErhor3TC3vW1qx2RVJxqjU04dkw@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=philipp_subx@redfish-solutions.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.