I am building Xenomai 2 on a Kernel version 3 with buildroot. Buildroot ist done. Now I am trying to compile it with the "make" command. When I try to compile with the "make" command it appears a failure: recipe for target 'doc/automake-1.14.1' failed. Any help how I can solve that problem?
Ubuntu already has automake version 1.15.1. So I don't really know why it is making the 1.14.1 version while building. Can I change that somewhere?
I have also tried to install the 1.14.1 version but that did not work because it did not find that version, although I have downloaded it...
Here is the cmd-window output:
GEN doc/automake-1.14.1
help2man: can't get `--help' info from automake-1.14
Try `--no-discard-stderr' if option outputs to stderr
Makefile:3707: recipe for target 'doc/automake-1.14.1' failed
make[1]: *** [doc/automake-1.14.1] Error 255
make[1]: Leaving directory '/home/daniel/Desktop/ccode/Daniel/buildroot-2014.08/output/build/host-automake-1.14.1'
package/pkg-generic.mk:177: recipe for target '/home/daniel/Desktop/ccode/Daniel/buildroot-2014.08/output/build/host-automake-1.14.1/.stamp_built' failed
make: *** [/home/daniel/Desktop/ccode/Daniel/buildroot-2014.08/output/build/host-automake-1.14.1/.stamp_built] Error 2
````````````````
This issue was fixed on September 11, 2014 by commit 2020ddbd0f2c32863e6be69a235852a088744c28. Please use an up-to-date version of Buildroot.
Related
I'm working with a Linux driver that is building on v5.7.x kernels but not on the latest v5.8.x releases.
To summarise, most of the driver is pre-built and the kernel interface is built on the target. This involves a make -f Kbuild command.
Having checked all of the relevant kernel interface files for any changes that would affect us, normally the driver would just build as usual on a new kernel. However, this time we get the following error:
make[2]: *** [scripts/Makefile.modpost:111: /path/to/source/Module.symvers] Error 1
make[1]: *** [Makefile:1669: modules] Error 2
make[1]: Leaving directory '/usr/src/kernels/5.8.0-1.el8.elrepo.x86_64'
make: *** [Kbuild:26: default] Error 2
This is from CentOS 8.1, but the same error has been seen on Ubuntu 20.04.
I am no expert on this so interpreting these errors is a bit difficult. I have tried building with the KBUILD_VERBOSE flag and it doesn't really provide any useful information, other than the build succeeding until this point.
On previous kernels the Module.symvers file would be created but empty. On 5.8 this file is not created at all presumably due to this error. As a result, the .ko file is not created.
Finally, if we drop in the source files rather than the pre-built .o files the build does succeed. These .o files are built with a very old version of GCC (4.4.7) but we have also tried building with a much newer version (8.3.1), the same version as the target machine.
I would appreciate suggestions for things to check. Let me know if any other details would help.
Edit:
I ran make on Makefile.modpost manually and got the following output:
sudo make -f ./scripts/Makefile.modpost
WARNING: Symbol version dump "vmlinux.symvers" is missing.
Modules may not have dependencies or modversions.
make -f /scripts/Makefile.modfinal
make[1]: Entering directory '/usr/src/linux-headers-5.8.0-050800-generic'
make[1]: /scripts/Makefile.modfinal: No such file or directory
make[1]: *** No rule to make target '/scripts/Makefile.modfinal'. Stop.
make[1]: Leaving directory '/usr/src/linux-headers-5.8.0-050800-generic'
make: *** [scripts/Makefile.modpost:117: __modpost] Error 2
I am answering my own question in case it helps anyone else with this problem. Although it has never been an issue in the past, we've always had a warning that the corresponding .o.cmd file was not present for our .o_shipped files. This appears to be important in kernel 5.8 onwards and my fix was to add a touch command to the Kbuild file (i.e. "touch .driver.o.cmd"). This does not remove the warning but it allows the driver to build as normal.
I'm building a Linux kernel on Fedora 28, but always run into the same error such as:
CC init/main.o
init/main.o: warning: objtool: elf_begin: invalid command
make[1]: *** [scripts/Makefile.build:277: init/main.o] Error 1
make[1]: *** Deleting file 'init/main.o'
make: *** [Makefile:1067: init] Error 2
make: *** Waiting for unfinished jobs....
I tried "linux-5.0.16.tar.gz" and "linux-5.0.21.tar.gz" downloaded from kernel.org
, and also tried to follow the instruction on Fedora wiki
But there is no way to avoid this 'invalid command' error. "elfutils-libelf-devel" and "elfutils-libelf" are installed. In the fedora way, 'fedpkg cone -a kernel' was successful, so all dependences are installed. Does anyone know what is missing?
Further progress:
The same procedure works on a different machine installed with Fedora 30.
However, after upgrading the original machine to Fedora 30, the error persists.
The machine with the 'invalid command' problem had an old version of libelf.so installed under /user/local. After removing the old libelf, objtool is linked to the current libelf library, and is able to run during compilation of the linux kernel.
A comment is found in the linux source code /tools/perf/util/symbols.h:
/*
* libelf 0.8.x and earlier do not support ELF_C_READ_MMAP;
* for newer versions we can use mmap to reduce memory usage:
*/
This comment led me to look for an out-dated version of libelf.
I am using:
linux openSUSE Tumbleweed
octave-4.0.1
gdcm-2.6.3
I have recently gotten into using linux for my research in university. For this research, I have been trying to install the dicom package into octave from the octave forge. When I submit the code pkg install -forge dicom into octave, I get fatal error: gdcm-2.0/gdcmReader.h: No such file or directory causing the installation to fail.
I have searched around for fixes to this problem which appears to have happened to several people in the past (see Dependency library not recognized during installation octave forge dicom package in debian linux). However, since I am new to linux, I really don't understand what these users have done to solve their problem. Additionally, both octave and gdcm have updated since these posts. I also, have not been able to find an updated version of the dicom package while I have been trying to troubleshoot this. If anyone has any input on this I would greatly appreciate it.
Below is what I am seeing in the command window log.
>> pkg install -forge dicom
dicomread.cpp:27:38: fatal error: gdcm-2.0/gdcmImageReader.h: No such file or directory
compilation terminated.
make: *** [Makefile:44: dicomread.oct] Error 1
make: *** Waiting for unfinished jobs....
dicominfo.cpp:45:33: fatal error: gdcm-2.0/gdcmReader.h: No such file or directory
compilation terminated.
dicomlookup.cpp:23:31: fatal error: gdcm-2.0/gdcmDict.h: No such file or directory
compilation terminated.
make: *** [Makefile:51: dicominfo.o] Error 1
dicomdict.cpp:30:31: fatal error: gdcm-2.0/gdcmDict.h: No such file or directory
compilation terminated.
make: *** [Makefile:60: dicomlookup.o] Error 1
make: *** [Makefile:57: dicomdict.o] Error 1
make: Entering directory '/tmp/oct-5jTUbJ/dicom/src'
mkoctfile -c -g dicominfo.cpp
mkoctfile -c -g dicomdict.cpp
mkoctfile -L/usr/local/lib -lgdcmcharls -lgdcmjpeg8 -lgdcmjpeg12 -lgdcmjpeg16 -lgdcmCommon -lgdcmDICT -lgdcmDSED -lgdcmIOD -lgdcmMSFF -g dicomread.cpp
mkoctfile -c -g dicomlookup.cpp
make: Leaving directory '/tmp/oct-5jTUbJ/dicom/src'
pkg: error running `make' for the dicom package.
error: called from 'configure_make' in file /usr/share/octave/4.0.1/m/pkg/private/configure_make.m near line 96, column 9
>>
This is due to the dicom package being very outdated (2011).
Recently, a number of researchers have updated the package to use the latest version of gdcm and removed some of the hardcodings that made installing gdcm beyond 2.0 uncompatable with the dicom library.
A thread on this is available here
http://octave.1599824.n4.nabble.com/Can-t-install-dicom-package-0-1-1-and-0-1-2-user-version-in-octave-4-0-2-and-ubuntu-14-0-td4681648.html
In short, their instructions are to use a repo of an updated version of dicom package installed. This assumes that gdcm has been installed with headers (i.e built from source).
hg clone http://hg.code.sf.net/p/octave/dicom
cd dicom
make install
during installation of NS2 v2.35 (Cygwin v1.7.32) in Windows 8 i keep getting this error message:
Package gcc4 is not present on your system.
Please install it using Cygwin's setup.exe
before trying to install the ns-2 distribution.
I tried downloading the gcc4 package from the setup but it does not show that it has a gcc4 package. So, i downloaded it from internet but the file was empty!!! If i ignore the warning for gcc4 and continue with the installation then i got the following error.
/usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld: final l ink failed: Invalid operation
collect2: error: ld returned 1 exit status
Makefile:569: recipe for target `tclsh.exe' failed
make: *** [tclsh.exe] Error 1
tcl8.5.10 make failed! Exiting ...
For problems with Tcl/Tk see http://www.scriptics.com
Somebody please help me!!!
Latest gcc ,i.e., 4.8 not compatible, Go for older versions of gcc like 4.7
I install cygwin 1.7.10 on windows 7.
I want to install gearmand-0.28,when during the make,it can't find spawn.h.
The error is:
./libtest/cmdline.h:24:19: fatal error: spawn.h: No such file or directory
compilation terminated.
Makefile:4157: recipe for target `libtest/libtest_libtest_la-binaries.lo' failed
make[1]: *** [libtest/libtest_libtest_la-binaries.lo] Error 1
make[1]: 离开目录“/home/power/gearmand-0.28”
Makefile:2072: recipe for target `all' failed
make: *** [all] Error 2
Which package I need install?
Looks like it's an issue with some versions of gearman with Cygwin. I finally managed to install gearmand, but an old version: 0.14. (see https://launchpad.net/gearmand/+download )
My environment: Cygwin 1.7.13-1, Windows 7 64-bit.
Don't forget to install boost, gcc, make, libuuid1-devel and libiconv. You can download & install them with Cygwin (setup.exe)