Tag Info

Hot answers tagged

4

The test is done by compiling a small dummy C program and by checking how the compiler names the output file. The following example is a simplified version of what configure is doing #!/bin/sh cat << EOT > dummy.c int main(int argc, char ** argv) { return 0; } EOT gcc -o dummy dummy.c if [ -f dummy.exe ] ; then # exe fi I would suggest ...


2

I want to add these file into my kernel such way that when kernel start this hello.o file execute and run What you are trying to achieve shouldn't be made through kernel edition. Executing a program at boot time can be handled in much simpler ways, without need for kernel programming experience. You can: Execute it when your shell starts: Write ...


2

I have a few ways to do this, easy ones first: Making the install prefix flexible is hard - I would just make the install prefix to your home directory, or somewhere that you can access on any of the machines, and use make install DESTDIR=/path/to/place/where/binaries/should/be/installed to install them to somewhere other than the prefix. I personally have ...


2

From the output you've given, you are trying to compile a 32-bit build of apache on a 64 bit system. This is from the intput to configure here: --host=x86_32-unknown-linux-gnu host_alias=x86_32-unknown-linux-gnu CFLAGS=-m32 LDFLAGS=-m32 Also see the output lines confirming this: configure:3629: checking build system type configure:3643: result: ...


2

You need to verify $PATH and $LD_LIBRARY_PATH environment variables. make sure they are point to correct version of ffmpeg and does not include older version if LD_LIBRARY_PATH is not already setup then try this : LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib ffmpeg


1

Despite what file says, it turns out to be debugging symbols after all. A thread about this on the LKML led me to try: make INSTALL_MOD_STRIP=1 modules_install And low and behold, a comparison from within the /lib/modules/x.x.x directory; before: > ls -hs kernel/crypto/anubis.ko 112K kernel/crypto/anubis.ko And after: > ls -hs ...


1

The issue is that one of the kernel headers / interfaces changed in a recent 3.x kernel. Where a UID / GID values were originally referred to as regular integers, they are now structs with a single element. Any code relying on the older definition now will fail to compile until updated to match the new kernel headers. I'm currently experimenting with ...


1

PHP extensions can be compiled statically or shared. Static compilation puts the extension directly into PHP (therefore it does not need to be loaded and cannot be unloaded). When using shared compilation --enable-calendar=shared that will create file calendar.so. You can enable or disable it by editing php.ini.


1

In addition to the patches listed here you need to patch link.c from vmhgfs.tar. 184a185 > #if LINUX_VERSION_CODE <= KERNEL_VERSION(3, 14, 99) 187a189,194 > #else > LOG(6, (KERN_DEBUG "VMware hgfs: HgfsReadlink: calling " > "readlink_copy\n")); > error = readlink_copy(buffer, buflen, fileName); > ...


1

Stuff in /usr/local usually supersedes stuff in /usr, so I'm a bit confused as to why you would install libraries there to have a "a nice custom distro", but then not want to compile against them. Those are the libraries the system will use actually use. Anyway, man pkg-config claims the base search path: is libdir/pkgconfig:datadir/pkgconfig where ...


1

Or should I simply ignore it? Unused variables could be an indication of a coding mistake. If you are satisfied this is not the case and want to suppress the warning for a particular variable, you can use a (GCC specific) __attribute__ tag, e.g.: /* Unused parameter (in definition, not declaration): */ void somefunc (int x __attribute__ ((unused))) { ...


1

"Variable set but not used" warnings are informational. According to the official documentation, -Wunused-but-set-variable controls the behavior of: Warn[ing] whenever a local variable is assigned to, but otherwise unused (aside from its declaration). This warning is enabled by -Wall. The purpose is to catch situations where the programmer assigns a ...


1

In general, ./configure && make && make install without any parameters sticks everything under /usr/local, which would place foo.pc in /usr/local/lib/pkgconfig/foo.pc To make use of this, you'd need to do basically PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:${PKG_CONFIG_PATH} pkg-config --cflags foo, or, compile in this manner: ./configure ...



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