Tag Info

New answers tagged

0

Why did you remove the R8169-driver? It should have worked with your card since late 2006.


0

After you've compiled Solr, you must go to the solr/ directory, and run the ant command dist in order to build the JARs: ant dist The Solr WAR file will now be present at solr/dist/solr-<version>.war.


23

This comes from automake, specifically from its AM_SANITY_CHECK macro, which is called from AM_INIT_AUTOMAKE, which is normally called early in configure.ac. The gist of this macro is: Check that the path to the source directory doesn't contain certain “unsafe” characters which can be hard to properly include in shell scripts makefiles. Check that ls ...


12

Gentoo is a Linux distribution that compiles packages from sources. Compiling packages requires much more space that installing pre-compiled binaries (that is, binaries that are compiled on the machines of the distribution maintainers). When you install something from the sources, you also need the sources for all the compilation dependencies. Almost all ...


0

This sounds like a permissions problem. Either user permissions (chmod or acl), MAC (Mandatory Access Control, often selinux or similar) or filesystem write permissions. I think it is probably the third in that your container is not able to write to the device.


0

netinet is currently not a kernel module, so i suggest to add your modified file to sys/conf/files instead.


2

For compiling kernel module you should create Makefile and to include kernel module makefile /usr/src/share/mk/bsd.kmod.mk for example: # Note: It is important to make sure you include the <bsd.kmod.mk> makefile after declaring the KMOD and SRCS variables. # Declare Name of kernel module KMOD = module # Enumerate Source files for kernel module ...


0

Check to see if there's a /proc/config.gz on the banana when the system is running (it will not be there if it is not). Most likely it does exist. Copy that into the top level of the source tree and: make clean gunzip -c config.gz > .config make oldconfig Then try building the module again.


1

If these are external modules, try building against the kernel first, then install using modules_install as described below. Make sure you are building in the path to your kernel source. From https://www.kernel.org/doc/Documentation/kbuild/modules.txt --- 2.1 Command Syntax The command to build an external module is: $ make -C ...


0

After extensive debugging I found out that mounting a folder on my host system at /root/buildroot/output/ causes the problem. Remove this mount and make linux-menuconfig is possible. Further debugging revealed that mounting a host folder at /root/buildroot/output/build in the container is the problem. I've no clue why.


3

It's all about risk mitigation; if make does something destructive, you can only lose whatever data was modifiable (or deletable) by the user running it. So you run make as a plain user to limit the scope to that user's files, and you run make install as root because you have to if you want to install to /usr/local typically. Note that in the example you ...


2

It comes down to trust vs convenience. True, make might be insecure, but then so might make install. It's just that the surface attack area should (hopefully) be smaller for make install, and it's more likely a quick perusal of the Makefile will spot anything strange. However, installing software into the $PATH is risky regardless of who has compiled it, so ...


1

There isn't anywhere special the source code needs to be. Normally it'd be wherever your repository is. If you want to leave it somewhere for the next admin to find, the most obvious place would be a company VCS server. /usr/src would also be a reasonable place to look, as well as $HOME. Eventually, if you decide to submit the module for inclusion in the ...


4

You can use the make targets delete-old and delete-old-libs to remove obsolete files. They run interactively, unless you set BATCH_DELETE_OLD_FILES: # pwd /usr/src # make -DBATCH_DELETE_OLD_FILES delete-old Run them after make installworld. Have a look at build(7) for more details. A word of warning - be careful with delete-old-libs - it will delete ...


0

If you can go with full kernel source tree, here are the steps I have followed in order to compile and install a driver on the source tree: Lets say you have the kernel sources extracted at /sources/linux-3.19 cd /sources/linux-3.19 make mrproper make menuconfig Here make sure to select your driver with "m" label. For instance, if you select to build ...


0

Programs do not search for libraries in the same directory as the executable by default. The traditional directory organization under Unix has executables in directories called …/bin and libraries in directories called …/lib. if you set prefix=~/.local when compiling software, you'll end up installing the executables in ~/.local/bin and the libraries in ...


1

What is your distribution? Does your distribution have rtmpdump available as a binary package? Debian does, for example, and therefore Ubuntu and Mint should as well, for example. If so, why aren't you using it? In any case, apt-file search librtmp.so librtmp-dev: /usr/lib/x86_64-linux-gnu/librtmp.so librtmp0: /usr/lib/x86_64-linux-gnu/librtmp.so.0 ...


2

In general it should be possible, if both hosts really have the same specifications (i.e. same processor architecture, same libraries in same versions installed, same kernel installed, same file system structure for referred config files/libraries, ...). But since you can do nasty things in Makefiles there might be situations where this is not possible. The ...


0

On a current CentOS 7 minimal install you need: sudo yum install gcc kernel-devel-$(uname -r)


3

At the stage where you have a directory tree containing a file …/etc/shadow (before building the filesystem image), modify that file to inject the password hash(es) that you want to have. The easiest way to do that is with recent enough versions of the chpasswd tool from the Linux shadow utilities suite (Debian wheezy is recent enough) with the -R option. ...


2

I thought I would add a better answer for anyone else observing this thread. So, if you've already gone through the trouble of building opencv on the device, you've probably followed the instructions here: http://docs.opencv.org/doc/tutorials/introduction/linux_install/linux_install.html In which case, if you don't add the -D args to dynamically override ...


0

Try to add compiler flags to configure script, so that they are propagated to all Makefile files. ./configure CFLAGS="-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include" CXXFLAGS="-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include" LDFLAGS="-lglib-2.0 -lintl -lpcre -lintl -liconv -lpcre"



Top 50 recent answers are included