From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: nerus <fhuvu30@gmail.com>,
Ottavio Caruso <ottavio2006-usenet2012@yahoo.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Weil <sw@weilnetz.de>, qemu-devel <qemu-devel@nongnu.org>,
qemu-discuss <qemu-discuss@nongnu.org>,
Yonggang Luo <luoyonggang@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: problema compilation
Date: Sat, 20 Feb 2021 00:07:06 +0100 [thread overview]
Message-ID: <b0bb2b4e-4ebe-f4c4-d8ef-191c19c876bb@amsat.org> (raw)
In-Reply-To: <CAFEAcA8Xuf3WfPiNPqSVLz+tMgvO+6OzKTRQpJ_9Z7MqeO6pCw@mail.gmail.com>
Cc'ing Stefan / Yonggang / Paolo.
On 2/20/21 12:03 AM, Peter Maydell wrote:
> On Fri, 19 Feb 2021 at 22:54, nerus <fhuvu30@gmail.com> wrote:
>>
>> Good evening, I turn to you because I have a problem that does not appear in the official documentation, nor in the different blogs or irc channels.
>>
>> I need to do a cross compilation but it is impossible from version 5.2, when I use msys2 an error occurs indicating that symbolic links cannot be created even though the windows user has permissions to create symbolic links, I configured this through gpedit.msc.
>>
>> when I use cygwin with the mingw64-w64 tool chain an error occurs whereby meson says that it cannot find any compiler even though the compiler path is specified in the configuration script, mingw cannot be used from linux either due to There are many missing components that cannot be compiled by hand because the proper versions are no longer available, how could you solve these problems without using already compiled binaries? Thank you
>
> Cross compilation works in general -- our CI testing setup
> includes various cross-compile configurations, including
> building Windows executables from a Linux host
> (eg https://gitlab.com/qemu-project/qemu/-/jobs/1042844159).
>
> You'll need to be more specific about exactly what you're
> trying to do and failing (eg quoting exact commands,
> setups, error messages).
>
> thanks
> -- PMM
>
next parent reply other threads:[~2021-02-19 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <05BD61C1-9771-4EF9-AD1B-8DAB8DFD127A@hxcore.ol>
[not found] ` <CAFEAcA8Xuf3WfPiNPqSVLz+tMgvO+6OzKTRQpJ_9Z7MqeO6pCw@mail.gmail.com>
2021-02-19 23:07 ` Philippe Mathieu-Daudé [this message]
2021-02-20 8:42 ` problema compilation Stefan Weil
2021-02-20 9:07 ` Howard Spoelstra
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=b0bb2b4e-4ebe-f4c4-d8ef-191c19c876bb@amsat.org \
--to=f4bug@amsat.org \
--cc=fhuvu30@gmail.com \
--cc=luoyonggang@gmail.com \
--cc=ottavio2006-usenet2012@yahoo.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).