compile fails in linux ... "No rule to make target" ... HELP
hello all,
attached you can find a tool (written in C) that i really need to make it compile under linux
i am able to compile and run it successfully in mac os x, but in linux the compilation fails
the only thing that i did so far is to change the following
#include <sys/malloc.h> to <malloc.h>
but still the compilation fails :
"No rule to make target"
i would appreciate any suggestions on how i can overcome this
thank you
I need to take a string (stringA) check it for spaces and replace any spaces found with an equal (=) sign.
This is not working. There are spaces between each component:
$StringA | tr "" ""
The error returned is:
test: Specify a parameter with this command
Can you help? (3 Replies)
Hi,
I tried native compile Linux dialog for Linux embedded device
and got "curses.h" error message.
As Linux dialog is already compiled and working as Debian .deb package (installed it).
What is a way to import curses.h from other package sources to work for dialog sources compilation in my... (2 Replies)
This is the script:
#!/bin/sh
if ; then rm -rf /usr/share/WallpaperChanger; fi
if ; then rm -rf /usr/bin/wallch; fi;
if ; then rm -rf /usr/share/applications/wallch.desktop; fi
if ; then rm -rf /usr/share/doc/wallch; fi
if ; then rm -rf /usr/share/man/man1/wallch.1.gz; fi
echo "Delete... (4 Replies)
I have been trying to split up my src directory to clear out files that are not re-compiled very often. Now I have the following setup in my trunk,
trunk/bld
trunk/src/
trunk/src/src_server
trunk/makefile.linux
In the make file, I have compile rules
SOURCELOC = src
# compile src c++... (4 Replies)
i am compiling a program called vasp on suse and get the following error. there are many more preprocess and ifort commands prior so i just grabbed the tail of the log file:
./preprocess <main.F | /usr/bin/cpp -P -C -traditional >main.f90 -DMPI -DHOST=\"LinuxIFC\" -DIFC -Dkind8 -DNGZhalf... (6 Replies)
i may be asking way too much here but i am not a programmer and not sure where to to turn. i have a program that i am trying to "make". but the compiler i am supposed to use gets nowhere. there are a bunch of .f90 files that are being processed as follows but it doesn't get past the first one:
... (1 Reply)
Hi gud day,
I would like to ask if possible to load the driver i compiled module without installing it in the ubuntu-kernel-distro/updates* or simple not executing "make install". what i mean is i compile the compat wireless driver using make and i want to try to load
on the system without... (1 Reply)
Discussion started by: jao_madn
1 Replies
LEARN ABOUT HPUX
subdomain.conf
SUBDOMAIN.CONF(5) AppArmor SUBDOMAIN.CONF(5)NAME
/etc/apparmor/subdomain.conf - configuration file for fine-tuning the behavior of the AppArmor security tool.
DESCRIPTION
The AppArmor security tool can be configured to have certain default behaviors based on configuration options set in subdomain.conf. There
are two variables that can be set in subdomain.conf: SUBDOMAIN_PATH, and SUBDOMAIN_MODULE_PANIC.
SUBDOMAIN_PATH
This variable accepts a string (path), and is by default set to '/etc/apparmor.d/' This variable defines where the AppArmor security tool
looks for its policy definitions (a.k.a. AppArmor profiles).
SUBDOMAIN_MODULE_PANIC
This variable accepts a string that is one of four values: warn, build, panic, or build-panic, and is set by default to warn.
This setting controls the behavior of the AppArmor initscript if it cannot successfully load the AppArmor kernel module on startup. The
four possible settings are:
warn
Log a failure message (the default behavior).
build
Attempt to build the AppArmor module against the currently running kernel. If the compilation is successful, the module will be loaded
and AppArmor started; if the compilation fails, a failure message is logged.
panic
Log a failure message and drop to runlevel 1 (single user).
build-panic
Attempt to build the module against the running kernel (like build) and if the compilation fails, drop to runlevel 1 (single user).
BUGS
Setting the initscript to recompile the module will fail on SUSE, as the module source is no longer installed by default. However, the
module has been included with the SUSE kernel, so no rebuilding should be necessary.
If you find any additional bugs, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>.
SEE ALSO apparmor(7), apparmor_parser(8), and <http://wiki.apparmor.net>.
AppArmor 2.7.103 2012-06-28 SUBDOMAIN.CONF(5)