Can't build crc32c - build

It's a C implementation.
Firstly, while building, it exits with error: "warning: linux/if_alg.h: No such file or directory". Then I run yum install kernel-devel-{version}, but it doesn't work.
Secondly when I copy the file from another PC, the error becomes "error: ‘AF_ALG’ undeclared (first use in this function)".
I have no idea to solve this issue. Please help me.
And here is my PC's info:
CPU:Intel(R) Xeon(R) CPU E5335 # 2.00GHz
OS: CentOS 6.5
Kernel-release: 2.6.32-431.5.1.el6.x86_64

Related

How to fix a `xeus-cling` kernel runtime error on Mac OS (C++ Jupyter kernel stdlib errors)

I installed xeus-cling with the usual conda install xeus-cling and get the following runtime errors when I go to start a C++ kernel (11, 14 and 17 versions) in the Jupyter notebook:
/opt/anaconda3/envs/cling/include/c++/v1/stdlib.h:143:12: error: no member named 'ldiv' in the global namespace
return ::ldiv(__x, __y);
< many such errors, eventually >
/opt/anaconda3/envs/cling/include/c++/v1/cstdlib:122:9: error: no member named 'rand' in the global namespace
using ::rand;
~~^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
I tried re-installing XCode command line tools - no go. Same setup works fine on my Linux machine.
How can I fix these errors and get the kernel to start?
I filed an issue here with the recent XCode version 12.5.1 (12E507) - it looks like either xeus-cling conda package is using an incompatible toolchain, or XCode is misconfigured - either way, the C++ kernel won't start. Conda 4.10.1 with Python 3.9.6 (in case this matters). Thanks in advance!

ERROR: Failed to build PhantomJS! Building Qt Base failed

I have Debian Linux(64-bit) in VirtualBox.
Ram: 8Gb (for Debian 4Gb)
CPU: i5-3470
If any other details are needed please tell me.
I have followed instructions written here, and here you can see the console log.
For some reason I am unable to to build phantomjs and I can't understand why its not working... Have searched a lot, but couldn't find any thread which would be about this error.
--- EDIT ---
When I executed this command:
./configure --with-openssl-includes=/usr/include/openssl-1.0/ --with-openssl-libraries=/usr/lib/openssl-1.0/
Output was this:
--with-openssl-includes=/usr/include/openssl-1.0/: invalid command-line switch
--with-openssl-libraries=/usr/lib/openssl-1.0/: invalid command-line switch
The output of the console has changed but I still get errors: https://pastebin.com/wbgi8syg
Looks like you are on stretch (or later) and that you are already aware of the libssl vs libssl1.0 case.
Therefore, if you don't have libssl-dev installed, this line will get you further:
python build.py --qt-config "-I /usr/include/openssl-1.0/ -L /usr/lib/openssl-1.0/"
If you already have it installed and my suggestion doesn't work, you can uninstall libssl-dev for the time to build phantomjs which will likely avoid having to play further with configuration related variables.

autotools syntax error with ax_check_compile_flag

I am using autotools for building my C++ application. In my configure.ac I have the following line:
AX_CHECK_COMPILE_FLAG([-Wall], [CPPFLAGS="$CPPFLAGS -Wall"])
which causes the following error when executing ./configure (after running autoreconf -i):
./configure: line 3825: syntax error near unexpected token `-Wall,'
./configure: line 3825: `AX_CHECK_COMPILE_FLAG(-Wall, CPPFLAGS="$CPPFLAGS -Wall")'
My system: Linux web 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux
On my Ubuntu machine it works well, why do I get this error?
autoreconf isn't magic (though I encounter package maintainers who obviously believe this). When you ran autoreconf, it failed to find the AX_CHECK_COMPILE_FLAG macro, and produced a corrupt configure script. Usually that produces an error/diagnostic message at the same time.
'AX_CHECK_COMPILE_FLAG` comes from the autoconf archive project, and Debian has a package which provides this, named autoconf-archive. Likely, you forgot to install it:
sudo apt-get install autoconf-archive

Problems while trying to build LLVM and Clang

I tried to build LLVM and Clang but am getting this error :
cp: cp: cp: cannot stat /home/saurabh/Build/clang-build/build/tools/clang/runtime/compiler-rt/clang_linux/asan-i386/libcompiler_rt.a'cannot stat/home/saurabh/Build/clang-build/build/tools/clang/runtime/compiler-rt/clang_linux/ubsan-x86_64/libcompiler_rt.a'cannot stat `/home/saurabh/Build/clang-build/build/tools/clang/runtime/compiler-rt/clang_linux/ubsan-i386/libcompiler_rt.a': No such file or directory
: No such file or directory: No such file or directory
I went through Cannot build LLVM and Clang but it doesn't seem to have any reasons why he had gotten a similar error (hence I am asking it again). I have tried to remove the -Werror flags in compiler-rt/make/ relevant files, since before that, it was stopping on this error :
/home/saurabh/Build/clang-build/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_mutex.cc:53:13: error:
comparison of constant 4294967295 with expression of type 'int' is always
false [-Werror,-Wtautological-constant-out-of-range-compare]
if (z == MutexTypeLeaf) {
~ ^ ~~~~~~~~~~~~~
1 error generated.
I had asked on #llvm and had been suggested that. Any ideas what could be causing this ?
Fwiw, I am on Ubuntu 12.10 64-bit.
You have to follow http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary. Be aware of the software dependencies you have to install. Also, check again if your --prefix=directory is set. If you cannot install Clang over LLVM (after you succeded to install LLVM), you can try install it using apt-get install clang and clang++. Therefore, you can compile your LLVM passes using this clang. For other corresponding packages, like VMkit for Java, you have to install ant and oracle jdk.
My LD_LIBRARY_PATH environment variable wasn't set properly. After I corrected it, this problem went away.

Mac/Django error message: "/mercurial/osutil.so: no appropriate 64-bit architecture"

I'm new to Macs (and quite new to Django) and I'm setting up an existing Django/MySQL site that uses Mercurial as a site package, on a new Macbook Pro.
All was going well during installation - no error messages. I installed the default versions of most packages from macports.
However when I try runserver, localhost shows the following error message:
ImportError at /
.../lib/python2.6/site-packages/mercurial/osutil.so: no appropriate 64-bit architecture (see "man python" for running in 32-bit mode)
Please could anyone advise? I've tried typing the following at the terminal:
defaults write com.apple.versioner.python Prefer-32-Bit -bool yes
but it didn't help.
I've gotten a similar error and a combination of two things helped me install Mercurial for OS X Lion. I'm running OS X 10.7.3.
First, there is a bug on line 455 of the setup.py script (at least for Mercurial 2.2.1, the version I tried). The line
version = runcmd(['/usr/bin/xcodebuild', '-version'], {})[0].splitlines()
should be replaced with
version = runcmd(['/usr/bin/xcodebuild', '-version'], {})[0]
Second, after I installed Mercurial (either by easy_install, Mac OS X binary installer, and compilation), I kept getting the following error message:
ImportError: dlopen(/Library/Python/2.7/site-packages/mercurial/osutil.so, 2): no suitable image found. Did find: /Library/Python/2.7/site-packages/mercurial/osutil.so: mach-o, but wrong architecture
However, after seeing this post, I noticed that
defaults read com.apple.versioner.python Prefer-32-Bit
outputs 1 on my system. However, running this command
defaults write com.apple.versioner.python Prefer-32-Bit -bool no
and then recompiling / installing mercurial resulted in a working executable for me at the end.
If everything from my comment checks out, try setting that Prefer-32-bit in an user environment variable instead of at the command line.
Edit this file: ~/.MacOSX/environment.plist
See:
http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html#//apple_ref/doc/uid/20002093-113982