From: Thomas Huth <thuth@redhat.com>
To: "Bin Meng" <bmeng.cn@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Cc: "Bin Meng" <bin.meng@windriver.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Yonggang Luo" <luoyonggang@gmail.com>
Subject: Re: [PATCH] .cirrus.yml: Change winsymlinks to 'native'
Date: Mon, 25 Jul 2022 10:55:14 +0200 [thread overview]
Message-ID: <3c88f9cf-a5fd-0bef-91b2-6ac8ed787e4d@redhat.com> (raw)
In-Reply-To: <20220719161230.766063-1-bmeng.cn@gmail.com>
On 19/07/2022 18.12, Bin Meng wrote:
> From: Bin Meng <bin.meng@windriver.com>
>
> At present winsymlinks is set to 'nativestrict', and its behavior is:
>
> a) if native symlinks are enabled and <target> exists, creates
> <destination> as a native Windows symlink;
> b) else if native symlinks are not enabled or if <target> does
> not exist, 'ln -s' fails.
>
> This causes the following error message was seen during the configure:
>
> "ln: failed to create symbolic link
> 'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory"
>
> Change winsymlinks to 'native' whose behavior is most similar to the
> behavior of 'ln -s' on *nix, that is:
>
> a) if native symlinks are enabled, and whether <target> exists
> or not, creates <destination> as a native Windows symlink;
> b) else if native symlinks are not enabled, and whether <target>
> exists or not, 'ln -s' creates as a Windows shortcut file.
>
> Signed-off-by: Bin Meng <bin.meng@windriver.com>
> ---
>
> .cirrus.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.cirrus.yml b/.cirrus.yml
> index 20843a420c..eac39024f2 100644
> --- a/.cirrus.yml
> +++ b/.cirrus.yml
> @@ -10,7 +10,7 @@ windows_msys2_task:
> memory: 8G
> env:
> CIRRUS_SHELL: powershell
> - MSYS: winsymlinks:nativestrict
> + MSYS: winsymlinks:native
> MSYSTEM: MINGW64
> MSYS2_URL: https://github.com/msys2/msys2-installer/releases/download/2022-05-03/msys2-base-x86_64-20220503.sfx.exe
> MSYS2_FINGERPRINT: 0
Acked-by: Thomas Huth <thuth@redhat.com>
Alex, if I've got that right, you're currently assembling a "testing" pull
request - could you please pick up this patch for that, too? ... I currently
don't have anything else pending right now, so I don't plan any new pull
request soon.
Thomas
next prev parent reply other threads:[~2022-07-25 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 16:12 [PATCH] .cirrus.yml: Change winsymlinks to 'native' Bin Meng
2022-07-25 1:24 ` Bin Meng
2022-07-25 2:07 ` 罗勇刚(Yonggang Luo)
2022-07-25 8:55 ` Thomas Huth [this message]
2022-07-25 12:25 ` Alex Bennée
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=3c88f9cf-a5fd-0bef-91b2-6ac8ed787e4d@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=f4bug@amsat.org \
--cc=luoyonggang@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).