public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Maarten Hoes <hoes.maarten@gmail.com>,
	Juan carlos Rebate <nerus492@gmail.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: help compilation qemu
Date: Sun, 3 May 2020 10:54:32 -0400	[thread overview]
Message-ID: <ba58194f-d8e9-e1c0-aa4f-4b0434e4f9fa@cs.umass.edu> (raw)
In-Reply-To: <CAHvU03VQxx2_tXhjP3SyZC6XTaRZv8ug6zSO2i0b-94QRgtn3A@mail.gmail.com>

On 5/3/2020 8:52 AM, Maarten Hoes via Cygwin wrote:
> Hrm.
> 
> That's odd. I just installed MSYS2 and followed the instructions provided
> in the QEMU wiki for MSYS2, and all preparatory steps of running
> msys2/pacman/git/configure (only excluding the actual 'make' for
> compilation) work as expected. There must be a difference between our
> setups/steps/configurations if that doesn't work for you.

I can imagine issues with both MSYS and Cygwin installed, if the order
of things on paths is not right, e.g., getting the Cygwin version of
something when trying to run MSYS, or vice versa.

Maybe try to make sure, when building qemu under MSYS, that no Cygwin
things are in your path?

Best wishes -- Eliot

  reply	other threads:[~2020-05-03 14:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 19:28 Juan carlos Rebate
2020-05-02 19:33 ` john doe
2020-05-02 20:07   ` Juan carlos Rebate
2020-05-02 20:24 ` Maarten Hoes
2020-05-02 20:41   ` Juan carlos Rebate
     [not found]     ` <CA+GYywAezLvoh+4PhgepphqcEsyUbm_ZOC8yDZqOncVePMzneg@mail.gmail.com>
2020-05-02 22:50       ` Juan carlos Rebate
2020-05-03 12:52     ` Maarten Hoes
2020-05-03 14:54       ` Eliot Moss [this message]
2020-05-03 17:09         ` Maarten Hoes
2020-05-24  0:08 Juan carlos Rebate
2020-05-24  9:25 ` Csaba Ráduly
2020-05-24 15:30   ` Juan carlos Rebate
2020-05-24 15:41     ` Eliot Moss
2020-05-24 17:45     ` Hans-Bernhard Bröker

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=ba58194f-d8e9-e1c0-aa4f-4b0434e4f9fa@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    --cc=hoes.maarten@gmail.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).