public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Arthur Norman <acn1@cam.ac.uk>,
	juan carlos rebate rodriguez <nerus492@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: problem using gcc-core for compile qemu
Date: Fri, 8 Jan 2021 08:06:13 -0500	[thread overview]
Message-ID: <085cd7e2-93d1-fe94-6bbd-236751db4963@cs.umass.edu> (raw)
In-Reply-To: <alpine.WNT.2.00.2101080832070.41236@panamint>

On 1/8/2021 3:42 AM, Arthur Norman via Cygwin wrote:
 >> I can't use virtualbx because what I need is to emulate
 >> the aarch64 architecture, I don't want to use binaries compiled by
 >> others, one of the reasons is that those binaries don't include sd-card emulation support...
 > This is perhaps an off-topic response as regards compiling things on cygwin, but some while back I
 > found a range of sets of instructions for setting up aarch64 emulation in qemu. When I had any
 > issues running on Windows I just used virtualbox to give myself an x86_64 Linux world and installed
 > qemu there. And after a while I could buy a Raspberry pi with a 64-bit cpu and use that, so these
 > days working with aarch64 (and an SD card) works best for me on an rpi4 not via emulation. But to
 > find people who have worked on adapting and setting up qemu to support aarch64 with an SD card you
 > might find it useful to follow the footsteps of those who were working towards rpi 64-bit support?
 > And I like and use cygwin for most of what I do, but when something I want to do is better supported
 > by Linux then setting up an Ubuntu via virtualbox uses some disc space but does not add much
 > overhead on my main W10 machine and lets me build, test and debug there because following a path
 > that is already well trodden is often easiest!
 > Arthur

I want to second some of that.  My research regularly involves development for
ARM targets (more commonly 32 bit, but also 64).  I happen to use VirtualBox
and there cross-compile from x86 to ARM.  This works for building even a whole
OS from scratch.  After that I am using gem5, not qemu, but the principle
would be the same.  I also spent less than $100 to set myself up with a
Raspberry Pi and SD card.  (I still need gem5 because I am emulating some
additional hardware that does not physically exist (yet, anyway).)

If you need to cross-compile to an ARM target, you could download the Cygwin
gcc package source and build the cross compiler to aarch 64, along with the
other cross tools from bin utils (I am thinking of nm, objdump, etc.).  Then
you can build binaries for ARM using Cygwin, if you like.  I am not aware of
already existing Cygwin packages for ARM targets, but somebody may have built
them.

One advantage of VirtualBox is that Ubuntu packages fo cross compiling to ARM
already exist so I just install and run them.

Best wishes - Eliot Moss

  reply	other threads:[~2021-01-08 13:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  3:23 Juan carlos Rebate
2021-01-07  3:37 ` Eliot Moss
2021-01-07 13:43   ` Eliot Moss
2021-01-07 14:39 ` Marco Atzeri
2021-01-07 14:53   ` Csaba Raduly
2021-01-07 16:18     ` Marco Atzeri
2021-01-07 17:00       ` Eliot Moss
2021-01-07 22:33   ` juan carlos rebate rodriguez
2021-01-08  5:52     ` Marco Atzeri
2021-01-08  6:55       ` Marco Atzeri
2021-01-08  8:42     ` Arthur Norman
2021-01-08 13:06       ` Eliot Moss [this message]
2021-01-08 13:19         ` Marco Atzeri
2021-01-08 20:54       ` juan carlos rebate rodriguez
2021-01-08 22:32         ` Lee
2021-01-08 22:33         ` Brian Inglis
2021-01-07 17:21 ` Brian Inglis

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=085cd7e2-93d1-fe94-6bbd-236751db4963@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=acn1@cam.ac.uk \
    --cc=cygwin@cygwin.com \
    --cc=nerus492@gmail.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).