02-26-2014
Script is a command that keeps a log of commands int a file but not the source code compilation output .
Thank you blackrageous ,Akshay Hegde, Corona688 for all your help .
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I'm wondering if anyone out there have experience using the SCCS source code in Unix? If so, can you recommend a good (user friendly) SCCS book for beginner users.
Thanks! (3 Replies)
Discussion started by: Mary
3 Replies
2. Linux
Hello Everyone,
I've been programming using C for somtime, and now I want to involve myself in Linux OS. I've decided to study the details of the Fedora code,but I don't know where I can download it.Any suggestions as how to study the code and about X window are also helpful.
Thanks in advance. (3 Replies)
Discussion started by: enoch99
3 Replies
3. HP-UX
Hello everyone,
Today we are attempting to port some legacy C code to a 64 HP-UX machine at my company and there is kind of a strange error we ran into.
there is a small function they have defined called zgetenv that
accepts a char* and basically just does some null checking and returns ... (0 Replies)
Discussion started by: khadesh
0 Replies
4. Programming
Hi all,
I implemented an application, through using c++ and compiled it with g++.
At first, what I did is (@ compilation):
g++ calcBacon.C -o test -DDEBUG
after I ran my application it took almost 120 sec. to finish its execution
when I compiled with optimization parameters, execution... (5 Replies)
Discussion started by: SaTYR
5 Replies
5. Programming
(gdb) r --------------------- enter
Breakpoint 1, 0x0000000000409d40 in main ()
(gdb) n
Single stepping until exit from function main,
which has no line number information.
Find_Cmd_Option: found option no. 2: seed (s)
Find_Cmd_Option: found option no. 5: dfile (c)
Initial no. div... (1 Reply)
Discussion started by: cdbug
1 Replies
6. Programming
I'm running a query similar to the one that I'm describing below -:
_______________________________
EXEC SQL INSERT INTO TABLE1
( C1
,C2
,C3
,C4 )
(SELECT DISTINCT B.V1
,B.V2
,( SELECT D.V3 FROM TABLE2 D WHERE D.V3 = C.V4)
,B.V4
FROM TABLE2 B ,TABLE3 C
WHERE B.V3 = C.V4) ;... (1 Reply)
Discussion started by: maheshp
1 Replies
7. Shell Programming and Scripting
Hi,
I want to remove the following code from Source files (or replace the code with empty.) from all the source files in given directory.
finally {
if (null != hibernateSession && hibernateSession.isOpen()) {
//hibernateSession.close();
}
}
It would be great if the script has... (2 Replies)
Discussion started by: hareeshram
2 Replies
8. Linux
I need the source code of fedora.
plz plz plz help me........... (1 Reply)
Discussion started by: neh
1 Replies
9. UNIX for Dummies Questions & Answers
hii...
i am a biginner....and i have linux source code ,downloaded from some website ,a compressed file on windows and dont know how do compile them..... (4 Replies)
Discussion started by: M K Raju
4 Replies
LEARN ABOUT DEBIAN
rubber-info
RUBBER-INFO(1) General Commands Manual RUBBER-INFO(1)
NAME
rubber-info - extract information from LaTeX documents
SYNOPSIS
rubber-info [options] [action] source
DESCRIPTION
Rubber-info is a utility for extracting various kinds of information from a LaTeX document. Information can be extracted from the source
(for instance when calculating dependencies) or from the compilation log files (to extract errors and warnings). This program is a comple-
ment for the compilation system rubber(1).
The command-line options are those used by rubber(1) plus one of the actions described below.
ACTIONS
One of the following command-line options must be specified, to decide which information to extract. Of course, for actions that read a log
file, a compilation must have been done before. If none of these actions is specified, --check is assumed.
--boxes
Extracts from the log file the places in the source where bad boxes appeared (these are the famous overfull and underfull hbox and
vbox)
--check
Report errors if there are any, otherwise report undefined references if there are any, otherwise list warnings and bad boxes. This
is the default action.
--deps Analyse the source files and produce a space-separated list of all the files that the document depends on and that Rubber cannot
rebuild.
--errors
Extract from the log file the list of errors that occured during the last compilation.
-h, --help
Display the list of all available options and exit nicely.
--refs Report the list of undefined or multiply defined references (i.e. the
ef's that are not defined by one label).
--rules
Analyse the source files and produce a list of dependency rules. One rule is produced for each intermediate target that would be
made when running rubber. Rules are formatted in the style of Makefiles.
--version
Print the version number and exit nicely.
--warnings
Stupidly enumerate all LaTeX warnings, i.e. all the lines in the log file that contain the string "Warning".
BUGS
There are surely a some...
This page documents Rubber version 1.1. The program and this man-page are maintained by Emmanuel Beffara <manu@beffara.org>. The homepage
for Rubber can be found at http://www.pps.jussieu.fr/~beffara/soft/rubber/.
SEE ALSO
The full documentation for rubber is maintained as a Texinfo manual. If the info and rubber programs are properly installed at your site,
the command
info rubber
should give you access to the complete manual.
RUBBER-INFO(1)