I'm trying to load a kernel module into the kernel by running the following command,
`anthony#ubuntu:~/Desktop/kmaldetect/loadable_kernel_module$ make -C /lib/modules/$(uname -r)/build
This is the error that i get:
make: Entering directory /usr/src/linux-headers-3.19.0-25-generic'
arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support
Makefile:669: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
make[1]: *** No rule to make target `arch/x86/syscalls/syscall_32.tbl', needed by `arch/x86/syscalls/../include/generated/asm/syscalls_32.h'. Stop.
make: *** [archheaders] Error 2
make: Leaving directory `/usr/src/linux-headers-3.19.0-25-generic'
Maybe someone could help me out.
All help is appreciated.
The Makefile in kmaldetect/loadable_kernel_module seems correct, doesn't simply running make there work?
Related
Here is aws-iot-device-sdk-embedded-C sample. But when I invoke make command I got error like:
~/environment/aws-iot-device-sdk-embedded-C/samples/linux/subscribe_publish_sample ((6c99912...)) $ make
make -C ../../../external_libs/mbedTLS
make[1]: Entering directory `/home/ec2-user/environment/aws-iot-device-sdk-embedded-C/external_libs/mbedTLS'
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory `/home/ec2-user/environment/aws-iot-device-sdk-embedded-C/external_libs/mbedTLS'
make: *** [all] Error 2
How build and run this sample? (I am not C developer so please provide detailed answer if possible)
The reason is missing mbedTLS library.
Please go to:
/home/ec2-user/environment/aws-iot-device-sdk-embedded-C/external_libs/mbedTLS
and have a look at it's README:
# Copy source code for mbedTLS into this directory
#
# You'll need to download mbedTLS from the official ARMmbed repository and
# place the files here. We recommend that you pick the latest version of 2.16
# LTS release in order to have up-to-date security fixes.
I am installing HAWQ on RedHat servers provisioned on Amazon EC2. I already have HDP 2.3 setup on the cluster.
I have cloned HAWQ from Github.
First I run ./configure --prefix=/opt/hawq.
In the second step, I run make.
The dependencies are compiling correctly when I run make from the root folder of incubator-hawq. The following error occours when make moves to compiling from src folder in the root directory (incubator-hawq):
make[2]: Entering directory `/root/incubator-hawq/src/port'
gcc -O3 -std=gnu99 -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels -Wformat-security -fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations -I/usr/include/libxml2 -I../../src/port -DFRONTEND -I../../src/include -D_GNU_SOURCE -I/root/incubator-hawq/depends/libhdfs3/build/install/usr/local/hawq/include -I/root/incubator-hawq/depends/libyarn/build/install/usr/local/hawq/include -c -o copydir.o copydir.c
In file included from copydir.c:25:0:
../../src/include/storage/fd.h:61:23: fatal error: hdfs/hdfs.h: No such file or directory
#include "hdfs/hdfs.h"
^
compilation terminated.
make[2]: *** [copydir.o] Error 1
make[2]: Leaving directory `/root/incubator-hawq/src/port'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/incubator-hawq/src'
make: *** [all] Error 2
I know the compiler cannot find hdfs/hdfs.h, but as the dependencies (libhdfs3) compiled successfully, I don't understand why the particular file isn't found. Please help if somebody has come across the same problem as I am pretty much stuck here.
Could you check file /root/incubator-hawq/depends/libhdfs3/build/install/usr/local/hawq/include/hdfs/hdfs.h exists?
If not, then it should be build defect, please open defect to hawq team or email to: dev#hawq.incubator.apache.org. Thanks.
Do you have a folder in incubator-hawq/depends/libhdfs3/build/installafter make?
The problem seems that libhdfs3 dependency is not successfully built. There are some possible reasons for that: using a old version gcc(<4.7), configuration error of libhdfs3.
To test my words, you could try this:
cd incubator-hawq/depends/libhdfs3
mkdir build_debug && cd build_debug
cmake ..
make
If you could successfully do that, I think there is another reason for your problem. In this case, could you paste the information with more building lines?
Another possible reason is that you use different configuration prefix. In this case, you should run make distclean before another configuration.
I am working on a basic kernel which is not supporting Make command.
The drivers provided by intel use Makefile to install.
So I cant copy the file into my target and run make.
I tried to cross compile but its giving following error.
make[1]: Entering directory /usr/src/linux-headers-3.11.0-15-generic'
/usr/src/linux-headers-3.11.0-15-generic/arch/x86/Makefile:92:
stack protector enabled but no compiler support
rm: cannot remove/home/sigma/karthik1/igb-5.3.4.4/src/.tmp_versions/igb.mod': Permission denied
make[1]: * [crmodverdir] Error 1
make[1]: Leaving directory `/usr/src/linux-headers-3.11.0-15-generic'
make: * [default] Error 2
I want to install mod_tile on opensuse. I am following the link to install it; after
#./configure
I run make:
#make
it shows the below error:
make[1]: *** [src/gen_tile.o] Error 1
make[1]: Leaving directory `/opt/mod_tiles_src/mod_tile'
its duplicate of the Other issue
i used the code from
https://github.com/springmeyer/mod_tile
which is working fine..
Iam trying to build a cross compiler using this tutorial:
http://wiki.osdev.org/OS_Specific_Toolchain
after succesfully building binutils,all-gcc,newlib
I am getting an error in the last part of make in build-gcc
checking for shl_load... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
Makefile:8970: recipe for target `configure-target-libstdc++-v3' failed
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/usr/src/build-gcc'
Makefile:870: recipe for target `all' failed
make: *** [all] Error 2
please help...
I don't know you configure command options. But if you have given --enable-language=c change it to --enable-languages=c. Or may be you are compiling bootstrap with languages c and c++. In which case this error occurs.
I ran into this issue when attempting to build a cross compiler for ARM. Eventually, switched to using crosstool-NG. It is a script that greatly simplifies the process. It worked like a charm for me.