Windows ninja error loading build ninja - Исправление ошибок и поиск оптимальных решений проблем

qingdujun@MacBook-Pro src % gn gen out/Release
ERROR at //third_party/fontconfig/fontconfig.gni:7:1: Assertion failed.
assert(is_linux)
^-----
See //third_party/fontconfig/BUILD.gn:6:1: whence it was imported.
import("//third_party/fontconfig/fontconfig.gni")
^-----------------------------------------------
See //headless/BUILD.gn:200:7: which caused the file to be included.
      "//third_party/fontconfig",
      ^-------------------------




qingdujun@MacBook-Pro src % autoninja -C out/Release/ headless_shell
ninja: Entering directory `out/Release/'
ninja: error: loading 'build.ninja': No such file or directory
Traceback (most recent call last):
  File "/Users/qingdujun/repos/workspace/depot_tools/ninjalog_uploader_wrapper.py", line 118, in <module>
    sys.exit(main())
  File "/Users/qingdujun/repos/workspace/depot_tools/ninjalog_uploader_wrapper.py", line 76, in main
    config = LoadConfig()
  File "/Users/qingdujun/repos/workspace/depot_tools/ninjalog_uploader_wrapper.py", line 31, in LoadConfig
    'chromium-build-stats.appspot.com'),
  File "/Users/qingdujun/repos/workspace/depot_tools/ninjalog_uploader.py", line 44, in IsGoogler
    _, content = h.request('https://'+server+'/should-upload', 'GET')
  File "/Users/qingdujun/.vpython-root/867170/lib/python2.7/site-packages/httplib2/__init__.py", line 1659, in request
    (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
  File "/Users/qingdujun/.vpython-root/867170/lib/python2.7/site-packages/httplib2/__init__.py", line 1399, in _request
    (response, content) = self._conn_request(conn, request_uri, method, body, headers)
  File "/Users/qingdujun/.vpython-root/867170/lib/python2.7/site-packages/httplib2/__init__.py", line 1355, in _conn_request
    response = conn.getresponse()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1108, in getresponse
    raise ResponseNotReady()
httplib.ResponseNotReady

Источник

I have followed esp-idf guideline to install and test to build the hello world and blink sample code but both the code met this problem.

Visual studio try to build hello world

> Executing task: ninja  <

ninja: error: loading 'build.ninja': The system cannot find the file specified.

The terminal process "C:WINDOWSSystem32WindowsPowerShellv1.0powershell.exe -Command ninja " terminated with exit code: 1.

I have tested all the ways I can find to fix it but I’m not sure anything I missed or not.

This is one of the way that I test but also met some problem.
cmd try to run the command below

C:Espressifframeworksesp-idf-v4.4>python -m pip install --user -r %IDF_PATH%/requirements.txt
    ERROR: Can not perform a '--user' install. User site-packages are not visible in this virtualenv.

This possible problem is the python environment is exist so I cannot do this command, but I try many ways to disabled or deactivated it still cannot.

python path

system environment

asked May 19, 2022 at 6:40

After trying to debug this for a long time, I made a backup copy of the entire project folder, then just went hog-wild deleting files. I deleted almost every file I didn’t author. Only left the main/CMakeLists.txt, main/component.mk, main/main.c, main/main.h, .gitignore, CMakeLists.txt, and Makefile. Then I ran idf.py set-target esp32 and idf.py -p /dev/ttyACM0 flash monitor and it worked fine again.

VS Code & ESP-IDF on Ubuntu 20.04.05 LTS

answered Nov 3, 2022 at 22:01

b264b264

3321 gold badge2 silver badges11 bronze badges

Check if the compiler is properly selected. If you don’t select a proper c/c++ compiler, then you might get this error. I had mingw in my system, but vs code did not auto detect the compiler. Then I manually added mingw and selected it for compilation after which this issue was resolved.

answered Dec 12, 2022 at 14:02

What worked for me after updating to the new stable release (v5.0) was

Go to the folder S:espesp-idfesp-idf-v5.0
Run command prompt at this directory and execute install.bat and later export.bat
After trying to build the program in VSCode the error «ninja: error: loading ‘build.ninja’» shows up.
Update the path in the ESP-IDF extension in VSCode using ESP-IDF:Configure Paths
locate your project folder e.g. «V:simpleTest_using_EspIDF_v5_0»
Open command prompt and execute: idf.py build
Now it builds also in VSCode using the Espressif IDF extension.

answered Jan 16 at 23:00

You not have a build.ninja file. Find this file on proje

answered Nov 10, 2022 at 21:47

Источник

AliceB: Posts: 12; Joined: Wed Apr 04, 2018 9:36 am

Windows 10 — ninja: error: loading ‘build.ninja’ : No

Good afternoon !

Thank you in advance for your attention, it is the first time I have to compile a software and I have some difficulties:

— I have followed the steps of the Build Instructions until Windows compilation
— Here come problems: when I launch build.cmd, I get:

Building sdk
Build type is set to: Release.
Visual Studio 2017 detection skipped as requested
Visual Studio 2015 detection skipped as requested
VStools: , VSCMake: Visual Studio 12 2013.
Compiler is: Visual Studio 12 2013
ninja: error: loading ‘build.ninja’ : No such file or directory
An error occured during buildong process
» «
Error while building «Release SDK» and the window closes

I have looked for ninja on internet but I don’t really get the point between all these build methods.
At each step my computer misses something… I might have downloaded Visual Studio without all the necessary options ?

I have also tried to follow the steps to get an IDE build with Visual Studio but I don’t understand how to generate Visual Studio .sln for both Debug and Release builds by running build —vsbuild-all option (as build.cmd doesn’t work)

Thank you very much for your attention (I need it !)
Alice

jtlindgren: Posts: 775; Joined: Tue Dec 04, 2012 3:53 pm; Location: INRIA Rennes, FRANCE

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by jtlindgren » Thu Apr 05, 2018 8:11 am

It that case its likely cmake does not generate the build.ninja file, though I don’t know why. Here’s what I suggest.

— Delete folders build/ and dist/
— Open windows command prompt CMD
— CD to the root of the source code
— Run «build.cmd >log.txt»

and paste the created log here. Maybe it’ll tell something useful.

Best,
Jussi

AliceB: Posts: 12; Joined: Wed Apr 04, 2018 9:36 am

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by AliceB » Thu Apr 05, 2018 8:33 am

Here is what I get:

C:workopenvibe>build.cmd >log.txt
CMake Error at CMakeLists.txt:8 (PROJECT):
No CMAKE_C_COMPILER could be found.

Tell CMake where to find the compiler by setting either the environment
variable «CC» or 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:8 (PROJECT):
No CMAKE_CXX_COMPILER could be found.

Tell CMake where to find the compiler by setting either the environment
variable «CXX» or 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.

Thanks,
Alice

AliceB: Posts: 12; Joined: Wed Apr 04, 2018 9:36 am

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by AliceB » Thu Apr 05, 2018 9:17 am

Here is my log.text:

Building sdk
Build type is set to: Release.
Visual Studio 2017 detection skipped as requested
Visual Studio 2015 detection skipped as requested
VStools: , VSCMake: Visual Studio 12 2013.
Compiler is: Visual Studio 12 2013
— The C compiler identification is unknown
— The CXX compiler identification is unknown
— Configuring incomplete, errors occurred!
See also «C:/work/openvibe/build/sdk-Release/CMakeFiles/CMakeOutput.log».
See also «C:/work/openvibe/build/sdk-Release/CMakeFiles/CMakeError.log».
An error occured during building process
«»
Error while building «Release SDK»

Thanks,
Alice

jtlindgren: Posts: 775; Joined: Tue Dec 04, 2012 3:53 pm; Location: INRIA Rennes, FRANCE

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by jtlindgren » Thu Apr 05, 2018 9:31 am

It looks like something is funky with your Visual Studio install in that case. Which version is it exactly?

Edit: it should print something like

VStools: C:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools, VSCMake: Visual Studio 12 2013.

For you, it prints an empty string before the comma.

Cheers,
Jussi

AliceB: Posts: 12; Joined: Wed Apr 04, 2018 9:36 am

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by AliceB » Thu Apr 05, 2018 11:03 am

I installed Visual Studio Community 2017 but I didn’t know which workloads or options were necessary for Openvibe.

I added Visual Studio Build Tools and other options but sincerely it was quite random, I didn’t find any CMake option.

Thank you for your patience,
Alice

jtlindgren: Posts: 775; Joined: Tue Dec 04, 2012 3:53 pm; Location: INRIA Rennes, FRANCE

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by jtlindgren » Thu Apr 05, 2018 11:17 am

That is very likely the problem. You need to have Visual Studio 2013 Express or Professional installed. You might get it to work with 2013 Community instead, but people have reported having trouble. I wouldn’t recommend it unless you’re an experienced programmer. We have no plans presently to get it to work on VS 2017.

Best,
Jussi

lslemon: Posts: 4; Joined: Tue Jun 12, 2018 3:11 pm

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by lslemon » Tue Jun 19, 2018 6:30 pm

Good afternoon

I am currently having issues with the building of the source code. I keep getting the error

«ninja: error: loading ‘build.ninja’: No such file or directory».

I have tried deleting and re-installing the dependencies, the builds and even cleared just the CMAKE cache from inside the build.
The full error I’m receiving is:

Building sdk
Build type is set to: Release.
Visual Studio 2017 detection skipped as requested
Visual Studio 2015 detection skipped as requested
VStools: C:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools, VSCMake: Visual Studio 12 2013.
Found Visual Studio 12 2013 tools: C:Program Files (x86)Microsoft Visual Studio 12.0Common7Toolsvsvars32.bat
Compiler is: Visual Studio 12 2013
— The C compiler identification is MSVC 18.0.40629.0
— The CXX compiler identification is MSVC 18.0.40629.0
— Check for working C compiler using: Ninja
— Check for working C compiler using: Ninja — broken
CMake Error at C:/work/openvibe/dependencies/cmake/share/cmake-3.4/Modules/CMakeTestCCompiler.cmake:61 (message):
The C compiler «C:/Program Files (x86)/Microsoft Visual Studio
12.0/VC/bin/cl.exe» is not able to compile a simple test program.

It fails with the following output:

Change Dir: C:/work/openvibe/build/sdk-Release/CMakeFiles/CMakeTmp

Run Build Command:»C:/work/openvibe/dependencies/ninja/ninja.exe»
«cmTC_99fdb»

[1/2] Building C object CMakeFilescmTC_99fdb.dirtestCCompiler.c.obj

[2/2] Linking C executable cmTC_99fdb.exe

FAILED: cmd.exe /C «cd . &&
C:workopenvibedependenciescmakebincmake.exe -E vs_link_exe
—intdir=CMakeFilescmTC_99fdb.dir —manifests —
C:PROGRA~2MICROS~2.0VCbinlink.exe /nologo
CMakeFilescmTC_99fdb.dirtestCCompiler.c.obj /out:cmTC_99fdb.exe
/implib:cmTC_99fdb.lib /pdb:cmTC_99fdb.pdb /version:0.0 /machine:X86 /debug
/INCREMENTAL /subsystem:console kernel32.lib user32.lib gdi32.lib
winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib
advapi32.lib && cd .»

LINK : fatal error LNK1104: cannot open file ‘gdi32.lib’

LINK Pass 1 failed. with 1104

ninja: build stopped: subcommand failed.

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:8 (PROJECT)

— Configuring incomplete, errors occurred!
See also «C:/work/openvibe/build/sdk-Release/CMakeFiles/CMakeOutput.log».
See also «C:/work/openvibe/build/sdk-Release/CMakeFiles/CMakeError.log».
An error occured during building process
«»
Error while building «Release SDK»

C:workopenvibe>build
Building sdk
Build type is set to: Release.
Visual Studio 2017 detection skipped as requested
Visual Studio 2015 detection skipped as requested
VStools: C:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools, VSCMake: Visual Studio 12 2013.
Found Visual Studio 12 2013 tools: C:Program Files (x86)Microsoft Visual Studio 12.0Common7Toolsvsvars32.bat
Compiler is: Visual Studio 12 2013
ninja: error: loading ‘build.ninja’: No such file or directory
An error occured during building process
«»
Error while building «Release SDK»

I’m aware that the error is stupidly long, but I was wondering if you have seen any issue like this before?

Thank you for reading and I hope to hear from you

Luke

jtlindgren: Posts: 775; Joined: Tue Dec 04, 2012 3:53 pm; Location: INRIA Rennes, FRANCE

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by jtlindgren » Wed Jun 20, 2018 7:59 am

Hi Luke,

the ‘clearest’ indicator there about the reason of the fail is that the ‘gdi32.lib’ seems to be missing.

Could it be this problem: https://stackoverflow.com/questions/335 … b/47175728

Since we generate everything by cmake we cannot directly apply the solution probably, but you could try to investigate if that library is really missing and if installing some specific SDK for your OS makes it appear. Try to google with the lib name.

Can you report back if you succeed to get it to work and how?

Thanks,
Jussi

lslemon: Posts: 4; Joined: Tue Jun 12, 2018 3:11 pm

Re: Windows 10 — ninja: error: loading ‘build.ninja’ : No

Post

by lslemon » Thu Jun 21, 2018 9:37 am

Hi Jussi,

I have been rooting through the internet looking for a solution to the problem, and when trying to download the windows SDK for Visual Studios 2013, it presented the issue that it isn’t compatible. DO you know if people have been able to build the software on windows 10?

I had the software working previously by just downloading the installer, and there were no issues apart from needing the drivers for the g.Nautilus headset. To get these drivers I am under the impression that I need to build the software using the source code?

Thanks for reading.
Luke.

Источник

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

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

devilr: Сообщения: 3450; ОС: Mandriva => Gentoo (~amd64); Контактная информация:

Решено: Ninja (opencv)

Решил собрать новый opencv — 3.4.1-r4
При сборке возникает ошибка:

Код: Выделить всё

 * ERROR: media-libs/opencv-3.4.1-r4::gentoo failed (compile phase):
 *   build.ninja not found. Error during configure stage.

Посмотрел, что за ninja — 1.8.2-r2 (вроде последняя)
Но, если её вызвать с простым параметром -v, будет

Код: Выделить всё

$ ninja -v
ninja: error: loading 'build.ninja': No such file or directory

Вопрос: кто виноват и что делать? В том смысле, что на багтрекере эта ошибка (сборки opencv) есть и висит неподтверждённой).
Это только у меня так?

Последний раз редактировалось devilr 27.11.2018 19:36, всего редактировалось 2 раза.

Мудрость приходит с возрастом.
Иногда возраст приходит один.
Digital Art

Bizdelnick: Модератор; Сообщения: 19826; Статус: nulla salus bello; ОС: Debian GNU/Linux

Re: Ninja

Сообщение

Bizdelnick » 27.11.2018 16:32

Очевидно, кто-то должен создать этот build.ninja (cmake?).

Пишите правильно:

в консоли
вку́пе (с чем-либо)
в общем
вообще

в течение (часа)
новичок
нюанс
по умолчанию

приемлемо
проблема
пробовать
трафик

devilr: Сообщения: 3450; ОС: Mandriva => Gentoo (~amd64); Контактная информация:

Re: Ninja

Сообщение

devilr » 27.11.2018 16:39

Bizdelnick писал: ↑

27.11.2018 16:32

Очевидно, кто-то должен создать этот build.ninja (cmake?).

Не так уж и очевидно, как по мне.

Код: Выделить всё

$ ninja --help
usage: ninja [options] [targets...]

if targets are unspecified, builds the 'default' target (see manual).

options:
  --version  print ninja version ("1.8.2.git.kitware.dyndep-1.jobserver-1")

  -C DIR   change to DIR before doing anything else
  -f FILE  specify input build file [default=build.ninja]

  -j N     run N jobs in parallel [default=10, derived from CPUs available]
  -k N     keep going until N jobs fail (0 means infinity) [default=1]
  -l N     do not start new jobs if the load average is greater than N
  -n       dry run (don't run commands but act like they succeeded)
  -v       show all command lines while building

  -d MODE  enable debugging (use '-d list' to list modes)
  -t TOOL  run a subtool (use '-t list' to list subtools)
    terminates toplevel options; further flags are passed to the tool
  -w FLAG  adjust warnings (use '-w list' to list warnings)

Соответственно, простой вызов параметра v должен показать «all command lines while building», а никак не ошибку.
Возможно, я где-то ошибаюсь…

Мудрость приходит с возрастом.
Иногда возраст приходит один.
Digital Art

/dev/random: Администратор; Сообщения: 5188; ОС: Gentoo

Re: Ninja

Сообщение

/dev/random » 27.11.2018 16:40

Там же в баге всё сказали: проблема из-за опечатки в ебилде opencv, написали «-BUILD_…» вместо «-DBUILD_…». В качестве обходного пути можете продаунгрейдить cmake: старые версии эту опечатку проглатывали нормально. А ninja тут ни при чём, ему положено так ругаться, если он запускается в каталоге без файла build.ninja.

devilr: Сообщения: 3450; ОС: Mandriva => Gentoo (~amd64); Контактная информация:

Re: Ninja

Сообщение

devilr » 27.11.2018 16:50

/dev/random писал: ↑

27.11.2018 16:40

Там же в баге всё сказали: проблема из-за опечатки в ебилде opencv, написали «-BUILD_…» вместо «-DBUILD_…». В качестве обходного пути можете продаунгрейдить cmake: старые версии эту опечатку проглатывали нормально. А ninja тут ни при чём, ему положено так ругаться, если он запускается в каталоге без файла build.ninja.

Ну, даунгрейдить cmake я пробовал — решения это не дало. А вот нарисовать патч — можно попробовать…

Мудрость приходит с возрастом.
Иногда возраст приходит один.
Digital Art

Bizdelnick: Модератор; Сообщения: 19826; Статус: nulla salus bello; ОС: Debian GNU/Linux

Re: Ninja

Сообщение

Bizdelnick » 27.11.2018 18:07

devilr писал(а): ↑

27.11.2018 16:39

Соответственно, простой вызов параметра v должен показать «all command lines while building», а никак не ошибку.

Чтобы показать команды сборки, надо знать команды сборки, а они как раз должны быть в build.ninja.

Последний раз редактировалось Bizdelnick 27.11.2018 18:39, всего редактировалось 1 раз.

Пишите правильно:

в консоли
вку́пе (с чем-либо)
в общем
вообще

в течение (часа)
новичок
нюанс
по умолчанию

приемлемо
проблема
пробовать
трафик

devilr: Сообщения: 3450; ОС: Mandriva => Gentoo (~amd64); Контактная информация:

Re: Ninja

Сообщение

devilr » 27.11.2018 18:09

Скопировал ebuild в /usr/local/portage, исправил «-BUILD_opencv_apps=» на «-DBUILD_opencv_apps=helps» — одна ошибка ушла, теперь появилась другая:

Код: Выделить всё

 * ERROR: media-libs/opencv-3.4.1-r4::x-portage failed (install phase):
 *   Header checksum mismatch, aborting.

Мудрость приходит с возрастом.
Иногда возраст приходит один.
Digital Art

devilr: Сообщения: 3450; ОС: Mandriva => Gentoo (~amd64); Контактная информация:

Re: Ninja (opencv)

Сообщение

devilr » 27.11.2018 19:36

Решением стало (пока временным, конечно) добавление флага «-abi_x86_32» и обычная сборка пакета.

Мудрость приходит с возрастом.
Иногда возраст приходит один.
Digital Art

Источник

Index
» Applications & Desktop Environments
» ninja: error: loading ‘build.ninja’: No such file or directory

Pages: 1

#1 2019-11-07 02:16:12

ArchDevel: Member; Registered: 2019-02-09; Posts: 3

ninja: error: loading ‘build.ninja’: No such file or directory

So I have been battling this issue for about a day now. I am hoping that someone could shed some light for me. I installed Ninja as a part of the SDK and development environment setup for the Zephyr Project and for the nrf Connect SDK. I am attempting to utilize the GIT clones of both of these locally to build an app for Zephyr utilizing its meta tool West. However when ever I pass the command:

 west build -b nrf9160_pca20035 samples/bluetooth/hci_uart

I am greeted with an error of:

—west build: build configuration:
source directory: /home/rex/.zephyrproject/zephyr/samples/bluetooth/hci_uart
build directory: /home/rex/.zephyrproject/zephyr/build
BOARD: nrf9160_pca20035 (origin: CMakeCache.txt)
—west build: building application
ninja: error: loading ‘build.ninja’ : No such file or directory
ERROR: command exited with status 1: /usr/bin/cmake —build /home/rex/.zephyrproject/zephyr/build

I do not know where to begin here. I have made sure all the dependencies have been met and my system is up to date. Can anyone shed some light?

The tool chain and environment was set with:

export ZEPHYR_TOOLCHAIN_VARIANT=zephyr

#2 2019-11-08 19:12:28

WSDMatty: Member; Registered: 2019-08-27; Posts: 20

Re: ninja: error: loading ‘build.ninja’: No such file or directory

Ninja requires a build.ninja file, which is similar to a Makefile. It tells Ninja what to build and how to build it. What that error is telling you, is that there is no build.ninja file present in the directory in which you are trying to run ninja.

I would look at the documentation for that project and see if you missed a step to produce the build file. For one of the projects I work on, Meson is used to produce the build file, then Ninja is used to build. Your project may handle this differently. But if you are meant to use ninja to build it, then somewhere, a build.ninja file must be created telling ninja how and what to build.

#3 2019-11-09 13:25:05

Lone_Wolf: Member; From: Netherlands, Europe; Registered: 2005-10-04; Posts: 10,652

Re: ninja: error: loading ‘build.ninja’: No such file or directory

BOARD: nrf9160_pca20035 (origin: CMakeCache.txt)

The cmake cache may have incorrect/outdated data, does west build have a parameter to force cmake to reconfigure ?
erasing the build folder often has the same effect.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B) && (time C > time B ) ≠ (A works at time C)

Источник

Спасибо В таком случае host-tools я уже собрал в Visual Studio (под MinGW он все равно не собирается).

Но как собрать reactos (та папка, что создалась и наполнилась в результате configure ninja)?
Там нет Makefile. Раз мне ninja не нужна, то можно попользоваться nmake. Но именно в reactos он сделать ничего не может.

Следующий вопрос, который обязательно последует — как собрать ISO образ.
Программу cdmake.exe я вижу в host-toolstoolscdmakeRelease
Ей нужно скормить параметры:

host-toolstoolscdmakeRelease>cdmake.exe
CDMAKE [-q] [-v] [-p] [-s N] [-m] [-b bootimage] [-j] source volume image

source specifications of base directory containing all files to
be written to CD-ROM image
volume volume label
image image file or device
-q quiet mode — display nothing but error messages
-v verbose mode — display file information as files are
scanned and written — overrides -p option
-p show progress while writing
-s N abort operation before beginning write if image will be
larger than N megabytes (i.e. 1024*1024*N bytes)
-m accept punctuation marks other than underscores in
names and extensions
-b bootimage create bootable ElTorito CD-ROM using ‘no emulation’ mode
-j generate Joliet filename records

Что надо будет указать в source? Папку reactos, которую я пока не могу собрать.

Добавлено:

Цели ninja в configure.cmd в принципе нет. Так что инструкция, явно устарела.
Да и конфигурация, как оказалось, проходит с ошибкой:

Для Visual Studio

…
CMake Error: Could not find cmake module file:/reactos/CMakeFiles/2.8.10.2-ReactOS/CMakeASMCompiler.cmake
…
— Configuring incomplete, errors occurred!
Configure script complete! Enter directories and execute appropriate build commands(ex: make, nmake, jom, etc…).

Для MinGW

Тоже самое. Версия cmake в RosBE с тем же номером. Для чистоты эксперимента, я удалял сmake, установленный отдельно для Visual Studio.

При конфигурировании для Visual Studio запускал командную строку для него же. В путях там не содержался bin из RosBE (помешать не могла).
Тем не менее, сообщение об ошибке есть. Не удивительно, что сборка до конца не идет да и идет ли она правильно, где получается (host-tools) …

Добавлено 2:

Решил попробовать собрать под Fedora 18. Мало ли … Может ReactOS разрабатывают под Linux …
Нет, скрипт configure.sh не готов к запуску. Окончания строк в нем от Windows — не распознается командный интерпретатор из-за этого (по первой строке). Пришлось поправить.
Но это отца русской демократии не спасло — «ReactOS-0.3.14/configure.sh: line 44: ошибка синтаксиса: неожиданный конец файла».
Под Linux ReactOS никто не собирал.

Итог — ReactOS просто не собирается. Сделать это могут те, кто участвует в разработке. Может это и правильно.

Да, я решил этим заняться под влиянием Курс «Операционные системы» в МГТУ им. Баумана с Алексеем Брагиным.
Сборка ReactOS там одна из лабораторных для студентов. Задача действительно нетривиальная. Ядро Linux (лет 15 назад этим баловался) у меня собиралось.

Источник

Having the same problem on Windows 10 64-bit pro. Source was downloaded on 10/30, so the version was whatever was posted on that day. However I just now ran update.bat, so presumably I’m on the latest version and still have the error.

I’m following the instructions at https://bitbucket.org/chromiumembedded/cef/wiki/MasterBuildQuickStart.md

There’s no build.ninja file in c:codechromium_gitchromiumsrc (or wherever it might be looking for it). I did a Windows file search inside c:code for «build.ninja». The only match is here: C:codechromium_gitchromiumsrctoolsbinary_sizelibsupersizetestdatamock_source_directoryoutReleasebuild.ninja

So if it isn’t where it should be, obviously something went wrong with its creation so I dug a little deeper.

Create.bat actually has an error in the output:

Code: Select all: Generating CEF project files... Traceback (most recent call last): File "c:/code/chromium_git/chromium/src/build/vs_toolchain.py", line 588, in <module> sys.exit(main()) File "c:/code/chromium_git/chromium/src/build/vs_toolchain.py", line 584, in main return commands[sys.argv[1]](*sys.argv[2:]) File "c:/code/chromium_git/chromium/src/build/vs_toolchain.py", line 562, in GetToolchainDir win_sdk_dir = SetEnvironmentAndGetSDKDir() File "c:/code/chromium_git/chromium/src/build/vs_toolchain.py", line 555, in SetEnvironmentAndGetSDKDir return NormalizePath(os.environ['WINDOWSSDKDIR']) File "c:codedepot_toolsbootstrap-3_8_0_chromium_8_binpythonbinlibos.py", line 425, in __getitem__ return self.data[key.upper()] KeyError: 'WINDOWSSDKDIR' ERROR at //build/config/win/visual_studio_version.gni:26:7: Script returned non-zero exit code. exec_script("../../vs_toolchain.py", [ "get_toolchain_dir" ], "scope") ^---------- Current dir: c:/code/chromium_git/chromium/src/out/Release_GN_x86/ Command: c:/code/depot_tools/bootstrap-3_8_0_chromium_8_bin/python/bin/python.exe c:/code/chromium_git/chromium/src/build/vs_toolchain.py get_toolchain_dir Returned 1. See //build/toolchain/win/midl.gni:7:1: whence it was imported. import("//build/config/win/visual_studio_version.gni") ^---------------------------------------------------- See //ui/accessibility/BUILD.gn:19:3: whence it was imported. import("//build/toolchain/win/midl.gni") ^-------------------------------------- See //BUILD.gn:157:7: which caused the file to be included. "//ui/accessibility:accessibility_unittests", ^------------------------------------------- Traceback (most recent call last): File "toolsgclient_hook.py", line 143, in <module> RunAction(src_dir, cmd) File "c:codechromium_gitchromiumsrcceftoolsgclient_util.py", line 36, in RunAction command, cwd=dir, always_show_header=True, print_stdout=True) File "c:codedepot_toolsgclient_utils.py", line 674, in CheckCallAndFilter rv, args, kwargs.get('cwd', None), None, None) subprocess2.CalledProcessError: Command 'gn gen out\Release_GN_x86 --ide=vs2017 --sln=cef --filters=//cef/*' returned non-zero exit status 1 in c:codechromium_gitchromiumsrc

The problem would appear to be happening with get_toolchain_dir

I found this related error report: https://www.magpcss.org/ceforum/viewtopic.php?f=6&t=17642. I am running in an Admin cmd window. My VS 2017 is not in the default location, but in E:binMicrosoft Visual Studio2017Community, if this matters.

I also found this https://bitbucket.org/chromiumembedded/cef/issues/2132/building-cef-by-following, which, in combination with the mention above of WINDOWSSDKDIR, I’m thinking I don’t have the right SDK version. I checked my VS 2017 Build Tools and have 10.0.17763.0.

So I check here https://bitbucket.org/chromiumembedded/cef/wiki/BranchesAndBuilding and find that it states clearly that you need SDK version Win 10.0.19041. After installing 10.0.19041, I get the exact same error.

The SDK was installed at E:Windows Kits. Thinking perhaps the non-standard directory was the issue, I created a symbolic link (directory type) from C:Program Files (x86)Windows Kits10 to E:Windows Kits10 and the installation proceeded past where it had before. So there is clearly an issue with the builder not detecting the correct installation location of the windows kit.

LESSONS LEARNED:
1. Double check the prerequisites;
2. If your Windows SDK is in a non-standard location, just create a symbolic directory link.

If there’s a better way to fix this, let me know, but at least I found a work-around.

Источник

View previous topic :: View next topic

Author

Message

DZoom
Tux’s lil’ helper

Joined: 13 Jun 2010
Posts: 78

Posted: Mon Jan 11, 2021 12:35 pm Post subject: [SOLVED] Ninja error, loading build.ninja fails

See last post for solution

Original post

Hi there,

While trying to get a world update through, i run into trouble because of some ninja issue i don’t get.

The package is app-accessibility/at-spi2-core, but the m=problem (ninja.build fails) seems to be more general.

If i would guess, i would say the fact that directly calling ninja fails as well:

Code:

$ ninja

ninja: error: loading ‘build.ninja’: No such file or directory

Details on the failed package install:

Code:

# emerge —info ‘=app-accessibility/at-spi2-core-2.36.0::gentoo’

Portage 3.0.12 (python 3.8.6-final-0, default/linux/amd64/17.1/desktop, gcc-9.3.0, glibc-2.32-r3, 5.4.80-gentoo-r1 x86_64)

=================================================================

System Settings

=================================================================

System uname: Linux-5.4.80-gentoo-r1-x86_64-Intel-R-_Core-TM-_i7-4770_CPU_@_3.40GHz-with-glibc2.2.5

KiB Mem: 16322604 total, 8795696 free

KiB Swap: 16383996 total, 16383740 free

Timestamp of repository gentoo: Fri, 08 Jan 2021 17:05:15 +0000

Head commit of repository gentoo: 47764f26c055fccd5076c2bc24f4168b589499f0

sh bash 5.0_p18

ld GNU ld (Gentoo 2.32 p2) 2.32.0

app-shells/bash: 5.0_p18::gentoo

dev-java/java-config: 2.3.1::gentoo

dev-lang/perl: 5.30.3::gentoo

dev-lang/python: 2.7.18-r5::gentoo, 3.8.6-r1::gentoo, 3.9.0-r1::gentoo

dev-util/cmake: 3.17.4-r1::gentoo

dev-util/pkgconfig: 0.29.2::gentoo

sys-apps/baselayout: 2.7::gentoo

sys-apps/openrc: 0.41.2::gentoo

sys-apps/sandbox: 2.20::gentoo

sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo

sys-devel/automake: 1.11.6-r3::gentoo, 1.13.4-r2::gentoo, 1.16.2-r1::gentoo

sys-devel/binutils: 2.32-r1::gentoo, 2.34-r2::gentoo

sys-devel/gcc: 9.3.0-r2::gentoo

sys-devel/gcc-config: 2.3.2-r1::gentoo

sys-devel/libtool: 2.4.6-r6::gentoo

sys-devel/make: 4.2.1-r4::gentoo

sys-kernel/linux-headers: 5.4-r1::gentoo (virtual/os-headers)

sys-libs/glibc: 2.32-r3::gentoo

Repositories:

gentoo

location: /var/db/repos/gentoo

sync-type: git

sync-uri: https://github.com/gentoo-mirror/gentoo

priority: -1000

crossdev

location: /usr/local/portage-crossdev

masters: gentoo

priority: 10

ACCEPT_KEYWORDS=»amd64″

ACCEPT_LICENSE=»@FREE»

CBUILD=»x86_64-pc-linux-gnu»

CFLAGS=»-march=core-avx2 -O3 -pipe»

CHOST=»x86_64-pc-linux-gnu»

CONFIG_PROTECT=»/etc /usr/share/gnupg/qualified.txt»

CONFIG_PROTECT_MASK=»/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c»

CXXFLAGS=»-march=core-avx2 -O3 -pipe»

DISTDIR=»/usr/portage/distfiles»

EMERGE_DEFAULT_OPTS=»-j8″

ENV_UNSET=»CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR»

FCFLAGS=»-O2 -pipe»

FEATURES=»assume-digests binpkg-docompress binpkg-dostrip binpkg-logs candy config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr»

FFLAGS=»-O2 -pipe»

GENTOO_MIRRORS=»ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ ftp://gentoo.mirror.web4u.cz/ ftp://ftp.spline.inf.fu-berlin.de/mirrors/gentoo/ ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo»

LANG=»en_US.utf8″

LDFLAGS=»-Wl,-O1 -Wl,—as-needed»

LINGUAS=»en de»

MAKEOPTS=»-j9″

PKGDIR=»/var/cache/binpkgs»

PORTAGE_CONFIGROOT=»/»

PORTAGE_RSYNC_OPTS=»—recursive —links —safe-links —perms —times —omit-dir-times —compress —force —whole-file —delete —stats —human-readable —timeout=180 —exclude=/distfiles —exclude=/local —exclude=/packages —exclude=/.git»

PORTAGE_TMPDIR=»/var/tmp»

USE=»X a52 aac acl acpi alsa amd64 avahi berkdb branding bzip2 cairo cdda cdr cjk cli consolekit crypt cups dbus dri dts dvd dvdr elogind emboss encode exif fbcon ffmpeg fftw flac fortran ftp gdbm gif git gnutls gphoto2 gpm gtk gui iconv icu inotify ios ipod jpeg jpeg2k latex lcms ldap libglvnd libtirpc mad matroska mmx mng mp3 mp4 mpd mpeg mtp ncurses nls nptl nvidia ogg openal opengl openmp pam pango pcre pdf png policykit ppds raw readline sdl seccomp smp spell split-usr sse sse2 sse3 sse4_1 ssl ssse3 startup-notification subversion svg syslog tcpd threads thunar tiff truetype udev udisks unicode upower usb vaapi vcd vdpau videos vorbis wxwidgets x264 xattr xcb xft xml xv xvid zeroconf zlib» ABI_X86=»64″ ADA_TARGET=»gnat_2018″ ALSA_CARDS=»hda-intel» APACHE2_MODULES=»authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias» CALLIGRA_FEATURES=»karbon sheets words» COLLECTD_PLUGINS=»df interface irq load memory rrdtool swap syslog» CPU_FLAGS_X86=»aes avx avx2 fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3″ ELIBC=»glibc» GPSD_PROTOCOLS=»ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx» GRUB_PLATFORMS=»efi-64″ INPUT_DEVICES=»evdev» KERNEL=»linux» L10N=»en en-US de» LCD_DEVICES=»bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text» LIBREOFFICE_EXTENSIONS=»presenter-console presenter-minimizer» LUA_SINGLE_TARGET=»lua5-1″ LUA_TARGETS=»lua5-1″ OFFICE_IMPLEMENTATION=»libreoffice» PHP_TARGETS=»php7-3 php7-4″ POSTGRES_TARGETS=»postgres10 postgres11″ PYTHON_SINGLE_TARGET=»python3_8″ PYTHON_TARGETS=»python2_7 python3_8″ RUBY_TARGETS=»ruby25 ruby26″ USERLAND=»GNU» VIDEO_CARDS=»nvidia» XTABLES_ADDONS=»quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account»

Unset: CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

Complete build log:

Code:

# cat /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/temp/build.log

* Package: app-accessibility/at-spi2-core-2.36.0

* Repository: gentoo

* Maintainer: gnome@gentoo.org

* USE: X abi_x86_64 amd64 elibc_glibc introspection kernel_linux userland_GNU

* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox

>>> Unpacking source…

>>> Unpacking at-spi2-core-2.36.0.tar.xz to /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work

>>> Source unpacked in /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work

>>> Preparing source in /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0 …

* Applying at-spi2-core-2.0.2-disable-teamspaces-test.patch …

[ ok ]

>>> Source prepared.

>>> Configuring source in /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0 …

* abi_x86_64.amd64: running multilib-minimal_abi_src_configure

meson setup —buildtype plain —libdir lib64 —localstatedir /var/lib —prefix /usr —sysconfdir /etc —wrap-mode nodownload —build.pkg-config-path /usr/share/pkgconfig —pkg-config-path /usr/share/pkgconfig —native-file /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/temp/meson.x86_64-pc-linux-gnu.amd64.ini -Dsystemd_user_dir=/usr/lib/systemd/user -Ddocs=false -Dintrospection=yes -Dx11=yes /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0 /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64

The Meson build system

Version: 0.55.3

Source dir: /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0

Build dir: /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64

Build type: native build

Project name: at-spi2-core

Project version: 2.36.0

C compiler for the host machine: x86_64-pc-linux-gnu-gcc (gcc 9.3.0 «x86_64-pc-linux-gnu-gcc (Gentoo 9.3.0-r2 p4) 9.3.0»)

C linker for the host machine: x86_64-pc-linux-gnu-gcc ld.bfd 2.32

Host machine cpu family: x86_64

Host machine cpu: x86_64

Found pkg-config: /usr/bin/x86_64-pc-linux-gnu-pkg-config (0.29.2)

Run-time dependency dbus-1 found: YES 1.12.16

Run-time dependency glib-2.0 found: YES 2.60.6

Run-time dependency gobject-2.0 found: YES 2.60.6

Run-time dependency gio-2.0 found: YES 2.60.6

Checking for function «dlopen» : NO

Checking for function «dlopen» : YES

Library dl found: YES

Run-time dependency x11 found: YES 1.6.8

Run-time dependency xtst found: YES 1.2.3

Checking for function «XkbGetMap» with dependencies x11, xtst: YES

Run-time dependency xi found: YES 1.7.10

Checking for alignment of «char» : 1

Checking for alignment of «double» : 8

Checking for alignment of «dbus_bool_t» with dependency dbus-1: 4

Checking for alignment of «dbus_int16_t» with dependency dbus-1: 2

Checking for alignment of «dbus_int32_t» with dependency dbus-1: 4

Checking for alignment of «dbus_int64_t» with dependency dbus-1: 8

Checking for alignment of «dbind_pointer» : 8

Checking for alignment of «dbind_struct» : 1

Run-time dependency gobject-introspection-1.0 found: YES 1.64.1

Program xgettext found: YES

Configuring config.h using configuration

Found pkg-config: /usr/bin/x86_64-pc-linux-gnu-pkg-config (0.29.2)

Program glib-genmarshal found: YES

Program glib-mkenums found: YES

Build-time dependency gobject-introspection-1.0 found: YES 1.64.1

Program g_ir_scanner found: YES (/usr/bin/g-ir-scanner)

Program g_ir_compiler found: YES (/usr/bin/g-ir-compiler)

Configuring accessibility.conf using configuration

Configuring at-spi-dbus-bus.desktop using configuration

Configuring org.a11y.Bus.service using configuration

Configuring at-spi-dbus-bus.service using configuration

Program dbus-daemon found: YES

Program dbus-broker-launch found: NO

Configuring org.a11y.atspi.Registry.service using configuration

Build targets in project: 14

Option buildtype is: plain [default: debugoptimized]

Found ninja-1.10.1 at /usr/bin/ninja

>>> Source configured.

>>> Compiling source in /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0 …

* abi_x86_64.amd64: running multilib-minimal_abi_src_compile

ninja -v -j9 -l0 -C /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64

ninja: Entering directory `/var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64′

[1/57] /usr/bin/glib-genmarshal —prefix atspi_marshal —output atspi/atspimarshal.c —body ../at-spi2-core-2.36.0/atspi/atspimarshal.list —include-header atspimarshal.h

FAILED: atspi/atspimarshal.c

/usr/bin/glib-genmarshal —prefix atspi_marshal —output atspi/atspimarshal.c —body ../at-spi2-core-2.36.0/atspi/atspimarshal.list —include-header atspimarshal.h

/usr/bin/env: ‘python3.6’: No such file or directory

[2/57] /usr/bin/glib-genmarshal —prefix atspi_marshal —output atspi/atspimarshal.h —pragma-once —header ../at-spi2-core-2.36.0/atspi/atspimarshal.list

FAILED: atspi/atspimarshal.h

/usr/bin/glib-genmarshal —prefix atspi_marshal —output atspi/atspimarshal.h —pragma-once —header ../at-spi2-core-2.36.0/atspi/atspimarshal.list

/usr/bin/env: ‘python3.6’: No such file or directory

[3/57] x86_64-pc-linux-gnu-gcc -Idbind/dbind-test.p -Idbind -I../at-spi2-core-2.36.0/dbind -I. -I../at-spi2-core-2.36.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -D_POSIX_C_SOURCE=200809L -D_DEFAULT_SOURCE -march=core-avx2 -O3 ‘-DG_LOG_DOMAIN=»dbind»‘ -MD -MQ dbind/dbind-test.p/.._atspi_atspi-gmain.c.o -MF dbind/dbind-test.p/.._atspi_atspi-gmain.c.o.d -o dbind/dbind-test.p/.._atspi_atspi-gmain.c.o -c ../at-spi2-core-2.36.0/atspi/atspi-gmain.c

[4/57] x86_64-pc-linux-gnu-gcc -Idbind/dbind-test.p -Idbind -I../at-spi2-core-2.36.0/dbind -I. -I../at-spi2-core-2.36.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -D_POSIX_C_SOURCE=200809L -D_DEFAULT_SOURCE -march=core-avx2 -O3 ‘-DG_LOG_DOMAIN=»dbind»‘ -MD -MQ dbind/dbind-test.p/dbind.c.o -MF dbind/dbind-test.p/dbind.c.o.d -o dbind/dbind-test.p/dbind.c.o -c ../at-spi2-core-2.36.0/dbind/dbind.c

[5/57] x86_64-pc-linux-gnu-gcc -Idbind/dbind-test.p -Idbind -I../at-spi2-core-2.36.0/dbind -I. -I../at-spi2-core-2.36.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -D_POSIX_C_SOURCE=200809L -D_DEFAULT_SOURCE -march=core-avx2 -O3 ‘-DG_LOG_DOMAIN=»dbind»‘ -MD -MQ dbind/dbind-test.p/dbtest.c.o -MF dbind/dbind-test.p/dbtest.c.o.d -o dbind/dbind-test.p/dbtest.c.o -c ../at-spi2-core-2.36.0/dbind/dbtest.c

[6/57] x86_64-pc-linux-gnu-gcc -Ibus/at-spi-bus-launcher.p -Ibus -I../at-spi2-core-2.36.0/bus -I. -I../at-spi2-core-2.36.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -I/usr/lib64/libffi/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -D_POSIX_C_SOURCE=200809L -D_DEFAULT_SOURCE -march=core-avx2 -O3 -pthread ‘-DSYSCONFDIR=»/etc»‘ ‘-DDATADIR=»/usr/share»‘ ‘-DDBUS_DAEMON=»/usr/bin/dbus-daemon»‘ -MD -MQ bus/at-spi-bus-launcher.p/at-spi-bus-launcher.c.o -MF bus/at-spi-bus-launcher.p/at-spi-bus-launcher.c.o.d -o bus/at-spi-bus-launcher.p/at-spi-bus-launcher.c.o -c ../at-spi2-core-2.36.0/bus/at-spi-bus-launcher.c

../at-spi2-core-2.36.0/bus/at-spi-bus-launcher.c: In function ‘sigterm_handler’:

../at-spi2-core-2.36.0/bus/at-spi-bus-launcher.c:765:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]

765 | write (sigterm_pipefd[1], «X», 1);

| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[7/57] /usr/lib/python-exec/python3.8/meson —internal exe —capture atspi/atspi-enum-types.h — /usr/bin/glib-mkenums —template /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64/../at-spi2-core-2.36.0/atspi/atspi-enum-types.h.template /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64/../at-spi2-core-2.36.0/atspi/atspi-constants.h /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64/../at-spi2-core-2.36.0/atspi/atspi-types.h

FAILED: atspi/atspi-enum-types.h

/usr/lib/python-exec/python3.8/meson —internal exe —capture atspi/atspi-enum-types.h — /usr/bin/glib-mkenums —template /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64/../at-spi2-core-2.36.0/atspi/atspi-enum-types.h.template /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64/../at-spi2-core-2.36.0/atspi/atspi-constants.h /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64/../at-spi2-core-2.36.0/atspi/atspi-types.h

/usr/bin/env: ‘python3.6’: No such file or directory

[8/57] x86_64-pc-linux-gnu-gcc -Idbind/dbind-test.p -Idbind -I../at-spi2-core-2.36.0/dbind -I. -I../at-spi2-core-2.36.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 -D_POSIX_C_SOURCE=200809L -D_DEFAULT_SOURCE -march=core-avx2 -O3 ‘-DG_LOG_DOMAIN=»dbind»‘ -MD -MQ dbind/dbind-test.p/dbind-any.c.o -MF dbind/dbind-test.p/dbind-any.c.o.d -o dbind/dbind-test.p/dbind-any.c.o -c ../at-spi2-core-2.36.0/dbind/dbind-any.c

ninja: build stopped: subcommand failed.

* ERROR: app-accessibility/at-spi2-core-2.36.0::gentoo failed (compile phase):

* ninja -v -j9 -l0 -C /var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64 failed

*

* Call stack:

* ebuild.sh, line 125: Called src_compile

* environment, line 2826: Called multilib-minimal_src_compile

* environment, line 1767: Called multilib_foreach_abi ‘multilib-minimal_abi_src_compile’

* environment, line 2037: Called multibuild_foreach_variant ‘_multilib_multibuild_wrapper’ ‘multilib-minimal_abi_src_compile’

* environment, line 1702: Called _multibuild_run ‘_multilib_multibuild_wrapper’ ‘multilib-minimal_abi_src_compile’

* environment, line 1700: Called _multilib_multibuild_wrapper ‘multilib-minimal_abi_src_compile’

* environment, line 568: Called multilib-minimal_abi_src_compile

* environment, line 1761: Called multilib_src_compile

* environment, line 2249: Called meson_src_compile

* environment, line 1589: Called eninja ‘-C’ ‘/var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64’

* environment, line 1177: Called die

* The specific snippet of code:

* «$@» || die «${nonfatal_args[@]}» «${*} failed»

*

* If you need support, post the output of `emerge —info ‘=app-accessibility/at-spi2-core-2.36.0::gentoo’`,

* the complete build log and the output of `emerge -pqv ‘=app-accessibility/at-spi2-core-2.36.0::gentoo’`.

* The complete build log is located at ‘/var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/temp/build.log’.

* The ebuild environment file is located at ‘/var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/temp/environment’.

* Working directory: ‘/var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0-abi_x86_64.amd64’

* S: ‘/var/tmp/portage/app-accessibility/at-spi2-core-2.36.0/work/at-spi2-core-2.36.0’

Code:

# emerge -pqv ‘=app-accessibility/at-spi2-core-2.36.0::gentoo’

[ebuild U ] app-accessibility/at-spi2-core-2.36.0 [2.30.1] USE=»X introspection -gtk-doc -test» ABI_X86=»(64) -32 (-x32)»

make.conf:

Code:

# These settings were set by the catalyst build script that automatically

# built this stage.

# Please consult /usr/share/portage/config/make.conf.example for a more

# detailed example.

# conservatice flags for testing

#CFLAGS=»-march=core-avx2 -O2 -pipe»

#CXXFLAGS=»${CFLAGS} -finline-functions»

# useful flags

CFLAGS=»-march=core-avx2 -O3 -pipe»

CXXFLAGS=»${CFLAGS}»

# WARNING: Changing your CHOST is not something that should be done lightly.

# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.

CHOST=»x86_64-pc-linux-gnu»

MAKEOPTS=»-j9″

# gentoo mirrors; lookup is performed from left to right through the list

GENTOO_MIRRORS=»ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ ftp://gentoo.mirror.web4u.cz/ ftp://ftp.spline.inf.fu-berlin.de/mirrors/gentoo/ ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo»

# european sync-server (is this important?)

#SYNC=»rsync://rsync.de.gentoo.org/gentoo-portage»

# These are the USE flags that were used in addition to what is provided by the

# profile used for building.

USE=»X -gnome -kde a52 aac acpi avahi alsa -bindist -bluetooth cdr cjk consolekit cups dbus -doc dvd dvdr fbcon ffmpeg fftw ftp -geolocation gif git gtk gnutls gphoto2 -hal icu inotify ios ipod -ipv6 jpeg jpeg2k latex ldap -libglvnd -libnotify -llvm matroska mmx mp3 mp4 mpeg mpd mtp -multilib nvidia ogg openal opengl pam pdf -plasma png policykit -python -qt4 -qt5 raw -rupy smp sse sse2 sse3 ssse3 sse4_1 ssl -static -static-libs svg subversion syslog -systemd threads thunar tiff truetype udev unicode usb vcd vaapi vdpau videos vorbis -wifi x264 xft -xosd xvid zeroconf»

CPU_FLAGS_X86=»aes avx avx2 fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3″

INPUT_DEVICES=»evdev»

VIDEO_CARDS=»nvidia»

ALSA_CARDS=»hda-intel»

# from before conversion to /var/db/repos/gentoo

#PORTDIR=»/usr/portage»

#DISTDIR=»${PORTDIR}/distfiles»

#PKGDIR=»${PORTDIR}/packages»

FEATURES=»candy»

EMERGE_DEFAULT_OPTS=»-j8″

# languages for libreoffice and co.

LINGUAS=»en de»

L10N=»en en-US de»

# necessary entry for cross compiling avr shit

# from before conversion to /var/db/repos/gentoo

# (hopefully commenting this out was enough)

#PORTDIR_OVERLAY=»/usr/local/portage»

GRUB_PLATFORMS=»efi-64″

#PYTHON_TARGETS=»python2_7 python3_9″

#PYTHON_SINGLE_TARGET=»python3_9″

emerge —info:

Code:

Portage 3.0.12 (python 3.8.6-final-0, default/linux/amd64/17.1/desktop, gcc-9.3.0, glibc-2.32-r3, 5.4.80-gentoo-r1 x86_64)

=================================================================

System uname: Linux-5.4.80-gentoo-r1-x86_64-Intel-R-_Core-TM-_i7-4770_CPU_@_3.40GHz-with-glibc2.2.5

KiB Mem: 16322604 total, 8647400 free

KiB Swap: 16383996 total, 16383740 free

Timestamp of repository gentoo: Fri, 08 Jan 2021 17:05:15 +0000

Head commit of repository gentoo: 47764f26c055fccd5076c2bc24f4168b589499f0

gentoo

location: /var/db/repos/gentoo

sync-type: git

sync-uri: https://github.com/gentoo-mirror/gentoo

priority: -1000

crossdev

location: /usr/local/portage-crossdev

masters: gentoo

priority: 10

Last edited by DZoom on Mon Jan 11, 2021 2:07 pm; edited 1 time in total

fedeliallalinea
Administrator

Joined: 08 Mar 2003
Posts: 29430
Location: here

Posted: Mon Jan 11, 2021 12:56 pm Post subject:

Code:

/usr/bin/env: ‘python3.6’: No such file or directory

You have some problem with PYTHON_TARGETS, what return command emerge -uUD @world?
_________________
Questions are guaranteed in life; Answers aren’t.

DZoom
Tux’s lil’ helper

Joined: 13 Jun 2010
Posts: 78

Posted: Mon Jan 11, 2021 1:20 pm Post subject:

fedeliallalinea wrote:

Code:

/usr/bin/env: ‘python3.6’: No such file or directory

You have some problem with PYTHON_TARGETS, what return command emerge -uUD @world?

Python 3.6 is not installed and i wasn’t planning to install it any more (see the topic i created yesterday: https://forums.gentoo.org/viewtopic-t-1127755.html)

I was invoking the world update via

Code:

# emerge -avDNu —with-bdeps=y —backtrack=100 —keep-going @world

The update fails at the very package i mentioned before, with a lot of existing preserved libs at the moment (i assume that will clear up when the update runs through). The output is the same as with the call you proposed.

https://pastebin.com/8gSmTNqv

fedeliallalinea
Administrator

Joined: 08 Mar 2003
Posts: 29430
Location: here

Posted: Mon Jan 11, 2021 1:35 pm Post subject:

Now I see that

Code:

[1/57] /usr/bin/glib-genmarshal —prefix atspi_marshal —output atspi/atspimarshal.h —pragma-once —header ../at-spi2-core-2.36.0/atspi/atspimarshal.list

FAILED: atspi/atspimarshal.h

The command glib-genmarshal is provided by dev-util/glib-utils package, maybe you should update it first
_________________
Questions are guaranteed in life; Answers aren’t.

DZoom
Tux’s lil’ helper

Joined: 13 Jun 2010
Posts: 78

Posted: Mon Jan 11, 2021 2:06 pm Post subject:

fedeliallalinea wrote:

Now I see that

Code:

[1/57] /usr/bin/glib-genmarshal —prefix atspi_marshal —output atspi/atspimarshal.h —pragma-once —header ../at-spi2-core-2.36.0/atspi/atspimarshal.list

FAILED: atspi/atspimarshal.h

The command glib-genmarshal is provided by dev-util/glib-utils package, maybe you should update it first

Updating glib-utils first brought me one step further, thanks a lot!

If time allows it i will write up which tools should be updated before the large world update.

I have the feeling most of the time we are solving build-environment issues anyway, the program and lib updates mostly run through if the toolchain is healthy.

Thanks again.

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник