I am currently trying to compile some Rust code and am coming across an error in ninja compilation when trying to compile skia-bindings package in Rust.
Checking for "C:\\Program Files\\LLVM\\bin\\clang-cl.exe"
Checking for "C:\\LLVM\\bin\\clang-cl.exe"
ninja: error: manifest 'build.ninja' still dirty after 100 tries
The error in question can be further seen with context in the full error code:
Compiling skia-bindings v0.53.0
error: failed to run custom build command for `skia-bindings v0.53.0`
Caused by:
process didn't exit successfully: `C:\Users\(my user name)\Documents\Visual Studio Code\(my project)\target\debug\build\skia-bindings-c451d9d6ef96ce63\build-script-build` (exit code: 101)
--- stdout
cargo:rerun-if-env-changed=SKIA_DEBUG
cargo:rerun-if-env-changed=SKIA_SOURCE_DIR
cargo:rerun-if-env-changed=FORCE_SKIA_BUILD
cargo:rerun-if-env-changed=FORCE_SKIA_BINARIES_DOWNLOAD
TRYING TO DOWNLOAD AND INSTALL SKIA BINARIES: 0.53.0/ab8bc4dfa8fc85713027-x86_64-pc-windows-msvc-d3d-gl
cargo:rerun-if-env-changed=SKIA_BINARIES_URL
FROM: https://github.com/rust-skia/skia-binaries/releases/download/0.53.0/skia-binaries-ab8bc4dfa8fc85713027-x86_64-pc-windows-msvc-d3d-gl.tar.gz
DOWNLOAD AND INSTALL FAILED: https://github.com/rust-skia/skia-binaries/releases/download/0.53.0/skia-binaries-ab8bc4dfa8fc85713027-x86_64-pc-windows-msvc-d3d-gl.tar.gz: status code 404
STARTING A FULL BUILD
cargo:rerun-if-env-changed=CLANGCC
cargo:rerun-if-env-changed=CC
cargo:rerun-if-env-changed=CLANGCXX
cargo:rerun-if-env-changed=CXX
HOST: x86_64-pc-windows-msvc
cargo:rerun-if-env-changed=OPT_LEVEL
cargo:rerun-if-env-changed=SKIA_USE_SYSTEM_LIBRARIES
cargo:rerun-if-env-changed=SDKTARGETSYSROOT
cargo:rerun-if-env-changed=SDKROOT
cargo:rerun-if-env-changed=VCINSTALLDIR
cargo:rerun-if-env-changed=LLVM_HOME
cargo:rerun-if-env-changed=USERPROFILE
cargo:rerun-if-env-changed=SKIA_NINJA_COMMAND
cargo:rerun-if-env-changed=SKIA_GN_COMMAND
Probing 'python'
Python 3 found: "python"
Synchronizing Skia dependencies
Skipping "bin".
skia\third_party/externals/wuffs
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/piex
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/brotli
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/d3d12allocator
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/freetype
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/icu
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/harfbuzz
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/libgifcodec
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/zlib
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/expat
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/libjpeg-turbo
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/vulkanmemoryallocator
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/libpng
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/libwebp
IS NOT TOP-LEVEL GIT DIRECTORY.
skia\third_party/externals/spirv-cross
IS NOT TOP-LEVEL GIT DIRECTORY.
Skia args: is_official_build=true is_debug=false skia_enable_gpu=true skia_enable_skottie=false skia_use_gl=true skia_use_egl=false skia_use_x11=false skia_use_system_libpng=false skia_use_libwebp_encode=false skia_use_libwebp_decode=false skia_use_system_zlib=false skia_use_xps=false skia_use_dng_sdk=false cc="clang" cxx="clang++" skia_use_direct3d=true skia_use_icu=false skia_use_system_libjpeg_turbo=false win_vc="C:\Program Files\Microsoft Visual Studio\2022\Community\VC" clang_win="C:\LLVM" target_cpu="x86_64" skia_use_expat=true skia_use_system_expat=false extra_cflags=["/MD","--target=x86_64-pc-windows-msvc"] extra_asmflags=["--target=x86_64-pc-windows-msvc"]
Done. Made 86 targets from 33 files in 1600ms
ninja: Entering directory `C:\Users\(my user name)\Documents\Visual Studio Code\(my project)\target\debug\build\skia-bindings-24372a3e41696695\out\skia'
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
[0/1] Regenerating ninja files
--- stderr
Checking for "C:\\Program Files\\LLVM\\bin\\clang-cl.exe"
Checking for "C:\\LLVM\\bin\\clang-cl.exe"
ninja: error: manifest 'build.ninja' still dirty after 100 tries
thread 'main' panicked at '`ninja` returned an error, please check the output for details.', C:\Users\(my user name)\.cargo\registry\src\github.com-1ecc6299db9ec823\skia-bindings-0.53.0\build_support\skia\config.rs:485:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
In an attempt to solve this issue, I have tried multiple steps such as:
Reinstalling Visual Studio 2022 with Build Tools multiple times
Manually installing LLVM binaries from LLVM github
Synchronizing system clock
I am not sure what else to try to fix this issue, any suggestions would be welcome. Tyia!
Related
I am currently working on Ubuntu 20.04.1 and would like to install GCC 4.6.2 so I can compile cd-hit-v4.5.7-2011-12-16.
I have a zipped version of GCC from#Download from https://ftp.gnu.org/gnu/gcc/gcc-4.6.2/
I have extracted the file using tar -xzf .tar.gz
I navigate to the extracted file and use the following commands
./contrib/download_prerequisites
./configure
make
The compilation of GCC starts but renders this error:
In file included from ../../.././libgcc/../gcc/tsystem.h:87:0,
from ../../.././libgcc/../gcc/libgcc2.c:29:
/usr/include/stdio.h:27:36: fatal error: bits/libc-header-start.h: No such file or directory
compilation terminated.
make[5]: *** [Makefile:377: _muldi3.o] Error 1
make[5]: Leaving directory '/home/user/Desktop/RETROCLONE/RETROCLONE_BCR_PROCESSING_PIPELILNE/gcc-4.6.2/x86_64-unknown-linux-gnu/32/libgcc'
make[4]: *** [Makefile:1007: multi-do] Error 1
make[4]: Leaving directory '/home/user/Desktop/RETROCLONE/RETROCLONE_BCR_PROCESSING_PIPELILNE/gcc-4.6.2/x86_64-unknown-linux-gnu/libgcc'
make[3]: *** [Makefile:110: all-multi] Error 2
make[3]: Leaving directory '/home/user/Desktop/RETROCLONE/RETROCLONE_BCR_PROCESSING_PIPELILNE/gcc-4.6.2/x86_64-unknown-linux-gnu/libgcc'
make[2]: *** [Makefile:18509: all-stage1-target-libgcc] Error 2
make[2]: Leaving directory '/home/user/Desktop/RETROCLONE/RETROCLONE_BCR_PROCESSING_PIPELILNE/gcc-4.6.2'
make[1]: *** [Makefile:23788: stage1-bubble] Error 2
make[1]: Leaving directory '/home/user/Desktop/RETROCLONE/RETROCLONE_BCR_PROCESSING_PIPELILNE/gcc-4.6.2'
make: *** [Makefile:899: all] Error 2
I then tried to change that by:
sed -i 's#\./fixinc\.sh#-c true#' gcc/Makefile.in
cd /Desktop/RETROCLONE/RETROCLONE_BCR_PROCESSING_PIPELILNE/gcc-4.6.2
sed -i 's#\./fixinc\.sh#-c true#' gcc/Makefile.in
cd ../gcc-build/
../gcc-4.6.2/configure --prefix=/usr \
> --libexecdir=/usr/lib --enable-shared \
> --enable-threads=posix --enable-__cxa_atexit \
> --enable-clocale=gnu --enable-languages=c,c++ \
> --disable-multilib --disable-bootstrap --with-system-zlib
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking for gawk... no
checking for mawk... mawk
configure: error: building out of tree but ../gcc-4.6.2 contains host-x86_64-unknown-linux-gnu.
Use a pristine source tree when building in a separate tree
I have a project with different sub-modules. Each sub-module has a CMakeLists.txt and I have a general CMakeLists.txt at the root of the project.
When I run cmake --build [...] or make [...], it recursively builds sub-modules as expected but it prints verbose like this:
make[2]: Entering directory '/some/path/'
make[2]: Entering directory '/some/path/'
make[2]: Leaving directory '/some/path/'
make[2]: Leaving directory '/some/path/'
...
What I have tried
Explicitly turn off cmake/make verbose by adding set(CMAKE_VERBOSE_MAKEFILE OFF) in the general CMakeLists.txt.
make [...] --no-print-directory
cmake [...] -- [...] --no-print-directory
The --no-print-directory flag removes these messages as intended, but I used to not have to specify this flag in previous projects. I would prefer to avoid using this flag to get the same results as before.
Versions
GNU Make 4.3
cmake version 3.16.4
You can use
MAKEFLAGS += --no-print-directory
Described in the GNU make manual
I try to cross-compiler icu4c 51.1 with Emscripten (clang) via
emconfigure source/configure --host=i386-pc-linux-gnu --prefix=${myprefix} --enable-static --disable-shared --disable-dyload --disable-renaming CXXFLAGS='-DU_USING_ICU_NAMESPACE=0' CPPFLAGS='-DU_DISABLE_RENAMING=1'
emmake make
emmake make install
It compiles most of the sources fine, but fails with
Unpacking ../source/data/in/icudt51l.dat and generating out/tmp/icudata.lst (list of data files)
LD_LIBRARY_PATH=../lib:../stubdata:../tools/ctestfw:$LD_LIBRARY_PATH ../bin/icupkg -d ./out/build/icudt51l --list -x \* ../source/data/in/icudt51l.dat -o out/tmp/icudata.lst
run-detectors: warning: unable to exec /usr/bin/lli-2.8: No such file or directory
run-detectors: warning: unable to exec /usr/bin/lli-2.9: No such file or directory
LLVM ERROR: Program used external function 'findBasename' which could not be resolved!
make[1]: *** [out/tmp/icudata.lst] Error 1
make[1]: Leaving directory `/home/andreas/.emscripten-libs/sources/icu4c/51.1/data'
make: *** [all-recursive] Error 2
So I am wondering, where it tries to find findBasename and what this data compiling is all about.
EDIT:
The error messages come from icupkg being built with clang, which does not make sense in this case. How can I specifc that the libraries are built with clang, but the tools with another compiler?
Sounds like it wasn't able to find, I'm guessing, ICU tool utilities lib in ../lib - might try running ldd or equivalent on icupkg
I just look at documentation - scons simple example and it does not work for me.
First file: main.cpp
#include <iostream>
int main()
{
std::cout << "Hello World" << std::endl;
return 0;
}
Second file: SCons SConstruct
Program('main.cpp')
Result:
scons: Reading SConscript files ...
scons: done reading SConscript
files. scons: Building targets ...
cl /Fomain.obj /c main.cpp /TP /nologo
"cl" is not an internal or external command, operable program or batch file.
scons: *** [main.obj] Error 1 scons:
building terminated because of errors.
I tried this on Window 7 with Visual Studio Express 2012, scons 2.3
Any help?
If I create environment myself all works.
env = Environment(ENV = {'PATH' : os.environ['PATH'], \
'INCLUDE' : 'c:\\Program Files (x86)\\Microsoft Visual Studio 11.0\\VC\\include\\;c:\\Program Files (x86)\\Windows Kits\\8.0\\Include\um\\;c:\\Program Files (x86)\\Windows Kits\\8.0\\Include\\shared\\', \
'LIB' : 'c:\\Program Files (x86)\\Microsoft Visual Studio 11.0\\VC\\lib\\;c:\\Program Files (x86)\\Windows Kits\\8.0\\Lib\\win8\\um\\x86\\'})
Also if build from cmd.exe, before call scons call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\vcvars32", and if building with scons from visual studio NMAKE do it for you.
I tried to compile xcbproto 1.7 in linux and get an error message when type make install command
Making install in xcbgen
make[1]: Entering directory `/home/reham/miriad_files/xcb-proto-1.7/xcbgen'
make[2]: Entering directory `/home/reham/miriad_files/xcb-proto-1.7/xcbgen'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/lib/python2.5/site-packages/xcbgen" || /bin/mkdir -p "/usr/local/lib/python2.5/site-packages/xcbgen"
/usr/bin/install -c -m 644 __init__.py error.py expr.py matcher.py state.py xtypes.py '/usr/local/lib/python2.5/site-packages/xcbgen'
/home/reham/Desktop/Fermi/ScienceTools-v9r15p2-fssc-20090808-i686-pc-linux-gnu-libc2.5/i686-pc-linux-gnu-libc2.5/bin/python: error while loading shared libraries: libpython2.5.so.1.0: cannot open shared object file: No such file or directory
make[2]: *** [install-pkgpythonPYTHON] Error 127
make[2]: Leaving directory `/home/reham/miriad_files/xcb-proto-1.7/xcbgen'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/reham/miriad_files/xcb-proto-1.7/xcbgen'
make: *** [install-recursive] Error 1
What is the problem?
It seems there's a problem with a custom python version you seem to have installed on your system. Namely this one:
/home/reham/Desktop/Fermi/ScienceTools-v9r15p2-fssc-20090808-i686-pc-linux-gnu-libc2.5/i686-pc-linux-gnu-libc2.5/bin/python
This seems to depend on the shared library libpython2.5.so.1.0 which isn't found by the linker.
Most probably the custom python version you installed brought this shared library along and it just isn't found as it is not in one of the standard directories.
To fix this you might either try to use the python version installed on your system or add the path containing libpython2.5.so.1.0 to the ones searched by the linker.
My guess is it will be somewhere below /home/reham/Desktop/Fermi/ScienceTools-v9r15p2-fssc-20090808-i686-pc-linux-gnu-libc2.5/i686-pc-linux-gnu-libc2.5/
Most probably in the subdirectory /lib .