help compilation qemu

Maarten Hoes hoes.maarten@gmail.com
Sun May 3 17:09:49 GMT 2020


Hi,

On Sun, May 3, 2020 at 4:54 PM Eliot Moss <moss@cs.umass.edu> wrote:

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


Good point. I tried to verify that, so I did


[1a]
On a cygwin prompt
echo $PATH | grep -i msys

[1b]
On a msys prompt
echo $PATH | grep -i cyg


And got no conflicting results. (msys is not in the cygwin path, and cygwin
is not in the msys path).


[2]
'mount' only showed cygdrive on a cygwin prompt, and only msys on a msys
prompt


[3]
Looked for a 'msys' string in a random binary in the path:

[3a]
On a msys prompt:
strings `which ls.exe` | grep -i msys

gave me msys hits.


[3b]
on a cygwin prompt:
strings `which ls.exe` | grep -i msys

gave me no hits.



So it at least appears to me that the environments are not conflicting for
me personally. Of course, that could very well be the case for the error
results of the original poster.

PS:
if anyone knows of better tests/checks to see if the environments are
intermingled in some way, I'd love to hear it.



- Maarten


More information about the Cygwin mailing list