10-16-2014
I think you are quoting a little too aggressively. Try ${INCL} instead of "${INCL}" to let it split on spaces instead of cramming it into lint as one giant argument.
To see the difference, try printf "%s\n" "${INCL}" vs printf "%s\n" ${INCL}
10 More Discussions You Might Find Interesting
1. Programming
how can i check my code with lint? What if the code containes multiple module? The check is been done on each module separately?
What is the command to use the lint
Any relevant site???
Thanks a lot. You are doing a great job.:cool: (2 Replies)
Discussion started by: amatsaka
2 Replies
2. UNIX for Dummies Questions & Answers
Can Any One let me know abut the use on "lint" in UNIX...... (1 Reply)
Discussion started by: kumar_saurabh
1 Replies
3. Programming
Hi
can anyone help me regarding the meaning of the following lint messages.
what is the use of having such lint comments in the c program.
/*lint -esym(534,cputs,fgets,cprintf) */
/*lint -efile(766,pragmas.h) */
Thanks a lot in advance. (5 Replies)
Discussion started by: axes
5 Replies
4. Shell Programming and Scripting
I often find myself running lint in the following fashion:
lint -Idir-1 ... -Idir-n some-src.c
where a number of -Idirs should be coming from the make file.
Here is example:
$ cd dir1
$ grep ^CF makefile
CFLAGS = -g -I ../ver1/include
$ lint -I ../ver1/include sr1.c
... (0 Replies)
Discussion started by: migurus
0 Replies
5. AIX
Hi ,
I Want to apply AIX lint to my source code which all are *.cpp/*.h
>lint test.cpp
lint: 1286-332 File test.cpp must have a .c, .C or .ln extension. It is ignored.
lint: 1286-334 There are no files to process.
I am getting above error.
-Ashok (3 Replies)
Discussion started by: ashokd001
3 Replies
6. High Performance Computing
Hi, I have a difficulty running mpirun on my workstation, RHEL 4.
I have uninstalled lam-7.1.4 with 'rpm -e lam-7.1.4'. No problem.
The I downloaded openmpi-1.3.tar.gz. unzipped as normal. No problem.
Then did 'make clean'. Then './configure'. No problems.
Then I did 'make' and then 'make... (1 Reply)
Discussion started by: The_Watcher
1 Replies
7. UNIX for Dummies Questions & Answers
Hey all,
I'm trying to execute a program and despite it appearing to be there, I keep getting this:
-bash: ./aisdispatcher: No such file or directoryTo run it, I'm going into the directory where it is stored and running
./aisdispatcher...the result of which should just be a listing of options... (10 Replies)
Discussion started by: pmd006
10 Replies
8. Shell Programming and Scripting
Hi all,
Running follow command on terminal;
$ glance -T cloudlive -I ubuntu -K ubuntu123 -N \
http://127.0.0.1:5000/v2.0/OpenX add name="cirros" is_public=true \
container_format=ovf disk_format=raw < \
/srv/cirros-0.3.0-x86_64-disk.img
It works without problem.
Putting it on a... (5 Replies)
Discussion started by: satimis
5 Replies
9. UNIX for Advanced & Expert Users
Hi All,
Can any one help me in how to run "lint command " on .c files to list all functions with wrong return value in hp unix.
Thanks in Advance. (1 Reply)
Discussion started by: jhon1257
1 Replies
10. Shell Programming and Scripting
the thread is deleted (1 Reply)
Discussion started by: jhon1257
1 Replies
tee(1) General Commands Manual tee(1)
NAME
tee - Displays the output of a program and copies it into a file
SYNOPSIS
tee [-ai] file...
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
tee: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Adds the output to the end of file instead of writing over it. Ignores the SIGINT signal.
OPERANDS
Standard input is stored into, or appended to, the file specified.
[Tru64 UNIX] The tee command can accept up to 20 file arguments.
DESCRIPTION
The tee command reads standard input and writes to both standard output, and each specified file.
The tee command is useful when you wish to view program output as it is displayed, and also want to save it in a file. The tee command does
not buffer output, so you may wish to pipe the output of tee to more if more than one full screen of data is anticipated.
NOTES
If a write to any file fails, the exit status of tee will be non-zero. Writes to all other specified files may be successful, and opera-
tion will continue until standard input is exhausted.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
EXAMPLES
To view and save the output from a command at the same time, enter: lint program.c | tee program.lint
This displays the standard output of the command lint program.c at the terminal, and at the same time saves a copy of it in the file
program.lint. If program.lint already exists, it is deleted and replaced. To display and append to a file, enter: lint program.c |
tee -a program.lint
This displays the standard output of lint program.c at the terminal and at the same time appends a copy of it to the end of pro-
gram.lint. If the file program.lint does not exist, it is created.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of tee: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for-
mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of
LC_MESSAGES.
SEE ALSO
Commands: cat(1), echo(1), script(1)
Standards: standards(5)
tee(1)