Hot answers tagged

11

Your error message is: make: cc: Command not found which tells you that you are missing the C compiler. As @GAD3R suggests, installing the Development Tools group will correct this. You probably also need the pam-devel package. But, that said: there's really no reason to build pam_radius yourself, as it already exists in EPEL ("Extra Packages for ...


5

You need to install the Development Tools : sudo yum groupinstall 'Development Tools'


3

Kusalananda's answer is the better approach generally; but in netatalk's case, upgrading the package to a newer version seems rather complex (at least, in the context of a distribution). Now that you've installed your locally-built version of netatalk, I would recommend the following approach (I'm assuming you extracted netatalk to a directory called ...


2

There's no general way to know which library is required to use a particular function. You need to look at the documentation of that library. A well-written tutorial or API reference should tell you, that's its job. You can at least get an idea of what library package is required: it's the same library package that contains the header file. How to determine ...


2

You should not have done the mkdir .config; you should have just copied the existing config file to a filename called .config in the kernel source directory. e.g. cd linux-yocto-3.14 cp /path/to/config-3.14.26-yocto-qemu .config make -j4 all


2

nixpkgs reorganized things since the accepted answer was posted and there is a new function for disabling tests. You now wrap any Haskell package with the nixpkgs.pkgs.haskell.lib.dontCheck function to disable tests. Here is an example Nix expression from one of my Haskell projects where I had to disable tests for the shared-memory dependency when building ...


1

As a sum up of the comments. One has to add the environment variables as follows. LD_LIBRARY_PATH="/home/<user>/lib" LIBRARY_PATH="/home/<user>/lib" CPATH="/home/<user>/include"


1

When compiling/installing from source, as with most software distributions like this, the service will not be installed. You need to do those steps manually (or with configuration management of some type). Here's an example that I find, specifically for Samba 4 on a systemd based Linux system. Translating from here: https://dev.tranquil.it/wiki/SAMBA_-...


1

As can be seen in the Catalogue of Built-In Rules: Linking a single object file n is made automatically from n.o by running the linker (usually called ld) via the C compiler. The precise recipe used is: $(CC) $(LDFLAGS) n.o $(LOADLIBES) $(LDLIBS) and Variables Used by Implicit Rules: LDFLAGS Extra flags to give to compilers when they ...


1

/usr/bin/ld : cannot find -lXmu -lXmu means libXmu.so , provided by the package libXmu-devel, 64bits. Please install, like # yum install libXmu-devel.x86_64


1

Those options work by passing options to the compiler, so the most straightforward way is to recompile the kernel. However for a reproducible and module-specific way kbuild allows you to set custom CFLAGs on a per-module basis. https://www.kernel.org/doc/Documentation/kbuild/makefiles.txt You particularly want to set -fno-stack-protector for the modules ...



Only top voted, non community-wiki answers of a minimum length are eligible