public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Dan Wilder <Dan.Wilder@watchguard.com>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>,
	"nick@nickgawronski.com" <nick@nickgawronski.com>
Subject: Re: building a program on my debian x64 system for the raspberrypi
Date: Mon, 29 Jun 2020 15:34:50 +0000	[thread overview]
Message-ID: <MWHPR1001MB2206CC1A6B8CA6EE7AABEDB5FD6E0@MWHPR1001MB2206.namprd10.prod.outlook.com> (raw)
In-Reply-To: <db55b8a3-d6e9-611c-32a9-d1771ff9af93@nickgawronski.com>

The raspberrypi.org website has some instructions which might help.

https://www.raspberrypi.org/documentation/linux/kernel/building.md

They talk about doing it on Ubuntu but in my experience what works on Ubuntu also works on Debian, with sometimes a few small variations.


--
Dan Wilder
________________________________
From: crossgcc <crossgcc-bounces@sourceware.org> on behalf of Nick Gawronski <nick@nickgawronski.com>
Sent: Monday, June 29, 2020 1:58 AM
To: crossgcc@sourceware.org <crossgcc@sourceware.org>
Subject: building a program on my debian x64 system for the raspberrypi

Hi, I am trying to setup a cross compilation system so I can build
binaries for the raspberrypi both model b and 3b models. Yes I know I
can compile directly on the raspberrypi but was wondering how easy is it
to setup a cross compilation system to be able to take advantage of my
fast system to build for my much slower raspberrypi computers?  Nick
Gawronski

--
For unsubscribe information see http://sourceware.org/lists.html#faq

      reply	other threads:[~2020-06-29 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  8:58 Nick Gawronski
2020-06-29 15:34 ` Dan Wilder [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=MWHPR1001MB2206CC1A6B8CA6EE7AABEDB5FD6E0@MWHPR1001MB2206.namprd10.prod.outlook.com \
    --to=dan.wilder@watchguard.com \
    --cc=crossgcc@sourceware.org \
    --cc=nick@nickgawronski.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).