Qemu error cannot find ninja

Hi Ciro,

I met the below problem and I searched the issues which don’t include this one. You can take a look below error:

Thanks a lot.

/**********************************************************************************************************************/

• cd /home/sean/linux-kernel-module-cheat/out/qemu/default/opt &&
  PATH=’/usr/lib/ccache:»${PATH}»‘
  /home/sean/linux-kernel-module-cheat/submodules/qemu/configure
  —enable-trace-backends=simple
  —target-list=x86_64-softmmu
  —enable-sdl
  ;

ERROR: Cannot find Ninja

Traceback (most recent call last):
File «./build», line 679, in
Main().cli()
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 267, in cli
exit_status = self.cli_noexit(*args, **kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 258, in cli_noexit
return self._do_main(vars(args))
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 152, in _do_main
return self.main(**self._get_args(kwargs))
File «/home/sean/linux-kernel-module-cheat/common.py», line 1540, in main
ret = self.timed_main()
File «./build», line 674, in timed_main
ret = component.build(self.env[‘arch’])
File «./build», line 55, in build
return self.build_callback()
File «./build», line 471, in f
return lkmc.import_path.import_path_main(component_file)(**args)
File «/home/sean/linux-kernel-module-cheat/common.py», line 739, in call
return super().call(**kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 149, in call
return self._do_main(kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 152, in _do_main
return self.main(**self._get_args(kwargs))
File «/home/sean/linux-kernel-module-cheat/common.py», line 1540, in main
ret = self.timed_main()
File «/home/sean/linux-kernel-module-cheat/common.py», line 2059, in timed_main
return self.build()
File «/home/sean/linux-kernel-module-cheat/build-qemu», line 38, in build
self.sh.run_cmd(
File «/home/sean/linux-kernel-module-cheat/shell_helpers.py», line 457, in run_cmd
raise e
Exception: Command exited with status:
if self.env[‘configure’]:
self.sh.run_cmd(
[
os.path.join(self.env[‘qemu_source_dir’], ‘configure’), LF,
‘—enable-trace-backends=simple’, LF,
‘—target-list={}’.format(target_list), LF,
‘—enable-sdl’, LF,
] +
build_type_cmd +
self.sh.shlex_split(self.env[‘extra_config_args’]),
extra_paths=[self.env[‘ccache_dir’]],
cwd=build_dir
)

/**********************************************************************************************************************/

can’t compile qemu. it says «can’t find ninja» #142

Comments

WinnieeBear commented Jan 18, 2021

I met the below problem and I searched the issues which don’t include this one. You can take a look below error:

ERROR: Cannot find Ninja

Traceback (most recent call last):
File «./build», line 679, in
Main().cli()
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 267, in cli
exit_status = self.cli_noexit(*args, **kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 258, in cli_noexit
return self._do_main(vars(args))
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 152, in _do_main
return self.main(**self._get_args(kwargs))
File «/home/sean/linux-kernel-module-cheat/common.py», line 1540, in main
ret = self.timed_main()
File «./build», line 674, in timed_main
ret = component.build(self.env[‘arch’])
File «./build», line 55, in build
return self.build_callback()
File «./build», line 471, in f
return lkmc.import_path.import_path_main(component_file)(**args)
File «/home/sean/linux-kernel-module-cheat/common.py», line 739, in call
return super().call(**kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 149, in call
return self._do_main(kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 152, in _do_main
return self.main(**self._get_args(kwargs))
File «/home/sean/linux-kernel-module-cheat/common.py», line 1540, in main
ret = self.timed_main()
File «/home/sean/linux-kernel-module-cheat/common.py», line 2059, in timed_main
return self.build()
File «/home/sean/linux-kernel-module-cheat/build-qemu», line 38, in build
self.sh.run_cmd(
File «/home/sean/linux-kernel-module-cheat/shell_helpers.py», line 457, in run_cmd
raise e
Exception: Command exited with status:
if self.env[‘configure’]:
self.sh.run_cmd(
[
os.path.join(self.env[‘qemu_source_dir’], ‘configure’), LF,
‘—enable-trace-backends=simple’, LF,
‘—target-list=<>‘.format(target_list), LF,
‘—enable-sdl’, LF,
] +
build_type_cmd +
self.sh.shlex_split(self.env[‘extra_config_args’]),
extra_paths=[self.env[‘ccache_dir’]],
cwd=build_dir
)

The text was updated successfully, but these errors were encountered:

Источник

Error during qemu installation #65

Comments

ClaudioWayne commented Dec 16, 2020 •

Prerequisites

Please answer the following questions for yourself before submitting an issue.

• I checked to make sure that this issue has not already been filed
• I’m reporting the issue to the correct repository (for multi-repository projects)
• I read my log of installation, all issues will be closed if you don’t do your part of work

Expected Behavior

run kvm-qemu.sh qemu without error

Current Behavior

On a Fresh Ubuntu 20.04.1 i get the following Errors:

Seems that qemu 5.2.0 needs ninja?
What worked for me
-> pip3 install ninja

E: Unable to locate package qemu-5.2.0-1_amd64.deb

What worked for me
Escape _ between qemu-version
Complete Path to qemu-5.2.0_5.2.0-1_amd64.deb
apt -y -o Dpkg::Options::=»—force-overwrite» install /tmp/qemu-$qemu_version/qemu-$qemu_version_$qemu_version-1_amd64.deb

Have you tried to update qemu 5.1.0 to 5.2.0 and and libvirt 6.2.0 libvirt 6.10.0 via ./kvm-qemu.sh without breaking CAPE? Or do you recommend a fresh CAPE and KVM/QEMU installation?

Steps to Reproduce

sudo ./kvm-qemu.sh qemu

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

The text was updated successfully, but these errors were encountered:

doomedraven commented Dec 16, 2020

hello @ClaudioWayne , i have updated it on my personal server without any problem, but i had problems to compile and install as it was overwriting so i forced that apt by hand, and about ninja i had it as libvirt 6.7 I think changed building to ninja. i will need to restore my testing vm and check the script again.

so after your fixes it works or not? just to know? i wil lcopy and but not sure if i will have time as i have one neat feature to test for cape and that will require days for a lot of rewrite and testing

ClaudioWayne commented Dec 16, 2020

Installing cape on a fresh Ubuntu with the changes in kvm-qemu.sh right now. It will take a while. i will let you know if it was successful.

doomedraven commented Dec 16, 2020

thank you, and thanks for all the updates and fixes

ClaudioWayne commented Dec 16, 2020

I just tested a sample on the complete fresh install in a win7 VM.
Everything works fine.

FYI:
During the installation i collected these Pip Errors

At the End of complete installation these packages are installed atm:

So requests, pyattck, matplotlib should be fine
log-symbols, halo 0.0.31 -> «colorama>=0.3.9»
for peepdf no idea

But i guess these errors are not critical.

BTW: Do you recommend Pillow 8.0.1 in the Guest-Machine to match with host?

Feel free to close this issue and have nice day.
Thank you for keeping this project alive.

doomedraven commented Dec 16, 2020

by parts
the latest pillow always better, we saw huge performance difference between old and new versions
about pip erros ya many libs trying to enforce the dependence but that is impossible, so that not critical so far

if i tell you truth i don’t even know which lib needs log-symbols

thank you for headups

ClaudioWayne commented Dec 16, 2020

okay, thanks for information

doomedraven commented Dec 16, 2020

so i suppouse we can close the issue?

ClaudioWayne commented Dec 16, 2020

ClaudioWayne commented Dec 18, 2020

Hi,
one more question:
did you notice some permission changes in libvirt version >6.7.0? Every time i submit an analysis and when processing starts, the password prompt appears. It also appears when i start virtmanager. With 6.7.0 its fine.
I tried usermod -a -G kvm , usermod -a -G libvirt chgrp kvm /dev/kvm
added rule etc/udev/rules.d/50-qemu-kvm.rules KERNEL==»kvm», GROUP=»kvm», MODE=»0660″
added rule /lib/udev/rules.d/65-kvm.rules KERNEL==»kvm», GROUP=»kvm», MODE=»0660″
/etc/apparmor.d/usr.sbin.libvirtd and /usr/sbin/libvirtd set AppArmor security profile to complain mode

but it could be an individual problem of mine

doomedraven commented Dec 18, 2020

Hello, well i heard from one friend about it, but wasn’t able to reproduce, normally ensure this,

ClaudioWayne commented Dec 18, 2020

thanks, i will try this. Have a nice weekend

doomedraven commented Dec 18, 2020

thank you, you too, let me know if that doesn’t work, I maybe can help to investigate, if you can capture the whole permission error that would help

doomedraven commented Dec 18, 2020

hey i just found why it happens, will push that to repo too in few mins, they changed from none to polkit string

ClaudioWayne commented Dec 18, 2020

oh sorry didn´t see your comment. i just pushed a PR. u can ignore it 😀

doomedraven commented Dec 18, 2020

glad that you also found that 🙂 yes i prefer keep it working for both versions as there is no problem as strings between versions changes, so i will close it, but thank you for taking it and helping

Источник

[BUG] r23b and CMake 3.21 on windows build can’t find ninja.exe #1609

Comments

skolson commented Nov 17, 2021 •

Description

On windows 10 with an existing project using NDK 23.0.7599858 CMake 3.21.1, upgrading to r23b causes this error:

[CXX1410] . arm64-v8aandroid_gradle_build.json debug|arm64-v8a : expected buildTargetsCommandComponents command ‘ninja.exe’ to exist

Sync succeeds but shows the above error in the output. Build fails with the same error. ninja.exe was and still is on the windows system PATH so it should be able to find it. During research tried each of the following, one at a time, all with no effect:
add «-DCMAKE_MAKE_PROGRAM=D:\Android\CMake\ninja.exe» to gradle cmake arguments
Upgrade CMake from 3.21.1 to 3.21.4
add set(CMAKE_MAKE_PROGRAM «D:\Android\CMake\ninja.exe») to CMakeLists.txt

Saw NDK issue 1581 which seemed related and based on the comments tried:
add set(CMAKE_FIND_USE_SYSTEM_ENVIRONMENT_PATH 1) to CMakeLists.txt

None of the above changed the error. Below is the top of the android_gradle_build.json file. Note that the setting from CMAKE_MAKE_PROGRAM is used in cleanCommandsComponents but not in buildTargetsCommandComponents

I can’t see why the PATH isn’t being used to find ninja.exe, or why setting CMAKE_MAKE_PROGRAM isn’t helping.

I’m also unsure if this is an NDK issue or a gradle plugin issue specific to these NDK and CMake versions, sorry if I guessed wrong by posting here 🙂

The project is a Kotlin library that I’m upgrading to Kotlin 1.6.0, which is what triggered the NDK upgrade. If it is useful I can create a github repo with this project.

Environment Details

Android Studio 2021.1.1 beta 3
NDK Version: 23.1.7779620
CMake 3.21.4
ninja 1.10.2
Gradle 7.3
com.android.tools.build:gradle 7.1.0-beta03
Host OS: Windows 10

The text was updated successfully, but these errors were encountered:

DanAlbert commented Nov 17, 2021

If it is useful I can create a github repo with this project.

This is always useful, and usually required for us to able to make any progress. QA found no problems on Windows so we know typical cases work fine (we wouldn’t have shipped otherwise), and guessing at what went wrong means you have to wait a lot longer for a fix because it’s nearly impossible for us to do.

skolson commented Nov 17, 2021

DanAlbert commented Nov 17, 2021

Going to be a while before I can test anything on Windows, so looking at the diff here: https://github.com/skolson/SqlCipherKotlinMP/commit/3dc96e9087dc20f66a9a630f187ca2088f1bfa4e

If you undo the NDK update, the problem goes away? That commit updates the NDK, CMake, and the Gradle plugin among other things, but the CMake or gradle plugin updates seem plausible. The NDK update isn’t out of the question either but since we didn’t see this in our own testing I’m skeptical.

skolson commented Nov 17, 2021

Thanks for the quick update. Short answer is yes, if I switch back to 23.0.7599858 with no other change, the ninja issue goes away. But this is misleading :-). I tried to upgrade to r23b because during the upgrade to Kotlin 1.6, I hit the error below with 23.0.7599858. I found some stuff that indicated this error was specific to using CMake 3.21 or later with that NDK and might be fixed on r23b, which is why I got to where I am. I’ve been using CMake 3.21.1 (for maybe a year or so) to work around other issues 🙂

I will start backing off one change at a time until I get back to working again, and will post again when I have more info.

skolson commented Nov 18, 2021 •

Progress! I found a much easier way to cause the issue. See Repo [Issue-specific-test-case]https://github.com/skolson/NdkIssue1609).
I built a new default C++ project in Android studio. Project builds fine using default 3.18.1 of CMake.
I then added the cmake.dir=D:\Android\CMake to local.properties, and in the app build.gradle changed the cmake version from 3.18.1 to 3.21.4. Problem recreated.
The works/fails behavior stays the same even if the NDK version changes. So my original issue title about this being specific to just r23b is wrong, it can happen with others.
Then if I change the CMakeLists.txt file to add this: cmake_minimum_required(VERSION 3.21.4) , Sync gets this as if it’s ignoring the cmake.dir in local.properties:

The doc at (https://developer.android.com/reference/tools/gradle-api/7.0/com/android/build/api/dsl/Cmake) says when the version is changed in build.gradle that the system PATH is used to locate CMake, but that’s not happening in my case. I have triple-checked the PATH and it is correct and working outside of Android Studio.
So the PATH isn’t used and cmake.dir in local.properties is being ignored.

Does this info mean this is a plugin issue and not NDK? Are there diagnostics I can run to help locate this problem? I’ve been using various versions of the NDK with CMake 3.21.1 on my project for more than a year and have never seen this until yesterday. That plus your comment above makes me think this is my environment somehow, but I don’t know how to diagnose the root cause. The system PATH has not changed. CMake was upgraded in-place to 3.21.4. I’m hoping with this test case you can recreate the error. In any case the error message is misleading when gradle config specifies a higher CMake than it can find.

Let me know what else I can do to help diagnose this.

Also it just occurred to me that yesterday Android Studio popped an update notice about the kotlin plugin, and I upgraded. It’s the only change outside of CMake and NDK versions I can think of that happened. Any chance that’s relevant?

skolson commented Nov 18, 2021

One more FYI — I’m beginning to believe this error is hiding some other error. Attached is the CMakeOutput.log for one of the builds of the original project that gradle failed, using CMake 3.21.4 and NDK 23.1.7779620. Despite gradle failing with the ninja message, this log file proves that the CMake used is 3.21.4 and the ninja.exe is used form the correct location and the log looks like CMake worked even though gradle failed.

Hope this is useful. If there are any other tasks I can do or diagnostics I can send, let me know. Also another FYI, I’ve been using 3.21 for quite a while due to an old issue. I changed the project back to using the default CMake of 3.18.1 hoping that the old issue is fixed and sure enough it is, the project builds fine. So the ninja error is not a stopper for me any more, but I have time to help diagnose whatever is wrong when using a non-default CMake. Thanks again for your help..
CMakeOutput.log

DanAlbert commented Nov 19, 2021

Hope this is useful. If there are any other tasks I can do or diagnostics I can send, let me know.

Will do! afaik we have what we need now and just need to find the time to investigate. There isn’t currently a timeline for r23c, but we’ll look at this for that release.

rprichard commented Dec 3, 2021

I suspect this is an issue with the Android Gradle Plugin, and it’s probably a duplicate of these bugs:

Should we close this issue?

skolson commented Dec 3, 2021

That sure looks like the same issue, so I’m good with closing this one. Interesting that the bug is on all platforms not just windows.

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

can’t compile qemu. it says «can’t find ninja» #142

I met the below problem and I searched the issues which don’t include this one. You can take a look below error:

ERROR: Cannot find Ninja

Traceback (most recent call last):
File «./build», line 679, in
Main().cli()
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 267, in cli
exit_status = self.cli_noexit(*args, **kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 258, in cli_noexit
return self._do_main(vars(args))
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 152, in _do_main
return self.main(**self._get_args(kwargs))
File «/home/sean/linux-kernel-module-cheat/common.py», line 1540, in main
ret = self.timed_main()
File «./build», line 674, in timed_main
ret = component.build(self.env[‘arch’])
File «./build», line 55, in build
return self.build_callback()
File «./build», line 471, in f
return lkmc.import_path.import_path_main(component_file)(**args)
File «/home/sean/linux-kernel-module-cheat/common.py», line 739, in call
return super().call(**kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 149, in call
return self._do_main(kwargs)
File «/home/sean/linux-kernel-module-cheat/cli_function.py», line 152, in _do_main
return self.main(**self._get_args(kwargs))
File «/home/sean/linux-kernel-module-cheat/common.py», line 1540, in main
ret = self.timed_main()
File «/home/sean/linux-kernel-module-cheat/common.py», line 2059, in timed_main
return self.build()
File «/home/sean/linux-kernel-module-cheat/build-qemu», line 38, in build
self.sh.run_cmd(
File «/home/sean/linux-kernel-module-cheat/shell_helpers.py», line 457, in run_cmd
raise e
Exception: Command exited with status:
if self.env[‘configure’]:
self.sh.run_cmd(
[
os.path.join(self.env[‘qemu_source_dir’], ‘configure’), LF,
‘—enable-trace-backends=simple’, LF,
‘—target-list=<>‘.format(target_list), LF,
‘—enable-sdl’, LF,
] +
build_type_cmd +
self.sh.shlex_split(self.env[‘extra_config_args’]),
extra_paths=[self.env[‘ccache_dir’]],
cwd=build_dir
)

The text was updated successfully, but these errors were encountered:

Источник

i have met a problem »’ CMake was unable to find a build program corresponding to «Ninja». »’ #108

share:xcbuild chen-pc$ make
mkdir -p build
cmake -Bbuild -H. -G Ninja -DCMAKE_INSTALL_PREFIX=
CMake Error: CMake was unable to find a build program corresponding to «Ninja». CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_C_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_C_COMPILER
CMake Error: Could not find cmake module file: /Users/chen-pc/xcbuild/build/CMakeFiles/3.2.2/CMakeCCompiler.cmake
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER
CMake Error: Could not find cmake module file: /Users/chen-pc/xcbuild/build/CMakeFiles/3.2.2/CMakeCXXCompiler.cmake
CMake Error at CMakeLists.txt:10 (project):
No CMAKE_C_COMPILER could be found.

Tell CMake where to find the compiler by setting the CMake cache entry
CMAKE_C_COMPILER to the full path to the compiler, or to the compiler name
if it is in the PATH.

CMake Error at CMakeLists.txt:10 (project):
No CMAKE_CXX_COMPILER could be found.

Tell CMake where to find the compiler by setting the CMake cache entry
CMAKE_CXX_COMPILER to the full path to the compiler, or to the compiler
name if it is in the PATH.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
— Configuring incomplete, errors occurred!

The text was updated successfully, but these errors were encountered:

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Updated Qemu install and fix botched pci passthru

Updated Qemu install and fix botched pci passthru

Post by sadpanda » Tue Mar 22, 2022 2:54 pm

xeon based system with two gpus, current mint install, trying to get PCI/Evdev passthru for win10 following these:

VM was booting with correct gpu but when I tried to add Evdev I would get a schema error. So per this guide:
https://passthroughpo.st/using-evdev-pa . -vm-input/
I tried changing virsh and adding qemu commands but that result in a vm that would not boot at all and I just noticed systemd-udevd is thrashing one cpu core at 100% all the time .

I then discovered ubuntu/mint package a very old version of qemu so I set off on updating. per:
https://wiki.qemu.org/Hosts/Linux#Fedor . tributions

and run .configure again and I get the following warnings/errors:

before I continue, how much of this needs addressed and how to I un-screw systemd-udevd ?

Thanks in advance.

Re: Updated Qemu install and fix botched pci passthru

Post by JoeFootball » Wed Mar 23, 2022 9:21 am

Re: Updated Qemu install and fix botched pci passthru

Post by sadpanda » Wed Mar 23, 2022 11:10 am

Thanks for the reply; please tell me if I’m reading this right as I’m very new to linux as a daily

ubuntu is in fact packaged with qemu 6.21 and ‘their’ packaged version is numbered 1.4.2-3 ? I’m not seeing much in the change log that would cause what I have going on.

Using strace and udevadm monitor I was able to track down the runaway process. Turned out to be nvidia driver stuck in some sort of loop. I decided to just timeshift back to before I started all this. CPU usage is normal but interestingly, nvidia card will not display anything despite driver being responsive. If I try to activate monitor I get:

The nvidia card is in the ‘preferred’ pci slot per HP, ATI card is set as primary in bios. Maybe nvidia card/driver doesn’t like being slave?

With some googling and package updates I was able to get the dependency list whittled down:

Источник

CMake was unable to find a build program corresponding to «Ninja». CMAKE_MAKE_PROGRAM is not set. #259

ninja —version is worked

[lookfe@troy xcbuild]$ make
which: no llbuild in (/home/lookfe/testIOS/ninja:/home/imgrec/anaconda2/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/lookfe/.local/bin:/home/lookfe/bin)
mkdir -p build
cmake -Bbuild -H. -G Ninja -DCMAKE_INSTALL_PREFIX=
CMake Error: CMake was unable to find a build program corresponding to «Ninja». CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_C_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_C_COMPILER
CMake Error: Could not find cmake module file: /home/lookfe/testIOS/xcbuild/build/CMakeFiles/2.8.12.2/CMakeCCompiler.cmake
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER_ENV_VAR
CMake Error: Error required internal CMake variable not set, cmake may be not be built correctly.
Missing variable is:
CMAKE_CXX_COMPILER
CMake Error: Could not find cmake module file: /home/lookfe/testIOS/xcbuild/build/CMakeFiles/2.8.12.2/CMakeCXXCompiler.cmake
— Configuring incomplete, errors occurred!
make: *** [all] 错误 1
[lookfe@troy xcbuild]$ ninja —version
1.7.2
[lookfe@troy xcbuild]$ uname -a
Linux troy 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

It looks can’t run in CentOS

The text was updated successfully, but these errors were encountered:

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

Решено: Ninja (opencv) (error: loading ‘build.ninja’)

Модератор: /dev/random

amd64) Контактная информация:

Решено: Ninja (opencv)

Сообщение devilr » 27.11.2018 16:05

Re: Ninja

Сообщение Bizdelnick » 27.11.2018 16:32

amd64) Контактная информация:

Re: Ninja

Сообщение devilr » 27.11.2018 16:39

Re: Ninja

Сообщение /dev/random » 27.11.2018 16:40

amd64) Контактная информация:

Re: Ninja

Сообщение devilr » 27.11.2018 16:50

Re: Ninja

Сообщение Bizdelnick » 27.11.2018 18:07

Источник

This article describes steps and how to solves isseus found in compiling QEMU on MSYS2 (https://www.msys2.org/).

Using 32 bit MINGW compiler tools to compile the 32 bit version of QEMU. The sources is downloaded from https://download.qemu.org/qemu-6.0.0.tar.xz. I’m using MSYS2 64 bit on Windows 10 with version below:

Installing gcc:

[user]@[workstation] MSYS ~
[hash] pacman -S mingw-w64-i686-gcc
resolving dependencies…
looking for conflicting packages…

Packages (14) mingw-w64-i686-binutils-2.36.1-3
mingw-w64-i686-crt-git-9.0.0.6166.0a00d0ea-1
mingw-w64-i686-gcc-libs-10.2.0-11 mingw-w64-i686-gmp-6.2.1-2

Try to perform configure:

[user]@[workstation] MINGW32 /d/projects/qemu
[hash] ./configure –cross-prefix=i686-w64-mingw32- 2>&1 | tee test.txt

But I have:

echo ‘ERROR: Python not found. Use –python=/path/to/python’
ERROR: Python not found. Use –python=/path/to/python

test -n ”

Install Python:

[user]@[workstation] MSYS ~
[hash] pacman -S mingw-w64-i686-python
resolving dependencies…
looking for conflicting packages…

It also requires Ninja for build framework:

echo ‘ERROR: Cannot find Ninja’
ERROR: Cannot find Ninja

test -n ”

echo

Install Ninja:

pacman -S ninja

Now I have:

../meson.build:1:0: ERROR: Unknown linker(s): [[‘i686-w64-mingw32-ar’]]
The follow exceptions were encountered:
Running “i686-w64-mingw32-ar –version” gave “[WinError 2] The system cannot find the file specified”

A full log can be found at D:/Projects/Qemu/build/meson-logs/meson-log.txt

test 1 -ne 0

error_exit ‘meson setup failed’

print_error ‘meson setup failed’

echo

Actually ar.exe already exist:

[user]@[workstation] MINGW32 /d/projects/qemu
[hash] ar
Usage: D:MSYS64mingw32binar.exe [emulation options] [-]{dmpqrstx}[abcDfilMNoOPsSTuvV] [–plugin ] [member-name] [count] archive-file file…
D:MSYS64mingw32binar.exe -M [<mri-script]

Perform rename:

Perform sanity check:

[user]@[workstation] MINGW32 /d/projects/qemu
[hash] i686-w64-mingw32-ar –version
GNU ar (GNU Binutils) 2.36.1
Copyright (C) 2021 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.

Has header “WinHvPlatform.h” : YES
Has header “WinHvEmulation.h” : YES
Run-time dependency appleframeworks found: NO (tried framework)
Found pkg-config: D:MSYS64mingw32bin/i686-w64-mingw32-pkg-config.EXE (0.29.2)
Run-time dependency pixman-1 found: NO (tried pkgconfig)

../meson.build:328:2: ERROR: Dependency “pixman-1” not found, tried pkgconfig

A full log can be found at D:/Projects/Qemu/build/meson-logs/meson-log.txt

Install pixman:

[user]@[workstation] MSYS ~
[hash] pacman -S pixman-1
error: target not found: pixman-1

[user]@[workstation] MSYS ~
[hash] pacman -S mingw-w64-i686-pixman
resolving dependencies…
looking for conflicting packages…

Packages (1) mingw-w64-i686-pixman-0.40.0-2

Total Download Size: 0.31 MiB
Total Installed Size: 1.59 MiB

:: Proceed with installation? [Y/n]

Program sphinx-build-3 sphinx-build found: NO
Program python3 found: YES (D:/MSYS64/mingw32/bin/python3.exe)
Program diff found: NO

../tests/qapi-schema/meson.build:207:0: ERROR: Program ‘diff’ not found

Install diff:

[user]@[workstation] MSYS ~
[hash] pacman -S diff
error: target not found: diff

[user]@[workstation] MSYS ~
[hash] pacman -S mingw-w64-i686-diffutils
resolving dependencies…
looking for conflicting packages…

Packages (2) mingw-w64-i686-libsigsegv-2.13-1 mingw-w64-i686-diffutils-3.6-2

Total Download Size: 0.38 MiB
Total Installed Size: 1.61 MiB

:: Proceed with installation? [Y/n]

There are no more issues. Perform build now:

[user]@[workstation] MINGW32 /d/projects/qemu
[hash] ninja -C build
[10/5486] Compiling C object libcapsto…stone_arch_AArch64_AArch64Module.c.obj

[user]@[workstation] MINGW32 /d/projects/qemu
[hash] ninja -C build
ninja: Entering directory `build’
[19/5459] Compiling C object libslirp.a.p/slirp_src_misc.c.obj
FAILED: libslirp.a.p/slirp_src_misc.c.obj
“i686-w64-mingw32-gcc” “-Ilibslirp.a.p” “-I.” “-I..” “-I../slirp” “-I../slirp/src” “-ID:/MSYS64/mingw32/include/glib-2.0” “-ID:/MSYS64/mingw32/lib/glib-2.0/include” “-ID:/MSYS64/mingw32/include” “-fdiagnostics-color=auto” “-pipe” “-Wall” “-Winvalid-pch” “-std=gnu99” “-O2” “-g” “-iquote” “.” “-iquote” “D:/Projects/Qemu” “-iquote” “D:/Projects/Qemu/include” “-iquote” “D:/Projects/Qemu/disas/libvixl” “-iquote” “D:/Projects/Qemu/tcg/i386” “-iquote” “D:/Projects/Qemu/accel/tcg” “-D_REENTRANT” “-U_FORTIFY_SOURCE” “-D_FORTIFY_SOURCE=2” “-m32” “-D_GNU_SOURCE” “-D_FILE_OFFSET_BITS=64” “-D_LARGEFILE_SOURCE” “-Wstrict-prototypes” “-Wredundant-decls” “-Wundef” “-Wwrite-strings” “-Wmissing-prototypes” “-fno-strict-aliasing” “-fno-common” “-fwrapv” “-Wold-style-declaration” “-Wold-style-definition” “-Wtype-limits” “-Wformat-security” “-Wformat-y2k” “-Winit-self” “-Wignored-qualifiers” “-Wempty-body” “-Wnested-externs” “-Wendif-labels” “-Wexpansion-to-defined” “-Wimplicit-fallthrough=2” “-Wno-missing-include-dirs” “-Wno-shift-negative-value” “-Wno-psabi” “-fstack-protector-strong” “-DG_LOG_DOMAIN=”Slirp”” -MD -MQ libslirp.a.p/slirp_src_misc.c.obj -MF “libslirp.a.p/slirp_src_misc.c.obj.d” -o libslirp.a.p/slirp_src_misc.c.obj “-c” ../slirp/src/misc.c
../slirp/src/misc.c:8:10: fatal error: sys/un.h: No such file or directory
8 | [hash]include
| ^~~~~~
compilation terminated.
[24/5459] Compiling C object libcapsto…_arch_AArch64_AArch64InstPrinter.c.obj
ninja: build stopped: subcommand failed.

Remove glib2-devel, perform re-configure:

[user]@[workstation] MSYS ~
[hash] pacman -R glib2-devel
checking dependencies…

Packages (1) glib2-devel-2.68.1-1

Total Removed Size: 5.69 MiB

:: Do you want to remove these packages? [Y/n] y
:: Processing package changes…
(1/1) removing glib2-devel ##… 100%

Perform remark the offending define that causes compile error:

D:MSYS64mingw32libglib-2.0includeglibconfig.h

Now I have:

[2055/5486] Linking target qemu-system-aarch64.exe
FAILED: qemu-system-aarch64.exe
“i686-w64-mingw32-g++” @qemu-system-aarch64.exe.rsp
D:/MSYS64/mingw32/bin/../lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/bin/ld.exe: libqemuutil.a(util_osdep.c.obj): in function qemu_mprotect__osdep': D:projectsqemubuild/../util/osdep.c:86: undefined reference to g_win32_error_message’
D:/MSYS64/mingw32/bin/../lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/bin/ld.exe: libqemuutil.a(util_error.c.obj): in function error_setg_win32_internal': D:projectsqemubuild/../util/error.c:184: undefined reference to g_win32_error_message’

Perform direct testing:

[user]@[workstation] MINGW32 /d/projects/qemu/build
[hash] “i686-w64-mingw32-g++” @qemu-system-aarch64.exe.rsp
D:/MSYS64/mingw32/bin/../lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/bin/ld.exe: libqemuutil.a(util_osdep.c.obj): in function qemu_mprotect__osdep': D:projectsqemubuild/../util/osdep.c:86: undefined reference tog_win32_error_message’
D:/MSYS64/mingw32/bin/../lib/gcc/i686-w64-mingw32/10.2.0/../../../../i686-w64-mingw32/bin/ld.exe: libqemuutil.a(util_error.c.obj): in function error_setg_win32_internal': D:projectsqemubuild/../util/error.c:184: undefined reference to g_win32_error_message’
collect2.exe: error: ld returned 1 exit status

Try to add glib2-devel and reconfigure:

[user]@[workstation] MSYS ~
[hash] pacman -S glib2-devel
resolving dependencies…
looking for conflicting packages…

Packages (1) glib2-devel-2.68.1-1

Total Installed Size: 5.69 MiB

But still with the same error. Try install glib2:

[user]@[workstation] MSYS ~
[hash] pacman -S mingw-w64-i686-glib2
resolving dependencies…
looking for conflicting packages…

Perform direct testing again, and this time the executable can be generated. Here is the partial result of the generated executable files:

This entry was posted on May 4, 2021 at 9:13 am and is filed under Miscellaneous. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.