Hi mates,
I am trying to copile and link to C programs with command:
cc file1,file2
but i raises the error "file not found" ... am i doing the right way?
any suggestion will be appreciated.
thanks
abdul (4 Replies)
Hi
I'm getting
ld: fatal: option -h and building a dynamic executable are incompatible
ld: fatal: Flags processing errors
When I run
ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o
after running
gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c
I'm... (6 Replies)
hi,
This is the first time I work in a big C project. All source code files are located in say directory /source/pp and all header files are in /include/pp. I've created a link to both of these directories from my home dir, say /home/ss. So in the /home/ss dir I have the /source/pp and /include/pp... (1 Reply)
Hello,
Can anyone tell me how I can make a file link or shortcut in UNIX 4.0, several
file links where damaged during an outage examples below.
Examples: file -> file
libX11.so -> /usr/shlib/libX11.so.pre.O3D
All of the file links that were damaged were in /shlib and point to... (3 Replies)
Dear friends,
First off all , let me apologize for my inexperience. I am just starting use of Linux and gcc .
Actually I ve some .c files in the present directory , and now I am
giving
+vc <my_file1.c> <my.file2.c> <myfile3.c>.
All the c files are in present directory.... (2 Replies)
I have a directory containing a series of files of the format:
A2008001231000.L2
I only care about the 6-8 digits, so the files are effectively:
?????---*.L2
I have files that range from ?????001*.L2 to ?????366*.L2
It should be noted these three digits represent the julian day of the... (2 Replies)
Hi,
I have d1,d2,d3 directories
/
/home/abc/d1
/home/abc/d2
/home/abc/d3
d1,d2 and d3 also have subdirctories.
d1-->d11-->d12
d2-->d22-->d23
d3-->d33-->d34
All these directories have files like date_filename.txt
so I want to find the files recusively for a particular date from... (1 Reply)
I would like to transfer all files ending with .log from /tmp and to /tmp/archive (using find )
The directory structure looks like :-
/tmp
a.log
b.log
c.log
/abcd
d.log
e.log
When I tried the following command , it movies all the log files... (8 Replies)
I have 2 txt files, 1.txt and 2.txt which contain the paths to files that need to be linked.
Example 1.txt:
/root/001/folder2/image4.nii.gz
/root/002/folder2/image4.nii.gz
Example 2.txt:
/root/001/folder2/image5.nii.gz
/root/002/folder2/image5.nii.gz
Each line represents images from... (7 Replies)
Basically my problem is that when I try to compile anything using ./configure && make, it fails because of linker errors. I can reproduce the behavior I'm getting as follows:
I have the two following files
main.c:
#include <stdio.h>
extern void func(void);
int
main(int argc, char... (5 Replies)
Discussion started by: MarshallBanana
5 Replies
LEARN ABOUT REDHAT
makekdedoc
MAKEKDEDOC(1) KDOC Documentation System MAKEKDEDOC(1)NAME
makekdedoc -- Generates HTML documentation for KDE libraries using KDOC.
SYNOPSIS
makekdedoc [--rule-file=<rulefile>] [--libdir=<libdir>]
[--outputdir=<outputdir>] [--url=<url>]
[--srcdir=<kdelibs src dir>]
[--kdoc=<path to kdoc>] [<library>...]
makekdedoc --help
DESCRIPTION
This is a perl script that uses KDOC to generate documentation for kdelibs. A "rule" file is used to figure out the libraries to document,
the order in which to document them and the libraries with which each one will be cross-referenced (eg kdeui uses -lkdecore). See "FILES"
for more info.
NOTE: The script assumes that you have already generated a Qt cross-reference using qt2kdoc[1].
OPTIONS
Defaults for each option are in square brackets.
library...
Specify the libraries to document. By default, all libraries defined by the rule file are documented.
--outputdir <path>, -d <path>
The directory where the output will be written. [`cwd`/srcdoc]
--url <url>, -u <url>
The base URL by which the generated docs will be accessed. For example, if your web server is configured to use $HOME/public_html for
your home page, you could set the outputdir to $HOME/public_html/srcdoc and the url to http://myhost/~mylogin/srcdoc. [output dir]
--rule-file <path>, -r <path>
The path to the rule file to use for generating the documentation. [<srcdir>/kdoc.rules]
--libdir <path>, -L <path>
The directory in which the KDOC cross-reference files are stored. [$KDOCLIBS if set, otherwise $HOME/.kdoc]
--kdoc <path>, -k <path>
The path to the kdoc program. [kdoc]
--kdocopt <options>, -p <options>
Extra options to be passed to kdoc.
--srcdir <path>, -b <path>
The path to the kdelibs source, eg "$HOME/baseline/kdelibs". [`cwd`]
--help, -h
Quit with a usage message.
EXAMPLES
makekdedoc --srcdir $HOME/baseline/kdelibs
--outputdir $HOME/public_html/src/kdelibs/
--url "http://www.ph.unimelb.edu.au/~ssk/src/kdelibs"
FILES
Rule file
This file lists the directories in the source directory to document. It also lists the files to document from each directory, and the
libraries with which to cross-reference the generated documentation. Here is a small example that documents two libraries and links the
second to the first.
# makekdedoc rule file
doc_MODULES = eenie meenie
# rules for eenie
eenie_FILES = *.h
eenie_LIBS = -lqt
# rules for meenie
meenie_FILES = a.h b.h
meenie_LIBS = -leenie -lqt
In this example, all files in "eenie/*.h" will be documented then two files from "meenie/" will be documented, in the order declared in
"doc_MODULES".
SEE ALSO
See kdoc[1] and qt2kdoc[1].
VERSION
makekdedoc $Revision: 1.2 $
AUTHOR
The script and this documentation were written by Sirtaj Singh Kang <taj@kde.org> in April 1999.
2.0a54 2000-10-10 MAKEKDEDOC(1)