public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: crossgcc@sourceware.org
Subject: Building Centos 7.6 for ppc32 (on Centos 7.x, using crosstool-ng-1.23.0)
Date: Mon, 21 Jan 2019 02:57:00 -0000	[thread overview]
Message-ID: <40A9BFBC-C008-408F-90E1-3D50DB17ADFF@redfish-solutions.com> (raw)

Hi.

I’m looking for any guidance on setting up crosstool-ng for cross-compiling CentOS 7.6 for ppc32 (in this case, ppc_85xxDP and ppc_6xx, or ppc_e500v2).

Also related stuff that needs to be done to integrate into RPM and rpmbuild, such as setting up a platform definition, etc.

Are there any cookbooks or URL’s to walk a newbie through the process?  I work on a lot of embedded projects so I’m used to buildroot-based environments, but I’ve never had to set one up from scratch.

I’m aware that vendors haven’t been supporting PPC32 well, and GCC 8.x will be deprecating support, caveat emptor.

Thanks,

-Philip

             reply	other threads:[~2019-01-21  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  2:57 Philip Prindeville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-17 22:52 Philip Prindeville

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=40A9BFBC-C008-408F-90E1-3D50DB17ADFF@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).