09-29-2008
Resolved
Many thanks to all those who replied, it actually worked by using, as advised cc hello.c -o hello and then running ./hello the book says to type gcc -g -o hello hello.c. Once again thank you.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Guys ,
This is an output of my script errored out for "Syntax error near unexpected token `(' " Can someone tell me whats wrong with my script.
Below is my original script pasted.
#!/bin/bash
Script Creation Date 01/21/2010
Author baraghun
... (7 Replies)
Discussion started by: raghunsi
7 Replies
2. UNIX for Advanced & Expert Users
Hi,
I am running the following script through cygwin and getting below mentioned error.
*******************************************
#!/bin/sh
# constants
WORK_DIR="deploy"
INFOFILE="deploy.info"
INTROFILE="Intro.sh"
CMGMT_PKG="com.kintana.cmgmt.deploy"
DEPLOY_PREFIX="mitg"
... (2 Replies)
Discussion started by: MandyR
2 Replies
3. UNIX for Dummies Questions & Answers
hi! just want to seek help on this error: syntax error near unexpected token 'do
this is my script
# !/bin/sh
#
for y in 27 25
do
exemmlmx -c "ZEEI;" -n XRT$y >> blah
done
what can be wrong? thanks! (6 Replies)
Discussion started by: engr.jay
6 Replies
4. Shell Programming and Scripting
I'm going mad not being able to get this to work. im assuming its only a simple mistake but its driving me bonkers trying to find it.
Please if you can help me it would save me pulling my hair out!!
Thanks
#!/bin/bash -xv
#
#Config
name="TEST Server"
+ name='TEST Server'... (6 Replies)
Discussion started by: Fisheh
6 Replies
5. Shell Programming and Scripting
first of all I thought the argument DONE is necessary for all scripts that have or begin with do statements which I have on my script, However, I still don't completely understand why I am receiving an error I tried adding another done argument statement but didn't do any good.
I appreciate... (3 Replies)
Discussion started by: wolf@=NK
3 Replies
6. Shell Programming and Scripting
I tried to execute the code but I got this error
./Array.c: line 9: syntax error near unexpected token '('
./Array.c: line 9: ' nvals = get_data(a,MAXARRAY);'
and
#include<stdio.h>
#define MAXARRAY 1000
main()
{
int a,
nvals;
nvals =... (7 Replies)
Discussion started by: sgradywhite
7 Replies
7. Shell Programming and Scripting
Hi all,
I have a simple script that doesn't work somehow. I can't seem to be spotting the cause of the malfunction.
count=$((1))
for item in `cat test1.txt`
printf %s `sed -n $((count))p test2.txt` > test3.txt
count=$((count+1))
do
something
done
I get ;
./why.sh: line 3:... (14 Replies)
Discussion started by: y33t
14 Replies
8. Shell Programming and Scripting
Hello every one!!
I don't know where I am going wrong but I am finding it difficult to clear this error of syntax error near unexpected token `else'
I am writing a simple shell script to find a file in a directory and if found execute that else return an error to the log file
... (14 Replies)
Discussion started by: masubram
14 Replies
9. How to Post in the The UNIX and Linux Forums
I have 2 files like a.txt and b.txt and the content is as below
cat a.txt
810750125 117780 /BSCSQAT4A/bscsqat4a/lib/jar/wclt_common.jar
1803152428 13300 /BSCSQAT4A/bscsqat4a/lib/jar/WFMSSupportTool.jar
2663502779 67049 /BSCSQAT4A/bscsqat4a/lib/jar/wma.jar
687942896 665272... (1 Reply)
Discussion started by: ranabhavish
1 Replies
10. Programming
Below query is not working for me. Please help me on this
DATA EXCLUDE STATEMENT: TABLE:\"LIKE \'%\_HISTORY\'\", TABLE:\"LIKE \'%\_HIST\'\", TABLE:\"in \(select tname from tab where REGEXP_LIKE(TNAME,\'\_H$\'\))\", TABLE:\"LIKE \'%\_LOG\'\", TABLE:\"LIKE \'DW\_%\'\", TABLE:\"LIKE... (1 Reply)
Discussion started by: princy
1 Replies
LEARN ABOUT FREEBSD
introduction
INTRO(1) BSD General Commands Manual INTRO(1)
NAME
intro -- introduction to general commands (tools and utilities)
DESCRIPTION
Section one of the manual contains most of the commands which comprise the BSD user environment. Some of the commands included in section
one are text editors, command shell interpreters, searching and sorting tools, file manipulation commands, system status commands, remote
file copy commands, mail commands, compilers and compiler tools, formatted output tools, and line printer commands.
All commands set a status value upon exit which may be tested to see if the command completed normally. Traditionally, the value 0 signifies
successful completion of the command, while a value >0 indicates an error. Some commands attempt to describe the nature of the failure by
using exit codes as defined in sysexits(3), while others simply set the status to an arbitrary value >0 (typically 1).
SEE ALSO
apropos(1), man(1), intro(2), intro(3), sysexits(3), intro(4), intro(5), intro(6), intro(7), security(7), intro(8), intro(9)
Tutorials in the UNIX User's Manual Supplementary Documents.
HISTORY
The intro manual page appeared in Version 6 AT&T UNIX.
BSD
October 21, 2001 BSD