New answers tagged

4

The first step is to determine what configuration options you need to set in order for the module to build. I use make menuconfig for that; / followed by the configuration option you want will tell you where to find it and what its dependencies are. For ECHAINIV, you need to enable CRYPTO and then enable ECHAINIV (as a module since that’s what you’re after ...


1

In general, you can do: make clean to clean up most artifacts generated by the build.


0

For this particular case I solved the issue by recompiling the openssl package, issue commands: $ ./configure $ make # make install (the last two commands has to be done as root.)


2

The most straightforward approach I know of is to use the build requirements which the package maintainers have determined are relevant, on a compatible distribution. Since Python 3 isn’t available in CentOS, you’d have to look at EPEL or some other repository; Fedora hosts the relevant source package. To list the build dependencies on an RPM-based ...


1

Per rpm.org, dependencies are defined in the .spec file, With this tag a package can require another with the matching name or Provides to be installed (if the package containign the Requires: is going to be installed). This is checked when a new package is installed and if a package with a matching Provides: is removed. And the example they provide, ...


1

The build is missing -lX11; to work around that, run ./configure LIBS=-lX11 && make


Top 50 recent answers are included