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 C5937386EC62
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: Marco Atzeri <marco DOT atzeri AT gmail DOT com>, Csaba Raduly <rcsaba AT gmail DOT com>
References: <CAJzZnfStmF4zseRoAvBm9HLd-dSgTjh8sWZTCFZJRPHCJsMaHQ AT mail DOT gmail DOT com>
 <1d7072d9-c982-d3cd-e4ca-b4fd3dc1c6f6 AT gmail DOT com>
 <CAEhDDbA7n+BqaiwV=1SxH18nDf8dwF_2agQKeMVd77cUB7XJkg AT mail DOT gmail DOT com>
 <5483804f-7b36-ece6-599b-93e272f0373f AT gmail DOT com>
From: Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID: <1e6d5b56-aceb-c003-efe7-1512e97d57d6@cs.umass.edu>
Date: Thu, 7 Jan 2021 12:00:51 -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: <5483804f-7b36-ece6-599b-93e272f0373f@gmail.com>
Content-Language: en-US
X-Spam-Status: No, score=-3.4 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
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>
Reply-To: moss AT cs DOT umass DOT edu
Cc: cygwin list <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>

On 1/7/2021 11:18 AM, Marco Atzeri via Cygwin wrote:

 > It is not that is impossible, but will likely need a big effort.
 >
 > As there are Windows binaries, I do not think it is worth

Right - I had noticed on the web some mention of people maybe working on
getting qemu going under Cygwin.  There is no reason why that cannot be done
in principle, but since qemu can boot operating systems and such, it requires
proper mapping a many OS calls, etc.

Naturally I have no idea what the OP's overall goal is.  As a computer science
researcher, I have often found that for setups like this, a VirtualBox virtual
machine is better because I can get a well-controlled "pure Linux"
environment, that I can also package up and share with students and
colleagues.  Also, compared with Cygwin, I typically get higher speed.  This
is because there is overhead inherent in modeling Posix on top of Windows via
a library.  A VM runs actual Linux.  Don't get me wrong - I love Cygwin and
use it for much of my work!  I like having Windows apps and tools available
while living is a very Unix-like command-line world.  But it's not the only
thing out there.

Note that a modern alternative to VirtualBox (or vmware) is WSL, the Windows
Subsystem for Linux, which (it turns out) is also a VM.  (Note: Unless things
have changed recently, WSL version 2 (which may offer performance advantages
over WSL version 1) is not compatible with VirtualBox.  They use the hardware
virtualization in "opposite" ways.  WSL 1 can be kept compatible with
VirtualBox, but its emulation of Linux on top of Windows suffers from similar
performance issues to those of Cygwin, especially around the fork() call.)

Anyway, maybe this will contribute to the OP's overall need, maybe not ...

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