Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
0
votes
2
answers
2325
views
Could not find libmount
During compilation of customized distribution (using buildroot v. 11.2018) I have problem with libmount library (the problem appeared after I had included efl package in buildroot menuconfig - *Target packages -> Graphic lib... -> efl* ). I have additionaly installed package libmount-dev with no res...
During compilation of customized distribution (using buildroot v. 11.2018)
I have problem with libmount library (the problem appeared after I had included efl package in buildroot menuconfig - *Target packages -> Graphic lib... -> efl* ).
I have additionaly installed package libmount-dev with no results.
checking for getxattr in -lc... yes
checking sys/xattr.h usability... yes
checking sys/xattr.h presence... yes
checking for sys/xattr.h... yes
checking for XATTR_NOFOLLOW... no
checking for LIBMOUNT... no
configure: error: *** Could not find libmount
How to include this library to obtain succesful compilation?
Fasset
(11 rep)
Nov 20, 2018, 07:04 PM
• Last activity: Jul 30, 2025, 11:01 PM
3
votes
1
answers
2902
views
How do you specify the pkg-config path when compiling something with cmake?
I want to build ffmpeg with support for the av1 codec on CentOS 7. I start by following the instructions [here][1]: git clone https://aomedia.googlesource.com/aom mkdir aom_build cd aom_build cmake ../aom make sudo make install This writes a file to `/usr/local/lib64/pkgconfig/aom.pc`. When I later...
I want to build ffmpeg with support for the av1 codec on CentOS 7.
I start by following the instructions here :
git clone https://aomedia.googlesource.com/aom
mkdir aom_build
cd aom_build
cmake ../aom
make
sudo make install
This writes a file to
/usr/local/lib64/pkgconfig/aom.pc
.
When I later clone ffmpeg's git repo and try to run ./configure --enable-libaom ...
, it complains that pkg-config can't find the aom.pc file.
This is because if I run pkg-config --variable pc_path pkg-config
, I can see that pkg-config only checks here:
/usr/lib64/pkgconfig:/usr/share/pkgconfig
It doesn't look in /usr/local/lib64/pkgconfig
, where aom.pc is.
So far, the only fix I've come up with is to run this instead in ffmpeg's git directory:
PKG_CONFIG_PATH=$PKG_CONFIG_PATH/usr/local/lib64/pkgconfig: ./configure --enable-libaom ...
This works, but I'd rather just tell libaom to write aom.pc to /usr/lib64/pkgconfig in the first place.
Is there any way, when building aom, to tell cmake or make to write the aom.pc file to /usr/lib64/pkgconfig instead of /usr/local/lib64/pkgconfig?
In other projects that have a ./configure
step, I've seen it possible to specify this with ./configure --pkgconfigdir=/usr/lib64/pkgconfig
, but the aom project doesn't have a ./configure
script, so I'm not sure what to do here.
Tal
(2252 rep)
Apr 24, 2019, 02:52 PM
• Last activity: Jul 28, 2025, 12:07 AM
1
votes
1
answers
1922
views
Qubes OS - Update a Template Kernel
I'm trying to update the kernel in the Debian Template of `Qubes OS`, following the official documentations, but it seems I'm missing something or doing something wrong. I'm using `gcc 6.3.0`. **Qubes Docs:** Installing kernel in Debian VM In Debian based VM, you need to install qubes-kernel-vm-supp...
I'm trying to update the kernel in the Debian Template of
**Qubes Docs:**
Installing kernel in Debian VM In Debian based VM, you need to install qubes-kernel-vm-support package. This package include required additional kernel module and initramfs addition required to start Qubes VM (for details see template implementation). Additionally you need some GRUB tools to create it’s configuration. Note: you don’t need actual grub bootloader as it is provided by dom0. But having one also shouldn’t harm. sudo apt-get update sudo apt-get install qubes-kernel-vm-support grub2-common Then install whatever kernel you want. If you are using distribution kernel package (linux-image-amd64 package), initramfs and kernel module should be handled automatically. If not, or you are building kernel manually, do this on using dkms and initramfs-tools: sudo dkms autoinstall -k # replace this with actual kernel version sudo update-initramfs -u When kernel is installed, you need to create GRUB configuration. You may want to adjust some settings in /etc/default/grub, for example lower GRUB_TIMEOUT to speed up VM startup. Then you need to generate actual configuration: In Fedora it can be done using update-grub2 tool: sudo mkdir /boot/grub sudo update-grub2 Then shutdown the VM. From now you can set pvgrub2 as VM kernel and it will start kernel configured within VM.
**Debian Docs:**
Don't be afraid to try compiling the kernel. It's fun and profitable. To compile a kernel the Debian way, you need some packages: fakeroot, kernel-package, linux-source-version. Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using tar xf /usr/src/linux-source-version.tar.xz and change to the directory linux-source-version that will have been created. Now, you can configure your kernel. Run make xconfig if X11 is installed, configured and being run; run make menuconfig otherwise (you'll need libncurses5-dev installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select “Kernel module loader” in “Loadable module support” (it is not selected by default). If not included, your Debian installation will experience problems. Clean the source tree and reset the kernel-package parameters: make-kpkg clean Now, compile the kernel: fakeroot make-kpkg --initrd Once the compilation is complete, you can install your custom kernel like any package. As root, do dpkg -i ../linux-image-version-subarchitecture.deb. For instance, the System.map will be properly installed and /boot/config-3.16 will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well.
**The Debian Way Output:** ... ... ... This is kernel package version 13.014+nmu1. install -p -d -o root -g root -m 755 /usr/src/linux-source-4.8/debian/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64/DEBIAN sed -e 's/=V/4.8.15-rt10-11.pvops.qubes.x86_64/g' -e 's/=IB//g' \ -e 's/=ST/linux/g' -e 's/=R//g' \ -e 's/=KPV/13.014+nmu1/g' \ -e 's/=K/vmlinuz/g' \ -e 's/=I/YES/g' -e 's,=D,/boot,g' \ -e 's@=A@amd64@g' \ -e 's@=B@x86_64@g' \ ... dpkg-gencontrol: error: illegal package name 'linux-image-4.8.15-rt10-11.pvops.qubes.x86_64': character '_' not allowed debian/ruleset/targets/image.mk:230: recipe for target 'debian/stamp/binary/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64' failed make: *** [debian/stamp/binary/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64] Error 255
**Manual compiling:**
I've downloaded
I think this can be solved easily, but if I can compile the kernel manually, then how should I procede?
**UPDATE:** Installing directly the Debian package
I noticed the
Qubes OS
, following the official documentations, but it seems I'm missing something or doing something wrong.
I'm using gcc 6.3.0
.
**Qubes Docs:**
Installing kernel in Debian VM In Debian based VM, you need to install qubes-kernel-vm-support package. This package include required additional kernel module and initramfs addition required to start Qubes VM (for details see template implementation). Additionally you need some GRUB tools to create it’s configuration. Note: you don’t need actual grub bootloader as it is provided by dom0. But having one also shouldn’t harm. sudo apt-get update sudo apt-get install qubes-kernel-vm-support grub2-common Then install whatever kernel you want. If you are using distribution kernel package (linux-image-amd64 package), initramfs and kernel module should be handled automatically. If not, or you are building kernel manually, do this on using dkms and initramfs-tools: sudo dkms autoinstall -k # replace this with actual kernel version sudo update-initramfs -u When kernel is installed, you need to create GRUB configuration. You may want to adjust some settings in /etc/default/grub, for example lower GRUB_TIMEOUT to speed up VM startup. Then you need to generate actual configuration: In Fedora it can be done using update-grub2 tool: sudo mkdir /boot/grub sudo update-grub2 Then shutdown the VM. From now you can set pvgrub2 as VM kernel and it will start kernel configured within VM.
**Debian Docs:**
Don't be afraid to try compiling the kernel. It's fun and profitable. To compile a kernel the Debian way, you need some packages: fakeroot, kernel-package, linux-source-version. Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using tar xf /usr/src/linux-source-version.tar.xz and change to the directory linux-source-version that will have been created. Now, you can configure your kernel. Run make xconfig if X11 is installed, configured and being run; run make menuconfig otherwise (you'll need libncurses5-dev installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select “Kernel module loader” in “Loadable module support” (it is not selected by default). If not included, your Debian installation will experience problems. Clean the source tree and reset the kernel-package parameters: make-kpkg clean Now, compile the kernel: fakeroot make-kpkg --initrd Once the compilation is complete, you can install your custom kernel like any package. As root, do dpkg -i ../linux-image-version-subarchitecture.deb. For instance, the System.map will be properly installed and /boot/config-3.16 will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well.
**The Debian Way Output:** ... ... ... This is kernel package version 13.014+nmu1. install -p -d -o root -g root -m 755 /usr/src/linux-source-4.8/debian/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64/DEBIAN sed -e 's/=V/4.8.15-rt10-11.pvops.qubes.x86_64/g' -e 's/=IB//g' \ -e 's/=ST/linux/g' -e 's/=R//g' \ -e 's/=KPV/13.014+nmu1/g' \ -e 's/=K/vmlinuz/g' \ -e 's/=I/YES/g' -e 's,=D,/boot,g' \ -e 's@=A@amd64@g' \ -e 's@=B@x86_64@g' \ ... dpkg-gencontrol: error: illegal package name 'linux-image-4.8.15-rt10-11.pvops.qubes.x86_64': character '_' not allowed debian/ruleset/targets/image.mk:230: recipe for target 'debian/stamp/binary/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64' failed make: *** [debian/stamp/binary/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64] Error 255
**Manual compiling:**
I've downloaded
linux-source-4.8
from Debian and I've extracted it in /usr/src
.
Then:
make defconf
make menuconf # custom settings
make
Same error as above:
dpkg-gencontrol: error: illegal package name 'linux-image-4.8.15-rt10-11.pvops.qubes.x86_64':
character '_' not allowed
I think this can be solved easily, but if I can compile the kernel manually, then how should I procede?
make install
and make modules_install
are required or I have to use dkms autoinstall
directly? This isn't specified...
**UPDATE:** Installing directly the Debian package
linux-image-amd64
make the console disappeared and the VM work unproperly, I tried to reboot it, but I could use it only by attaching to the serial console.
I noticed the
dpkg
crashed during installation, so I ran dpkg --configure -a
and it finished the installation, but it showed a warning message that told with that initramfs
, the machine would have never booted, in fact I updated GRUB
and rebooted, but initramfs
couldn't mount root.
JumpAlways
(123 rep)
Jan 31, 2017, 05:43 AM
• Last activity: Jul 27, 2025, 02:07 PM
2
votes
1
answers
3122
views
Upgrading Berkeley DB rpm in a Centos OS
I have a software which needs Berkeley DB 4.5 or above. But in my CentOS 5.11 x86_64 Server I have: * Package db4-4.3.29-10.el5_5.2.x86_64 already installed and latest version * Package db4-4.3.29-10.el5_5.2.i386 already installed and latest version How can I upgrade these rpm to a newer version? I...
I have a software which needs Berkeley DB 4.5 or above.
But in my CentOS 5.11 x86_64 Server I have:
* Package db4-4.3.29-10.el5_5.2.x86_64 already installed and latest version
* Package db4-4.3.29-10.el5_5.2.i386 already installed and latest version
How can I upgrade these rpm to a newer version?
I tried to upgrade using Centos 6.6 rpm in this way:
rpm -Uvh ftp://195.220.108.108/linux/centos/6.6/os/x86_64/Packages/db4-4.7.25-18.el6_4.i686.rpm
but I receive this error:
Retrieving ftp://195.220.108.108/linux/centos/6.6/os/x86_64/Packages/db4-4.7.25-18.el6_4.i686.rpm
warning: /var/tmp/rpm-xfer.IKWqHE: Header V3 RSA/SHA1 signature: NOKEY, key ID c105b9de
error: Failed dependencies:
rpmlib(FileDigests) = 4.4.0 conflicts with pam-0.99.6.2-12.el5.i386
db4 >= 4.4.0 conflicts with pam-0.99.6.2-12.el5.x86_64
libdb-4.3.so is needed by (installed) subversion-1.6.11-12.el5_10.i386
libdb-4.3.so is needed by (installed) pam_ccreds-3-5.i386
libdb-4.3.so is needed by (installed) apr-util-1.2.7-11.el5_5.2.i386
libdb-4.3.so is needed by (installed) db4-devel-4.3.29-10.el5_5.2.i386
libdb_cxx-4.3.so is needed by (installed) db4-devel-4.3.29-10.el5_5.2.i386
I also tried to compile from source
db-4.5.20.tar.gz
. I compiled it with no problem, however my software is still seeing the Berkley DB preinstalled in rpm package db4-4.3.29.
Any help please ?
gr68
(334 rep)
Jan 28, 2015, 04:01 PM
• Last activity: Jul 24, 2025, 04:00 PM
7
votes
2
answers
9597
views
How to compile a third party driver into the kernel?
I am using Linux Mint 17.2 on Toshiba c640. As my LAN driver is no more functional, I am using a USB to LAN converter which was provided with some driver installation files. Every time i want to use the device I have to install the drivers manually by running the given commands. So I am requesting u...
I am using Linux Mint 17.2 on Toshiba c640. As my LAN driver is no more functional, I am using a USB to LAN converter which was provided with some driver installation files. Every time i want to use the device I have to install the drivers manually by running the given commands. So I am requesting u guys if u could help me to make it automatically load them after every rebooting. For that purpose manufacturer have given some instructions but since I am not a pro techie I couldn't do it myself. I am providing the details of files. Any help is appreciated. Thank you
These are the files:
Contents are

Readme.txt
:
Note:
1. Please run as root
2. Supported linux kernel range from 2.6.x to 3.8.x
3. CH9x00 module depends on mii and usbnet modules
4. If you want complied this module in kernel, refer to followed
a. # cp ch9x00.c ~/2.6.25/driver/net/usb/
b. # cd ~/2.6.25/driver/net/usb/
c. modified Makefile and Kconfig for ch9x00.c
Install:
# make
# make load
Uninstall:
# make unload
Makefile
:
# This makefile for CH9X00 network adaptor
# Makefile for linux 2.6.x - 3.8.x
ifneq ($(KERNELRELEASE), )
#call from kernel build system
obj-m := ch9x00.o
else
KERNELDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
modules:
$(MAKE) -C $(KERNELDIR) M=$(PWD)
load:
modprobe mii
modprobe usbnet
insmod ch9x00.ko
unload:
rmmod ch9x00
clean:
rm -rf *.o *~ core .depend .*.cmd *.mod.c .tmp_versions modules.* Module*
endif
Maddyrdm
(71 rep)
Aug 11, 2015, 08:16 AM
• Last activity: Jul 19, 2025, 03:06 AM
1
votes
1
answers
39
views
dpkg-shlibdeps: missing symbols in libasteriskpj.so.2 [asterisk]
I’m trying to build Asterisk packages for Ubuntu 22.04 LTS, and I’m encountering the same issue with both version 22.4.x and 22.5.0. During the build process, I get the following warnings: dpkg-shlibdeps: warning: symbol __ast_free used by debian/asterisk/usr/lib/x86_64-linux-gnu/libasteriskpj.so.2...
I’m trying to build Asterisk packages for Ubuntu 22.04 LTS, and I’m encountering the same issue with both version 22.4.x and 22.5.0. During the build process, I get the following warnings:
dpkg-shlibdeps: warning: symbol __ast_free used by debian/asterisk/usr/lib/x86_64-linux-gnu/libasteriskpj.so.2 found in none of the libraries
dpkg-shlibdeps: warning: symbol ast_pjproject_max_log_level used by debian/asterisk/usr/lib/x86_64-linux-gnu/libasteriskpj.so.2 found in none of the libraries
dpkg-shlibdeps: warning: symbol __ast_repl_malloc used by debian/asterisk/usr/lib/x86_64-linux-gnu/libasteriskpj.so.2 found in none of the libraries
dpkg-shlibdeps: warning: symbol ast_option_pjproject_log_level used by debian/asterisk/usr/lib/x86_64-linux-gnu/libasteriskpj.so.2 found in none of the libraries
The .deb package builds successfully, but I'm not sure if the library will function correctly. I did find these symbols in the Asterisk binary.
For simplicity, I’m building a single “all-in-one” package, as this makes local deployment easier for me.
Qmails
(13 rep)
Jul 18, 2025, 11:54 AM
• Last activity: Jul 18, 2025, 12:16 PM
3
votes
1
answers
5075
views
Apache + mod_ssl build not linking to my OpenSSL build
I have spent some time searching online but none of what I found seems to help. I'm running CentOS 6 64bit and would like to compile Apache with mod_ssl and need to link it to my own OpenSSL build (which is newer than the OS provided version). OpenSSL 1.1.0i is configured with: ./config --prefix=/op...
I have spent some time searching online but none of what I found seems to help.
I'm running CentOS 6 64bit and would like to compile Apache with mod_ssl and need to link it to my own OpenSSL build (which is newer than the OS provided version).
OpenSSL 1.1.0i is configured with:
./config --prefix=/opt/openssl-1.1.0 --openssldir=/opt/openssl-1.1.0 shared
Apache 2.4 is configured with:
./configure --enable-layout=mycustomlayout \
--prefix=/opt/httpd-2.4.34 \
--exec-prefix=/opt/httpd-2.4.34 \
--with-mpm=prefork \
--enable-so \
--enable-ssl \
--with-ssl=/opt/openssl-1.1.0 \
--enable-cgi \
--enable-http2 \
--enable-proxy-http2 \
--with-included-apr
It appears to compile just fine but mod_ssl isn't aware of where OpenSSL 1.1.0 is installed:
[root@host .libs]# ldd ./mod_ssl.so | grep -iP 'ssl|crypto'
libssl.so.1.1 => not found
libcrypto.so.1.1 => not found
And so only works when you explicitly tell it where to look:
[root@host .libs]# export LD_LIBRARY_PATH=/opt/openssl-1.1.0/lib:$LD_LIBRARY_PATH
[root@host .libs]# ldd ./mod_ssl.so | grep -iP 'ssl|crypto'
libssl.so.1.1 => /opt/openssl-1.1.0/lib/libssl.so.1.1 (0x00007f069149a000)
libcrypto.so.1.1 => /opt/openssl-1.1.0/lib/libcrypto.so.1.1 (0x00007f069100a000)
Even building mod_ssl statically into httpd binary with
--enable-mods-static=ssl
doesn't help.
I tried --enable-ssl
, --enable-ssl --enable-ssl-staticlib-deps
, and --enable-ssl --enable-ssl-staticlib-deps --enable-mods-static=ssl
and still the same result:
libssl.so.1.1 => not found
libcrypto.so.1.1 => not found
Also tried, without luck, setting these variables before ./configure
:
export PKG_CONFIG_PATH=/opt/openssl-1.1.0/lib/pkgconfig:$PKG_CONFIG_PATH \
LD_LIBRARY_PATH=/opt/openssl-1.1.0/lib:$LD_LIBRARY_PATH \
LDFLAGS="-L/opt/openssl-1.1.0/lib"
I know I can just add to /etc/ld.so.conf.d
to autoload the new OpenSSL library or adjust Apache's init script to add to LD_LIBRARY_PATH
but I'd much prefer to have it working properly, have the program where to look for libssl.so
/ libcrypto.so
, just like my PHP build:
[root@host php]# export PKG_CONFIG_PATH=/opt/openssl-1.1.0/lib/pkgconfig:$PKG_CONFIG_PATH \
LD_LIBRARY_PATH=/opt/openssl-1.1.0/lib:$LD_LIBRARY_PATH \
LDFLAGS="-L/opt/openssl-1.1.0/lib" \
PHP_PREFIX=/opt/php-7.2.9 \
EXTENSION_DIR=$PHP_PREFIX/usr/lib64/php/modules
[root@host php]# ./configure […] \
--with-imap=shared \
--with-imap-ssl \
--with-openssl=shared \
--with-openssl-dir=/opt/openssl-1.1.0/bin
[root@host php]# make
[root@host php]# unset PKG_CONFIG_PATH LD_LIBRARY_PATH LDFLAGS
[root@host modules]# ldd ./openssl.so | grep -iP 'ssl|crypto'
libssl.so.1.1 => /opt/openssl-1.1.0/lib/libssl.so.1.1 (0x00007fc2220a6000)
libcrypto.so.1.1 => /opt/openssl-1.1.0/lib/libcrypto.so.1.1 (0x00007fc221c17000)
What am I doing wrong? Could this be a bug?
E-71
(53 rep)
Aug 29, 2018, 03:30 AM
• Last activity: Jul 15, 2025, 12:05 PM
0
votes
1
answers
2202
views
Error: #error This file requires compiler and library support for the ISO C++ 2011 standard
I am running a c++ code with TAU (analyzing and profiling tool) on Ubuntu 20.04 LTS using some cluster. The command I am running looks like this: ``` tau_cxx.sh -I$FFTW3_INC wrappingScript.cpp spectralFunctions.cpp arithmeticFunctions.cpp -optLinking="-lfftw3 -lm -g" -o ../../Datasim/TauTest.out ```...
I am running a c++ code with TAU (analyzing and profiling tool) on Ubuntu 20.04 LTS using some cluster. The command I am running looks like this:
tau_cxx.sh -I$FFTW3_INC wrappingScript.cpp spectralFunctions.cpp arithmeticFunctions.cpp -optLinking="-lfftw3 -lm -g" -o ../../Datasim/TauTest.out
This however is giving me the following error:
Executing> /opt/apps/gcc/5.2.0/bin/g++ -I/opt/apps/gcc5_2/mvapich22_2/fftw/3.3.8/include wrappingScript.cpp spectralFunctions.cpp arithmeticFunctions.cpp -o ../../Datasim/TauTest.out
In file included from /arcapps/cascades-broadwell-slurm/opt/apps/gcc/5.2.0/include/c++/5.2.0/cstdint:35:0,
from arithmeticFunctions.cpp:8:
/arcapps/cascades-broadwell-slurm/opt/apps/gcc/5.2.0/include/c++/5.2.0/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
#error This file requires compiler and library support for the \
^
make: *** [all] Error 1
So I tried compiling with `-std=c++11
` like this:
tau_cxx.sh -I$FFTW3_INC -std=c++11 wrappingScript.cpp spectralFunctions.cpp arithmeticFunctions.cpp -optLinking="-lfftw3 -lm -g" -o ../../Datasim/TauTest.out
This somehow messes up my `-I$FFTW3_INC
` and I get errors like:
undefined reference to `fftw_malloc'
I tried also linking it in my TAU options like:
tau_cxx.sh -I$FFTW3_INC wrappingScript.cpp spectralFunctions.cpp arithmeticFunctions.cpp -optLinking="-lfftw3 -lm -std=c++11 -g" -o ../../Datasim/TauTest.out
This had no effect and gave me the original error. Can someone help please I am confused.
Jamie
(111 rep)
May 27, 2021, 10:00 PM
• Last activity: Jul 12, 2025, 01:00 AM
-3
votes
0
answers
41
views
Fedora - can't make - "lib/modules/6.14.5-100.fc40.x86_64/build: No such file or directory. Stop."
I'm running Fedora and trying to use make. When I run it, I get the error: ``` make -C /lib/modules/6.14.5-100.fc40.x86_64/build M=/home/[my_name]/[folder_of_thing] make[1]: Entering directory '/home/[my_name]/[folder_of_thing]' make[1]: *** /lib/modules/6.14.5-100.fc40.x86_64/build: No such file or...
I'm running Fedora and trying to use make. When I run it, I get the error:
make -C /lib/modules/6.14.5-100.fc40.x86_64/build M=/home/[my_name]/[folder_of_thing]
make: Entering directory '/home/[my_name]/[folder_of_thing]'
make: *** /lib/modules/6.14.5-100.fc40.x86_64/build: No such file or directory. Stop.
make: Leaving directory '/home/[my_name]/[folder_of_thing]'
make: *** [Makefile:5: default] Error 2
As far as I can tell, that build file exists in the /lib/modules/6.14.5-100.fc40.x86_64/ folder.
Please advise! Thank you so much for your help!
Edit: the issue was a broken symbolic link. The solution was to install the missing files: dnf install kernel-devel-6.14.5-100.fc40.x86_64
Hope this helps anyone with this issue. I saw other similar posts, but the exact command was slightly different for Fedora.
bread
(1 rep)
Jul 10, 2025, 09:43 PM
• Last activity: Jul 11, 2025, 04:05 AM
0
votes
1
answers
3623
views
How fix "No rule to make target 'arch/arm64/boot/dts/kona-rumi.dtb', needed by '__build'. Stop
Previously, I had the same error related to the file: `arch/arm64/boot/dts/qcom/apq8016-sbc.dtb`, but I solved it by deleting the line `subdir-y += qcom` from the `arch/arm64/boot/dts/Makefile`. Now a new same error appears and I have no idea how to fix it. Internet advice didn't help. Error: make[3...
Previously, I had the same error related to the file:
arch/arm64/boot/dts/qcom/apq8016-sbc.dtb
, but I solved it by deleting the line subdir-y += qcom
from the arch/arm64/boot/dts/Makefile
.
Now a new same error appears and I have no idea how to fix it.
Internet advice didn't help.
Error:
make: *** No rule to make target 'arch/arm64/boot/dts/kona-rumi.dtb', needed by '__build'. Stop.
make: *** Waiting for unfinished jobs....
make: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts] Error 2
make[1] : *** [arch/arm64/Makefile:172: dtbs] Error 2
make[1] : *** Waiting for unfinished jobs....
Error with make V=1
:
make -f ../scripts/Makefile.build obj=arch/arm64/boot/dts/ti need-builtin=
(cat /dev/null; ) > arch/arm64/boot/dts/ti/modules.order
make -f ../scripts/Makefile.build obj=arch/arm64/boot/dts/vendor need-builtin=
make -f ../scripts/Makefile.build obj=arch/arm64/boot/dts/vendor/qcom need-builtin=
(cat /dev/null; ) > arch/arm64/boot/dts/vendor/qcom/modules.order
make: *** No rule to make target 'arch/arm64/boot/dts/vendor/qcom/kona-rumi.dtb', needed by '__build'. Stop.
make: *** Waiting for unfinished jobs....
make: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts/vendor/qcom] Error 2
make: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts/vendor] Error 2
make[1] : *** [arch/arm64/Makefile:172: dtbs] Error 2
make[1] : *** Waiting for unfinished jobs....
MyKernel:
kernel
My build code:
export ARCH=arm64
export SUBARCH=arm64
export HEADER_ARCH=arm64
export DTC_EXT=dtc
PATH="/home/hehe/Downloads/clang/bin:/home/hehe/Downloads/aarch64-linux-android-4.9/bin:/home/hehe/Downloads/arm-linux-androideabi-4.9/bin:${PATH}"
rm -rf out
make O=out clean && make mrproper
make O=out ARCH=arm64 kona_defconfig
make -j$(nproc --all) O=out ARCH=arm64 CC=clang CLANG_TRIPLE=aarch64-linux-gnu- CROSS_COMPILE=aarch64-linux-android- CROSS_COMPILE_ARM32=arm-linux-androideabi-
JohnTit
(11 rep)
Feb 16, 2023, 05:22 PM
• Last activity: Jul 8, 2025, 12:08 AM
0
votes
1
answers
60
views
Which GCC version to use for compiling Linux 5.4.1 to bzImage without strlcpy errors?
I’m trying to compile the Linux 5.4.1 kernel to a `bzImage` using an older GCC version I built from source (gcc 8.2.0 and binutils 2.31.1), with: ``` make CC= LD= -j$(nproc) ``` However, I get errors about a redundant declaration of `strlcpy`. Which GCC version should I use to compile this kernel ve...
I’m trying to compile the Linux 5.4.1 kernel to a
bzImage
using an older GCC version I built from source (gcc 8.2.0 and binutils 2.31.1), with:
make CC= LD= -j$(nproc)
However, I get errors about a redundant declaration of strlcpy
. Which GCC version should I use to compile this kernel version without errors, so I can test the system calls I just created? I have specific requirements to work with this kernel.
update: actually i do not know why it counts my system headers as well while compiling and finds another declaration of strlcpy in /usr/include...
/home/alexisl/Kernels/linux-5.4.1-mod/tools/include/linux/string.h:20:15: error: redundant redeclaration of ‘strlcpy’ [-Werror=redundant-decls]
20 | extern size_t strlcpy(char *dest, const char *src, size_t size);
| ^~~~~~~
In file included from /home/alexisl/Kernels/linux-5.4.1-mod/tools/include/linux/string.h:6:
/usr/include/string.h:506:15: note: previous declaration of ‘strlcpy’ with type ‘size_t(char * restrict, const char * restrict, size_t)’ {aka ‘long unsigned int(char * restrict, const char * restrict, long unsigned int)’}
506 | extern size_t strlcpy (char *__restrict __dest,
so that is why the compilation process fails. how do i isolate it and make it not take into account the system's headers?
ALEXIS LAZANAS
(1 rep)
May 23, 2025, 07:43 PM
• Last activity: Jul 6, 2025, 09:59 PM
1
votes
1
answers
1511
views
When configuring Glibc prior to compiling it I recieve an error concerning kernel headers telling me to use "--with-headers"
I am using the latest stable Linux from Scratch book version. In [Step 5.5.1](https://www.linuxfromscratch.org/lfs/view/stable/chapter05/glibc.html), when configuring Glibc I run the provided script, and receive an error telling me to use the --with-headers configure option, however I am already usi...
I am using the latest stable Linux from Scratch book version. In [Step 5.5.1](https://www.linuxfromscratch.org/lfs/view/stable/chapter05/glibc.html) , when configuring Glibc I run the provided script, and receive an error telling me to use the --with-headers configure option, however I am already using it.
The book states to configure using:
../configure \ --prefix=/usr \ --host=$LFS_TGT \ --build=$(../scripts/config.guess) \ --enable-kernel=3.2 \ --with-headers=$LFS/usr/include \ libc_cv_slibdir=/lib
When doing so I receive the following error:
checking installed Linux kernel header files... missing or too old!
configure: error: GNU libc requires kernel header files from
Linux 3.2.0 or later to be installed before configuring.
The kernel header files are found usually in /usr/include/asm and
/usr/include/linux; make sure these directories use files from
Linux 3.2.0 or later. This check uses , so
make sure that file was built correctly when installing the kernel header
files. To use kernel headers not from /usr/include/linux, use the
configure option --with-headers.
Any advise on how to proceed would be much appreciated.
Lukas
(77 rep)
Jul 8, 2021, 02:35 AM
• Last activity: Jun 21, 2025, 10:49 AM
3
votes
1
answers
7358
views
Error building Oracle client 11g R2 on RHEL 5.5
We are trying to install oracle 11g R2 64 bit in Rhel 5.5 machine ( 64 bit ). Kernel version is 2.6.18-194.el5. We are getting the below error while installation. error in invoking target 'mkldflags ntcontab.o nnfgt.o' of makefile '/home/oracle/app/product/11.2.0/network/lib/ins_net_client.mk'. See...
We are trying to install oracle 11g R2 64 bit in Rhel 5.5 machine ( 64 bit ). Kernel version is 2.6.18-194.el5. We are getting the below error while installation.
error in invoking target 'mkldflags ntcontab.o nnfgt.o' of makefile '/home/oracle/app/product/11.2.0/network/lib/ins_net_client.mk'.
See '/home/oracle/oraInventory/logs/installAction2013-09-03_04-52-05PM.log' for details.
We have installed all necessary library packages.
binutils-2.17.50.0.6-14.el5.x86_64
compat-libstdc++-33-3.2.3-61.x86_64
compat-libstdc++-33-3.2.3-61.i386
elfutils-libelf-0.137-3.el5.x86_64
elfutils-libelf-0.137-3.el5.i386
elfutils-libelf-devel-static-0.137-3.el5.x86_64
elfutils-libelf-devel-static-0.137-3.el5.i386
elfutils-libelf-devel-0.137-3.el5.x86_64
elfutils-libelf-devel-0.137-3.el5.i386
gcc-4.1.2-48.el5.x86_64
gcc-c++-4.1.2-48.el5.x86_64
glibc-2.5-49.x86_64
glibc-2.5-49.i686
glibc-common-2.5-49.x86_64
glibc-devel-2.5-49.x86_64
glibc-devel-2.5-49.i386
glibc-headers-2.5-49.x86_64
ksh-20100202-1.el5.x86_64
libaio-0.3.106-5.x86_64
libaio-0.3.106-5.i386
libaio-devel-0.3.106-5.x86_64
libaio-devel-0.3.106-5.i386
libgcc-4.1.2-48.el5.x86_64
libgcc-4.1.2-48.el5.i386
libstdc++-4.1.2-48.el5.x86_64
libstdc++-4.1.2-48.el5.i386
libstdc++44-devel-4.4.0-6.el5.x86_64
libstdc++44-devel-4.4.0-6.el5.i386
libstdc++-devel-4.1.2-48.el5.x86_64
libstdc++-devel-4.1.2-48.el5.i386
make is already installed:
make-3.81-3.el5.x86_64
Contents of log file:
INFO: Calling Query fileQueries10.1.0.3.0 exists
filename = /home/oracle/app/product/11.2.0/rdbms/lib/libknlopt.a
INFO: Query Returned: false
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/network/lib/ins_nau.mk
installTarget = ioklist
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = null
undoTarget = null
undoArguments = null
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking Adapters
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/network/lib/ins_nau.mk
installTarget = iokinit
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = null
undoTarget = null
undoArguments = null
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking Adapters
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/network/lib/ins_nau.mk
installTarget = iokdstry
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = null
undoTarget = null
undoArguments = null
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking Adapters
INFO: Linking 'Oracle Database Utilities 11.2.0.3.0 '
INFO: Linking 'Oracle Database Utilities 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component Oracle Database Utilities
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/rdbms/lib/ins_rdbms.mk
installTarget = utilities
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = null
undoTarget = null
undoArguments = null
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking Utilities Executables
INFO: Linking 'SQL*Plus 11.2.0.3.0 '
INFO: Linking 'SQL*Plus 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component SQL*Plus
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/sqlplus/lib/ins_sqlplus.mk
installTarget = install
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = null
undoTarget = null
undoArguments = null
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking SQLPLUS Executables
INFO: Linking 'Oracle Programmer 11.2.0.3.0 '
INFO: Linking 'Oracle Programmer 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component Oracle Programmer
INFO: Linking 'Oracle Internet Directory Client 11.2.0.3.0 '
INFO: Linking 'Oracle Internet Directory Client 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component Oracle Internet Directory Client
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/ldap/lib/ins_ldap.mk
installTarget = clientonlyinstall
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = null
undoTarget = clientonlyinstall
undoArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking OID Client
INFO: Calling Action unixActions10.2.0.3.0 registerForMake
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/ldap/lib/ins_ldap.mk
installTarget = clientonlyinstall
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
undoMakeFileName = /home/oracle/app/product/11.2.0/ldap/lib/ins_ldap.mk
undoTarget = clientonlyinstall
undoArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
logFile = /home/oracle/app/product/11.2.0/install/make.log
progMsg = Linking Client-only Install
INFO: Linking 'SQLJ Runtime 11.2.0.3.0 '
INFO: Linking 'SQLJ Runtime 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component SQLJ Runtime
INFO: Linking 'Oracle SQLJ 11.2.0.3.0 '
INFO: Linking 'Oracle SQLJ 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component Oracle SQLJ
INFO: Linking 'Oracle Client 11.2.0.3.0 '
INFO: Linking 'Oracle Client 11.2.0.3.0 '
INFO: 9/3/13 4:54:07 PM IST: Starting install Link Phase of component Oracle Client
INFO: Linking in progress
INFO: Linking in progress
INFO: Link Phase JRE files in Scratch :0
INFO: Calling Action unixActions10.2.0.3.0 make
registerOnly = false
installMakePath = /usr/bin/make
installMakeFileName = /home/oracle/app/product/11.2.0/network/lib/ins_net_client.mk
installTarget = mkldflags ntcontab.o nnfgt.o
undoMakeFileName =
installArguments = ORACLE_HOME=/home/oracle/app/product/11.2.0
logFile = /home/oracle/app/product/11.2.0/install/make.log
undoTarget =
progMsg = Linking ldflags Executables
INFO: Linking ldflags Executables
INFO: Linking ldflags Executables
INFO: The output of this make operation is also available at: '/home/oracle/app/product/11.2.0/install/make.log'
INFO:
INFO: Start output from spawned process:
INFO: ----------------------------------
INFO:
INFO: rm -f ntcontab.*
INFO: (if [ "compile" = "compile" ] ; then \
/home/oracle/app/product/11.2.0/bin/gennttab > ntcontab.c ;\
/usr/bin/gcc -m32 -m32 -fPIC -c ntcontab.c ;\
rm -f /home/oracle/app/product/11.2.0/lib/ntcontab.o ;\
mv ntcontab.o /home/oracle/app/product/11.2.0/lib/ ;\
/usr/bin/ar rv /home/oracle/app/product/11.2.0/lib/libn11.a /home/oracle/app/product/11.2.0/lib/ntcontab.o ; fi)
INFO: /bin/sh: line 2: /usr/bin/gcc: No such file or directory
INFO: mv: cannot stat `ntcontab.o'
INFO: : No such file or directory
INFO: /usr/bin/ar: /home/oracle/app/product/11.2.0/lib/ntcontab.o: No such file or directory
INFO: make: *** [ntcontab.o] Error 1
INFO: End output from spawned process.
INFO: ----------------------------------
INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'mkldflags ntcontab.o nnfgt.o' of makefile '/home/oracle/app/product/11.2.0/network/lib/ins_net_client.mk'. See '/home/oracle/oraInventory/logs/installActions2013-09-03_04-52-05PM.log' for details.
Exception Severity: 1
INFO: Adding ExitStatus STOP_INSTALL to the exit status set
INFO: Finding the most appropriate exit status for the current application
INFO: Exit Status is -4
INFO: Shutdown Oracle Client Installer
What is the solution for this error?
user44663
(69 rep)
Sep 4, 2013, 01:23 PM
• Last activity: Jun 20, 2025, 09:04 PM
4
votes
2
answers
6382
views
Building python with openssl support
I have the following directory structure: nchambers@nchambers-305E4A-305E5A-305E7A:~/mini-bin$ la 2to3 cpp-5.3.0 gcov-5.3.0 grmid-5.3.0 objcopy-2.25.1 python3.5-config .sources 2to3-3.5 elfedit-2.25.1 gcov-tool-5.3.0 grmiregistry-5.3.0 objdump-2.25.1 python3.5m strings-2.25.1 addr2line-2.25.1 g++-5....
I have the following directory structure:
nchambers@nchambers-305E4A-305E5A-305E7A:~/mini-bin$ la
2to3 cpp-5.3.0 gcov-5.3.0 grmid-5.3.0 objcopy-2.25.1 python3.5-config .sources
2to3-3.5 elfedit-2.25.1 gcov-tool-5.3.0 grmiregistry-5.3.0 objdump-2.25.1 python3.5m strings-2.25.1
addr2line-2.25.1 g++-5.3.0 gfortran-5.3.0 gserialver-5.3.0 pydoc python3.5m-config strip-2.25.1
aot-compile-5.3.0 gappletviewer-5.3.0 gij-5.3.0 gtnameserv-5.3.0 pydoc3 python3-config x86_64-unknown-linux-gnu-c++-5.3.0
ar-2.25.1 gc-analyze-5.3.0 gjar-5.3.0 idle pydoc3.5 python-config x86_64-unknown-linux-gnu-g++-5.3.0
.archives gcc-5.3.0 gjarsigner-5.3.0 idle3 python pyvenv x86_64-unknown-linux-gnu-gcc-5.3.0
as-2.25.1 gcc-ar-5.3.0 gjavah-5.3.0 idle3.5 python2 pyvenv-3.5 x86_64-unknown-linux-gnu-gcc-ar-5.3.0
bash gcc-nm-5.3.0 gkeytool-5.3.0 jcf-dump-5.3.0 python2.7 ranlib-2.25.1 x86_64-unknown-linux-gnu-gcc-nm-5.3.0
.binaries gcc-ranlib-5.3.0 gnative2ascii-5.3.0 jv-convert-5.3.0 python2.7-config readelf-2.25.1 x86_64-unknown-linux-gnu-gcc-ranlib-5.3.0
.build gcj-5.3.0 gorbd-5.3.0 ld-2.25.1 python2-config rebuild-gcj-db-5.3.0 x86_64-unknown-linux-gnu-gcj-5.3.0
c++-5.3.0 gcj-dbtool-5.3.0 gprof-2.25.1 ld.bfd-2.25.1 python3 size-2.25.1 x86_64-unknown-linux-gnu-gfortran-5.3.0
c++filt-2.25.1 gcjh-5.3.0 grmic-5.3.0 nm-2.25.1 python3.5 smtpd.py
nchambers@nchambers-305E4A-305E5A-305E7A:~/mini-bin$ la .sources/
bash-4.4-beta binutils-2.25.1 boost_1_60_0 gcc-5.3.0 Python-2.7.11 Python-3.5.1
nchambers@nchambers-305E4A-305E5A-305E7A:~/mini-bin$ la .build/
bash-4.4-beta binutils-2.25.1 boost_1_60_0 gcc-5.3.0 Python-2.7.11 Python-3.5.1
nchambers@nchambers-305E4A-305E5A-305E7A:~/mini-bin$ la .binaries/
bash-4.4-beta binutils-2.25.1 boost_1_60_0 gcc-5.3.0 Python-2.7.11 Python-3.5.1
nchambers@nchambers-305E4A-305E5A-305E7A:~/mini-bin$
Generally, tar balls go in
.archives
, unpacked sources go in .sources
, building happens in .build
, and the final binaries are store in .binaries
. I then symlink the binaries from .binaries
to ~/mini-bin
which is on my $PATH.I know its a weird workflow, but it works for me. Anyways, I am looking to rebuild python-2.7.11 (and 3.4.0, but am starting with 2.7.11) from source. It builds fine on my system, but I need it to build with ncurses, readline, ssl, etc support. Do I have to compile these libraries from source? If so, where would I put the libraries? How do I tell python to build with them. Thank you and have a good day!
DTSCode
(143 rep)
Jan 12, 2016, 01:36 AM
• Last activity: Jun 19, 2025, 04:02 AM
0
votes
1
answers
73
views
Trying to compile a tinycore linux kernel leads to Error 2
EDIT 1 - Following instructions from : https://github.com/on-prem/tinycore-kernel EDIT 2 - after trying **make os**, it fails giving an **Error 2** compiler error. i know that it has something to do with the modern GCC version im using,not being compatible with the older version of GCC. Specifically...
EDIT 1 - Following instructions from : https://github.com/on-prem/tinycore-kernel
EDIT 2 - after trying **make os**, it fails giving an **Error 2** compiler error. i know that it has something to do with the modern GCC version im using,not being compatible with the older version of GCC. Specifically, something to do with a security flaw or risk being registered by **objtool** during the **make os** process. so, this version of tinycore was compiled with an older version of GCC. In addition to that, i am using the most recent linux kernel (6.11) to compile it, and tinycore uses a more outdated kernel (4.19). it is an error having to do with **objtool** and thats as far as i can see. perhaps also, something in the script is missing or no longer available, a missing file, corepure64.gz is not available unless manually installed, and this doesnt change the output, same **Error 2** message
I am using the new Ubuntu 25.04, I am compiling within the regular terminal window. I have followed the steps as they are listed in the tinycore github. the first two steps worked after some packages were installed, but at the third step, it gives me **Error 2**, which seems common and easy to fix. this version of tinycore is using a specific kernel, version 4.19. I think that came out in 2018 or 2019.
I entered into the terminal
sudo make kernel
then, I ran
sudo make extensions
and finally, the **Error 2** comes in when I enter
sudo make os
These are the steps listed in the README and on the github, but here's the exact error I receive.
luma@luma-virtualbox ~/D/tinycore-kernel (master)> sudo make os
rm -rf /tmp/tinycore-kernel-build/os-corepure64
mkdir -p /tmp/tinycore-kernel-build/os-corepure64
cd /tmp/tinycore-kernel-build/os-corepure64 && \
gunzip -c /opt/tinycore/11.x/x86_64/release/distribution_files/corepure64.gz | cpio -id && \
rm -rf lib/modules/* && \
mkdir -p lib/modules/4.19.152-tinycore64 && \
cp -rp /tmp/tinycore-kernel-build/modules-base/usr/local/lib/modules/4.19.152-tinycore64/kernel lib/modules/4.19.152-tinycore64/
gzip: /opt/tinycore/11.x/x86_64/release/distribution_files/corepure64.gz: No such file or directory
cpio: premature end of archive
make: *** [Makefile:94: os] Error 2
What can I do from here?
To note, I was able to compile the standard linux kernel listed by Linus on github. yet, I had this exact same **Error 2** when I did **sudo make os.**. I found a fix where it had something to do with module signing and disabling a key.
When I compiled that kernel, I was able to **sudo make os**, and it did not output **Error 2.** I no longer have access to it and I wanted a smaller alternative.
kernel1111111
(1 rep)
Jun 7, 2025, 08:22 AM
• Last activity: Jun 8, 2025, 10:34 AM
0
votes
1
answers
1889
views
CentOS 7: When building Mapnik, the configure step does not find optional dependencies like libpng-devel, libjpeg-devel, etc
I am trying to build/install Mapnik (3.0.10) on a CentOS 7 system and I am having trouble getting all the dependencies in place and recognized. I have installed gcc/g++ compiler from the gcc6 series to ensure c++14 support, which Mapnik needs. If I point directly to my new `gcc` and poll its version...
I am trying to build/install Mapnik (3.0.10) on a CentOS 7 system and I am having trouble getting all the dependencies in place and recognized.
I have installed gcc/g++ compiler from the gcc6 series to ensure c++14 support, which Mapnik needs. If I point directly to my new
gcc
and poll its version I get this:
[root@raven ~]# /usr/local/bin/gcc --version
gcc (GCC) 6.5.0
Copyright (C) 2017 Free Software Foundat/..snip..
Next I temporarily overrode the $CC
and $CXX
environment variables so the updated compiler would be used for subsequent builds, then I installed Boost 1.69.0 from source, like this. Note that this actually installs a second Boost, so the --prefix
parameter establishes where this alternative Boost will install to:
export CC=/usr/local/bin/gcc
export CXX=/usr/local/bin/g++
cd /root/downloads
wget https://dl.bintray.com/boostorg/release/1.69.0/source/boost_1_69_0.tar.gz
tar -xzf boost_1_*
cd boost_1_*
./bootstrap.sh --prefix=/opt/boost
./b2 install --prefix=/opt/boost --with=all
Now, if I check /opt/boost
, I see what I expect..
[root@raven ~]# dir /opt/boost/
include lib
Finally I get to installing Mapnik itself. I'm basically using the approach noted here . However, I've already got several of the dependencies in place due to previously installing GDAL and PostGIS. But, when I run Mapnik's .configure
step, it fails to find my optional dependencies.
For example, I built proj
from source and know exactly where it is..
[root@raven ~]# dir /usr/proj49/
bin include lib share
And ldconfig
finds it too..
[root@raven mapnik-v3.0.10]# ldconfig -p | grep libproj
libproj.so.12 (libc6,x86-64) => /usr/proj49/lib/libproj.so.12
libproj.so.0 (libc6,x86-64) => /lib64/libproj.so.0
libproj.so (libc6,x86-64) => /usr/proj49/lib/libproj.so
libproj.so (libc6,x86-64) => /lib64/libproj.so
So I specify my alternative Boost location as well as PROJ_LIBS
and PROJ_INCLUDES
as .configure
parameters.....but it still fails to find proj
? Here's some abridged output. Note that it finds my Boost, as specified, but it fails to find proj
, in spite of the config params..
[root@raven ~]# cd /root/downloads/mapnik-v3.0.10
[root@raven mapnik-v3.0.10]# ./configure BOOST_LIBS=/opt/boost/lib BOOST_INCLUDES=/opt/boost/includes PROJ_LIBS=/usr/proj49/lib PROJ_INCLUDES=/usr/proj49/include
..snip..
Searching for boost libs and headers... (cached)
Found boost libs: /opt/boost/lib
Found boost headers: /opt/boost/include
Checking for C++ header file boost/version.hpp... yes
Checking for Boost version >= 1.47... yes
Found boost lib version... 1_69
..snip..
Checking for C library proj... no
Could not find optional header or shared library for proj
..snip..
Most of the optional dependencies seem to be similarly overlooked—libpng-devel
, libjpeg-devel
, sqlite3, the tiff stuff, proj, etc. And most of those are package installs, not source builds.
As we'll be using this server for quite some time I would like to have the latest Mapnik with its full complement of support (especially for proj, png, and jpeg). It's especially vexing that my proj
install isn't tying in, because I know exactly where it is and provided Mapnik those parameters.
I apologize for the long noisy read, but does anyone see what I am missing?
[**Update**: 4.24.19 5pm]
Ok, I may have figured it out. I was hoping it had something to do with environment/shell setup, rather than having to build all dependencies from source with the same compiler, and stumbled onto an old post where a "Dom Lehr" recommended modifying the LD_LIBRARY_PATH
environment variable to include specifically /usr/local/lib
. Well, I tried that, and it didn't solve the problem. However, I optimistically expanded the parameter values to include some additional locations, and now I can complete the .configure
step with all dependencies recognized. Here's how I did it..
vi /etc/profile.d/sh.local
# Add colon-separated paths to the LD_LIBRARY_PATH variable like this..
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib:/usr/local/lib64:/usr/lib:/usr/lib64:
I added everything I could think of where I found seemingly related .so files. Save the file, then..
/sbin/ldconfig
ldconfig
Then I logged out of my terminal session and logged back in to refresh the shell. Then double-checked that it worked:
[root@raven mapnik-v3.0.10]# echo $LD_LIBRARY_PATH
/opt/remi/php70/root/usr/lib64::/usr/local/lib:/usr/local/lib64:/usr/lib:/usr/lib64:
It did. So I refreshed my temporary compiler arguments, went to the Mapnik source folder, and re-ran the .configure
instruction, and it worked without issue..
export CC=/usr/local/bin/gcc
export CXX=/usr/local/bin/g++
cd /root/downloads/mapnik-v3.0.10
./configure BOOST_LIBS=/opt/boost/lib BOOST_INCLUDES=/opt/boost/includes
And it worked. Now, whether it will build without issue is still a mystery, but this seems to have done the trick!
Well I spoke to soon. Now make
fails with..
> >&&’
scons: *** [src/json/mapnik_json_geometry_grammar.o] Error 1
scons: building terminated because of errors.
make: *** [src/json/libmapnik-json.a] Error 2
....which is in-line with a lot of others posts I've found where folks are having trouble with mismatched compiler/dependency issues. Back to the drawing board.
elrobis
(101 rep)
Apr 24, 2019, 03:44 PM
• Last activity: Jun 5, 2025, 03:05 AM
2
votes
1
answers
2396
views
libbfd-2.22.so missing while compiling Binutils/Glibc/Zlib
When I try to compile Binutils, Glibc and Zlib using chroot on my [LFS](http://www.linuxfromscratch.org/lfs/) system, I get this error: > ar: error while loading shared libraries: libbfd-2.22.so: cannot open shared object file: No such file or directory I compiled Binutils before without using chroo...
When I try to compile Binutils, Glibc and Zlib using chroot on my [LFS](http://www.linuxfromscratch.org/lfs/) system, I get this error:
> ar: error while loading shared libraries: libbfd-2.22.so: cannot open shared object file: No such file or directory
I compiled Binutils before without using chroot, the files libbfd.a, libbfd.so, libbfd-2.22.so and libbfd.la exist both in /tools/lib/ and /usr/lib/
I don't know where the compiler is searching for it.
How to continue compilation?
Vi Pau
(166 rep)
Aug 1, 2012, 07:29 AM
• Last activity: Jun 3, 2025, 09:01 PM
0
votes
1
answers
2038
views
(Buildroot) "silentoldconfig" error on compile
I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM. Unfortunately, this appears...
I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM.
Unfortunately, this appears to not be the case as I am greeted with the following error upon attempting to build in this new VM:
#
# configuration written to /home/mirion/mirion/buildroot-2013.05/.config
#
/usr/bin/make -j5 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
make: Entering directory '/home/mirion/mirion/buildroot-2013.05'
BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/tristate.config BUILDROOT_CONFIG=/home/mirion/mirion/buildroot-2013.05/.config /home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/conf --silentoldconfig Config.in
*** Error during update of the configuration.
Makefile:692: recipe for target 'silentoldconfig' failed
make: *** [silentoldconfig] Error 1
make: Leaving directory '/home/mirion/mirion/buildroot-2013.05'
Makefile:396: recipe for target '/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf' failed
make: *** [/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf] Error 2
mv: cannot stat 'output/images/rootfs.ubi': No such file or directory
Are there any ideas as to what I can do to resolve this?
I did some poking around on google but could not find anything conclusive.
EDIT: Original VM was running Lubuntu 12.04, the new VM is running Ubuntu 17.10.
Thanks.
lukemk1
(39 rep)
Apr 9, 2018, 05:57 PM
• Last activity: Jun 1, 2025, 08:04 AM
187
votes
4
answers
244663
views
What is the Fedora equivalent of the Debian build-essential package?
What is the Fedora equivalent of the Debian build-essential package?
What is the Fedora equivalent of the Debian build-essential package?
Steve Burdine
(6499 rep)
Aug 28, 2010, 02:07 PM
• Last activity: May 29, 2025, 08:39 AM
2
votes
1
answers
2723
views
libzip Linux cross-compile configuration
I am trying to cross compile **libzip-1.5.1** having previously successfully complied **zlib-1.2.11** (these are required by libzip and I have installed in a local home path), but I am experiencing problems with the cmake's process. The script I use to build and compile (from a build directory into...
I am trying to cross compile **libzip-1.5.1** having previously successfully complied **zlib-1.2.11** (these are required by libzip and I have installed in a local home path), but I am experiencing problems with the cmake's process.
The script I use to build and compile (from a build directory into the libzip's sources folder) is the following:
#!/bin/sh
PREFIX=${PWD}/install
CCPATH=/opt/arm64/gcc-linaro-6.3.1-2017.02-rc2-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf
ZLIBPATH=${PWD}/../../zlib-1.2.11/
# here is where zlib is installed
# ZLIBINSTALLEDPATH contains include, lib, share directories
ZLIBINSTALLEDPATH=${ZLIBPATH}/build_armhf64/install/
export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:${ZLIBINSTALLEDPATH}/lib/pkgconfig/"
export LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${ZLIBINSTALLEDPATH}/lib/"
export CMAKE_AR=${CCPATH}-ar
export CC=${CCPATH}-gcc
export CXX=${CCPATH}-g++
export CMAKE_LINKER=${CCPATH}-ld
export CMAKE_RANLIB=${CCPATH}-ranlib
export CMAKE_OBJDUMP=${CCPATH}-objdump
export CMAKE_OBJCOPY=${CCPATH}-objcopy
export CMAKE_STRIP=${CCPATH}-strip
#export CMAKE_READELF=${CCPREFIX}-readelf
export CMAKE_NM=${CCPATH}-nm
cmake -DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DZLIB_INCLUDE_DIR=${ZLIBINSTALLEDPATH}/include/ \
-DZLIB_LIBRARY=${ZLIBINSTALLEDPATH}/lib/ \
../
make -j 8
But at 94 % of building process, I get the following errors:
[ 92%] Building C object regress/CMakeFiles/tryopen.dir/tryopen.c.o
[ 94%] Building C object src/CMakeFiles/zipcmp.dir/zipcmp.c.o
[ 94%] Linking C executable add_from_filep
[ 94%] Linking C executable fopen_unchanged
[ 94%] Linking C executable tryopen
[ 94%] Building C object regress/CMakeFiles/hole.dir/source_hole.c.o
[ 94%] Linking C executable zipmerge
../lib/libzip.so.5.0: undefined reference to `inflate'
../lib/libzip.so.5.0: undefined reference to `crc32'
../lib/libzip.so.5.0: undefined reference to `zError'
../lib/libzip.so.5.0: undefined reference to `deflate'
../lib/libzip.so.5.0: undefined reference to `deflateInit2_'
../lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `inflateInit2_'
collect2: error: ld returned 1 exit status
regress/CMakeFiles/add_from_filep.dir/build.make:95: recipe for target 'regress/add_from_filep' failed
make: *** [regress/add_from_filep] Error 1
CMakeFiles/Makefile2:726: recipe for target 'regress/CMakeFiles/add_from_filep.dir/all' failed
make: *** [regress/CMakeFiles/add_from_filep.dir/all] Error 2
make: *** Waiting for unfinished jobs....
../lib/libzip.so.5.0: undefined reference to `inflate'
../lib/libzip.so.5.0: undefined reference to `crc32'
../lib/libzip.so.5.0: undefined reference to `zError'
../lib/libzip.so.5.0: undefined reference to `deflate'
../lib/libzip.so.5.0: undefined reference to `deflateInit2_'
../lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `inflateInit2_'
collect2: error: ld returned 1 exit status
regress/CMakeFiles/tryopen.dir/build.make:95: recipe for target 'regress/tryopen' failed
make: *** [regress/tryopen] Error 1
CMakeFiles/Makefile2:800: recipe for target 'regress/CMakeFiles/tryopen.dir/all' failed
make: *** [regress/CMakeFiles/tryopen.dir/all] Error 2
../lib/libzip.so.5.0: undefined reference to `inflate'
../lib/libzip.so.5.0: undefined reference to `crc32'
../lib/libzip.so.5.0: undefined reference to `zError'
../lib/libzip.so.5.0: undefined reference to `deflate'
../lib/libzip.so.5.0: undefined reference to `deflateInit2_'
../lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `inflateInit2_'
collect2: error: ld returned 1 exit status
regress/CMakeFiles/fopen_unchanged.dir/build.make:95: recipe for target 'regress/fopen_unchanged' failed
make: *** [regress/fopen_unchanged] Error 1
CMakeFiles/Makefile2:615: recipe for target 'regress/CMakeFiles/fopen_unchanged.dir/all' failed
make: *** [regress/CMakeFiles/fopen_unchanged.dir/all] Error 2
[ 94%] Building C object regress/CMakeFiles/ziptool_regress.dir/source_hole.c.o
../lib/libzip.so.5.0: undefined reference to `inflate'
../lib/libzip.so.5.0: undefined reference to `crc32'
../lib/libzip.so.5.0: undefined reference to `zError'
../lib/libzip.so.5.0: undefined reference to `deflate'
../lib/libzip.so.5.0: undefined reference to `deflateInit2_'
../lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `inflateInit2_'
collect2: error: ld returned 1 exit status
src/CMakeFiles/zipmerge.dir/build.make:95: recipe for target 'src/zipmerge' failed
make: *** [src/zipmerge] Error 1
CMakeFiles/Makefile2:432: recipe for target 'src/CMakeFiles/zipmerge.dir/all' failed
make: *** [src/CMakeFiles/zipmerge.dir/all] Error 2
[ 94%] Linking C executable zipcmp
[ 94%] Linking C executable ziptool
[ 96%] Linking C executable hole
CMakeFiles/zipcmp.dir/zipcmp.c.o.:. /Inlib /functionlibzip.so.5.0 :` compute_crcundefined' :reference
zipcmp.cto: (`.inflatetext'+
0x4a0.).:/ libundefined/ libzip.so.5.0reference: toundefined `referencecrc32 'to
zipcmp.c`:crc32('.
text.+.0x53e/)lib:/ libzip.so.5.0undefined: referenceundefined toreference
tocrc32 '
zErrorCMakeFiles'/
zipcmp.dir./.zipcmp.c.o/:lib /Inlibzip.so.5.0 :function undefined` test_filereference':
zipcmp.cto: (`.deflatetext'+
0x1494.).:/ libundefined/ libzip.so.5.0reference: toundefined `referencecrc32'
zipcmp.c:(.text+0x14fe): undefined reference to `crc32'
.. /tolib /`libzip.so.5.0deflateInit2_:'
undefined. .reference/ libto/ libzip.so.5.0`:inflate 'undefined
.reference. /tolib /`libzip.so.5.0inflateEnd:'
undefined. .reference/ libto/ libzip.so.5.0`:zError 'undefined
.reference. /tolib /libzip.so.5.0deflateEnd:' undefined reference to
deflate'
.
../.lib//liblibzip.so.5.0/:libzip.so.5.0 :undefined undefinedreference referenceto to deflateInit2_
'inflateInit2_
'.
./lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `collect2: error: ld returned 1 exit status
inflateInit2_'
collect2: error: ld returned 1 exit status
src/CMakeFiles/ziptool.dir/build.make:95: recipe for target 'src/ziptool' failed
make: *** [src/ziptool] Error 1
src/CMakeFiles/zipcmp.dir/build.make:95: recipe for target 'src/zipcmp' failed
make: *** [src/zipcmp] Error 1
CMakeFiles/Makefile2:469: recipe for target 'src/CMakeFiles/ziptool.dir/all' failed
make: *** [src/CMakeFiles/ziptool.dir/all] Error 2
CMakeFiles/Makefile2:395: recipe for target 'src/CMakeFiles/zipcmp.dir/all' failed
make: *** [src/CMakeFiles/zipcmp.dir/all] Error 2
../lib/libzip.so.5.0: undefined reference to `inflate'
../lib/libzip.so.5.0: undefined reference to `crc32'
../lib/libzip.so.5.0: undefined reference to `zError'
../lib/libzip.so.5.0: undefined reference to `deflate'
../lib/libzip.so.5.0: undefined reference to `deflateInit2_'
../lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `inflateInit2_'
collect2: error: ld returned 1 exit status
[ 98%] Linking C executable ziptool_regress
regress/CMakeFiles/hole.dir/build.make:121: recipe for target 'regress/hole' failed
make: *** [regress/hole] Error 1
CMakeFiles/Makefile2:652: recipe for target 'regress/CMakeFiles/hole.dir/all' failed
make: *** [regress/CMakeFiles/hole.dir/all] Error 2
../lib/libzip.so.5.0: undefined reference to `inflate'
../lib/libzip.so.5.0: undefined reference to `crc32'
../lib/libzip.so.5.0: undefined reference to `zError'
../lib/libzip.so.5.0: undefined reference to `deflate'
../lib/libzip.so.5.0: undefined reference to `deflateInit2_'
../lib/libzip.so.5.0: undefined reference to `inflateEnd'
../lib/libzip.so.5.0: undefined reference to `deflateEnd'
../lib/libzip.so.5.0: undefined reference to `inflateInit2_'
collect2: error: ld returned 1 exit status
regress/CMakeFiles/ziptool_regress.dir/build.make:121: recipe for target 'regress/ziptool_regress' failed
make: *** [regress/ziptool_regress] Error 1
CMakeFiles/Makefile2:689: recipe for target 'regress/CMakeFiles/ziptool_regress.dir/all' failed
make: *** [regress/CMakeFiles/ziptool_regress.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
It seems that cmake cannot find the compiled zlib libraries, even if the paths seems to be well configured (or not ?).
Do some has experienced similar issues with libzip ?
Is there any addition cmake's macro that would solve this issue ?
**---- UPDATE ----**
----------
I actually get rid of this error suppressing building task for **zipcmp**, **zipmerge** and **ziptool** (since I don't need them) commenting the lines:
#ADD_EXECUTABLE(zipcmp zipcmp.c ${SRC_EXTRA_FILES})
#TARGET_LINK_LIBRARIES(zipcmp zip)
#INSTALL(TARGETS zipcmp RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR})
#ADD_EXECUTABLE(zipmerge zipmerge.c ${SRC_EXTRA_FILES})
#TARGET_LINK_LIBRARIES(zipmerge zip)
#INSTALL(TARGETS zipmerge RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR})
#ADD_EXECUTABLE(ziptool ziptool.c ${SRC_EXTRA_FILES})
#TARGET_LINK_LIBRARIES(ziptool zip)
#INSTALL(TARGETS ziptool RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR})
into src/CMakeLists.txt
.
Then I compiled the libs using make -j 8 zip
and then make install/fast
.
It still returns the error
Install the project...
-- Install configuration: ""
-- Installing: /home/simo/adtdev/Var_libs/libzip-1.5.1/build_armhf64/install/lib/pkgconfig/libzip.pc
-- Installing: /home/simo/adtdev/Var_libs/libzip-1.5.1/build_armhf64/install/include/zipconf.h
-- Installing: /home/simo/adtdev/Var_libs/libzip-1.5.1/build_armhf64/install/include/zip.h
-- Installing: /home/simo/adtdev/Var_libs/libzip-1.5.1/build_armhf64/install/lib/libzip.a
CMake Error at man/cmake_install.cmake:36 (file):
file INSTALL cannot find
"/home/simo/adtdev/Var_libs/libzip-1.5.1/build_armhf64/man/ZIP_SOURCE_GET_ARGS.3".
Call Stack (most recent call first):
cmake_install.cmake:46 (include)
Makefile:89: recipe for target 'install/fast' failed
make: *** [install/fast] Error 1
but I don't care about it since I have the libs and headers installed in the install dir, and this is what I need.
xyx
(797 rep)
Nov 8, 2018, 01:41 PM
• Last activity: May 23, 2025, 11:06 AM
Showing page 1 of 20 total questions