X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org AC3993844028
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=cs.umass.edu
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=moss AT cs DOT umass DOT edu
Subject:	Re: problem using gcc-core for compile qemu
To:	Arthur Norman <acn1 AT cam DOT ac DOT uk>,
	juan carlos rebate rodriguez <nerus492 AT gmail DOT com>
References:	<CAJzZnfStmF4zseRoAvBm9HLd-dSgTjh8sWZTCFZJRPHCJsMaHQ AT mail DOT gmail DOT com>
	<1d7072d9-c982-d3cd-e4ca-b4fd3dc1c6f6 AT gmail DOT com>
	<cd43634f0573a04bb44d5b9d9165f49feb4839de DOT camel AT gmail DOT com>
	<alpine DOT WNT DOT 2 DOT 00 DOT 2101080832070 DOT 41236 AT panamint>
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID:	<085cd7e2-93d1-fe94-6bbd-236751db4963@cs.umass.edu>
Date:	Fri, 8 Jan 2021 08:06:13 -0500
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
	Thunderbird/68.12.1
MIME-Version:	1.0
In-Reply-To:	<alpine.WNT.2.00.2101080832070.41236@panamint>
X-Spam-Status:	No, score=-3.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	moss AT cs DOT umass DOT edu
Cc:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

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
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -