X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89B84395C015
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1610095387;
	bh=QdzzQ+vwwqfWl9MTq7JnW2imBMIFa61QNEMXDPvX9RE=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=YokULSVY94GG4XjGfmglUk6LdV4ZbmqbgBIuxsAbbgsPZgR4qq9x1b0wOzC70kZKu
	 kuG2Nm0vIOyjGH5RQNOTttCDf/wl3gGLrQEleUuIPYfAFPvFvLSYgzHNpvCKm5Qfi6
	 uejWAkY0g/j8gG8jPxNHjxWjSCy6vlZ3nnU7SWw8=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 107C33950C59
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Date: Fri, 8 Jan 2021 08:42:58 +0000 (GMT Standard Time)
To: juan carlos rebate rodriguez <nerus492 AT gmail DOT com>
Subject: Re: problem using gcc-core for compile qemu
In-Reply-To: <cd43634f0573a04bb44d5b9d9165f49feb4839de.camel@gmail.com>
Message-ID: <alpine.WNT.2.00.2101080832070.41236@panamint>
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>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
X-X-Sender: acn1 AT imap DOT hermes DOT cam DOT ac DOT uk
MIME-Version: 1.0
X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, DKIMWL_WL_MED,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_MSPIKE_H3,
 RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, 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
Precedence: list
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>
From: Arthur Norman via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Arthur Norman <acn1 AT cam DOT ac DOT uk>
Cc: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

> 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

--
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