From: "Emmanuel Blot" <eblot.ml@gmail.com>
To: QEMU <qemu-devel@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: ld: file not found: _PreallocMode_lookup on macOS Catalina
Date: Mon, 19 Oct 2020 18:40:58 +0200 [thread overview]
Message-ID: <AA504B32-5134-4CDD-8CDA-6F200C7376CF@gmail.com> (raw)
In-Reply-To: <3869557c-10a0-8f07-a59a-69120a522568@redhat.com>
On 19 Oct 2020, at 17:50, Philippe Mathieu-Daudé wrote:
> Cc'ing Markus/John/Paolo
I never used `git bisect` up to now, so I might be wronb but it seems
the issue would have been introduced with the following commit:
604f3e4e90c011a6b94fdc1d13700f3ec2375f2a is the first bad commit
commit 604f3e4e90c011a6b94fdc1d13700f3ec2375f2a
Author: Yonggang Luo <luoyonggang@gmail.com>
Date: Thu Sep 3 01:00:50 2020 +0800
meson: Convert undefsym.sh to undefsym.py
Shell scripts are not easily invoked from the build process
on MSYS, so convert undefsym.sh to a python script.
Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
Message-Id: <20200902170054.810-3-luoyonggang@gmail.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
meson.build | 2 +-
scripts/undefsym.py | 49
+++++++++++++++++++++++++++++++++++++++++++++++++
scripts/undefsym.sh | 20 --------------------
3 files changed, 50 insertions(+), 21 deletions(-)
create mode 100644 scripts/undefsym.py
delete mode 100755 scripts/undefsym.sh
next prev parent reply other threads:[~2020-10-19 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 15:33 ld: file not found: _PreallocMode_lookup on macOS Catalina Emmanuel Blot
2020-10-19 15:50 ` Philippe Mathieu-Daudé
2020-10-19 16:40 ` Emmanuel Blot [this message]
2020-10-19 17:14 ` Paolo Bonzini
2020-10-19 17:24 ` Emmanuel Blot
2020-10-19 17:16 ` Emmanuel Blot
2020-10-19 17:23 ` Paolo Bonzini
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=AA504B32-5134-4CDD-8CDA-6F200C7376CF@gmail.com \
--to=eblot.ml@gmail.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.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).