Sponsored Content
Special Forums UNIX Desktop Questions & Answers line 3: syntax error near unexpected token `(' Post 302241081 by jim mcnamara on Sunday 28th of September 2008 08:56:48 AM
Old 09-28-2008
Franklin -

Some wierd compilers expect two arguments to main. It also could be a shell error, like you think.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Syntax error near unexpected token `('

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

syntax error near unexpected token '{

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

Syntax error near unexpected token

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

Syntax error near unexpected token `}' please help

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

Cannot execute/finish script because of last line syntax error: unexpected end of file/token `done'

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

Syntax error near unexpected token '('

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

Syntax error near unexpected token

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

Syntax error near unexpected token `else'

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

Syntax error near unexpected token `('

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

Sh: -c: line 0: syntax error near unexpected token `(' how to resolve this

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
mpicxx(1)							     Open MPI								 mpicxx(1)

NAME
mpicxx -- Open MPI C++ wrapper compiler SYNTAX
mpicxx [-showme|-showme:compile|-showme:link] ... OPTIONS
-showme Do not invoke the underlying compiler. Instead, show the command line that would be executed to compile the program. NOTE: If a non-filename argument is passed on the command line, the -showme option will not display any additional flags. For example, both "mpicxx --showme" and "mpicxx --showme my_source.c" will show all the wrapper-supplied flags. But "mpicxx -showme -v" will only show the underlying compiler name and "-v". -showme:compile Do not invoke the underlying C++ compiler. Instead, show the compiler flags that would be supplied to the C++ compiler. -showme:link Do not invoke the underlying C++ compiler. Instead, show the linker flags that would be supplied to the C++ compiler. See the man page for your underlying compiler for other options that can be passed through mpicxx DESCRIPTION
Conceptually, the role of these commands is quite simple: transparently add relevant compiler and linker flags to the user's command line that are necessary to compile / link Open MPI programs, and then invoke the underlying compiler to actually perform the command. As such, these commands are frequently referred to as "wrapper" compilers because they do not actually compile or link applications them- selves; they only add in command line flags and invoke the back-end compiler. Background Open MPI is comprised of three software layers: OPAL (Open Portable Access Layer), ORTE (Open Run-Time Environment), and OMPI (Open MPI). There are wrapper compilers for each layer; each layer's wrapper only links in the libraries relevant for that layer. Specifically, each layer provides the following wrapper compilers: OPAL opalcc and opalc++ ORTE ortecc and ortec++ OMPI mpicc, mpic++, mpicxx, mpiCC (only on systems with case-senstive file systems), mpif77, and mpif90. Note that mpic++, mpicxx, and mpiCC all invoke the same underlying C++ compiler with the same options. All are provided as compatibility with other MPI implementa- tions. The Fortran wrapper compilers for MPI (mpif77 and mpif90) will be inoperative and will return an error on use if Fortran 77 / Fortran 90 support was not built into the MPI layer. Overview mpicxx is a convenience wrappers for the underlying C++ compiler. Translation of an Open MPI program requires the linkage of the Open MPI- specific libraries which may not reside in one of the standard search directories of ld(1). It also often requires the inclusion of header files what may also not be found in a standard location. mpicxx passes its arguments to the underlying C++ compiler along with the -I, -L and -l options required by Open MPI programs. The Open MPI Team strongly encourages using the wrapper compilers instead of attempting to link to the Open MPI libraries manually. This allows the specific implementation of Open MPI to change without forcing changes to linker directives in users' Makefiles. Indeed, the specific set of flags and libraries used by the wrapper compilers depends on how Open MPI was configured and built; the values can change between different installations of the same version of Open MPI. Indeed, since the wrappers are simply thin shells on top of an underlying compiler, there are very, very few compelling reasons not to use mpicxx. When it is not possible to use the wrappers directly, the -showme:compile and -showme:link options should be used to determine what flags the wrappers would have used. For example: shell$ cc -c file1.c `mpicc -showme:compile` shell$ cc -c file2.c `mpicc -showme:compile` shell$ cc file1.o file2.o `mpicc -showme:link` -o my_mpi_program NOTES
It is possible to make the wrapper compilers multi-lib aware. That is, the libraries and includes specified may differ based on the com- piler flags specified (for example, with the GNU compilers on Linux, a different library path may be used if -m32 is seen versus -m64 being seen). This is not the default behavior in a standard build, but can be activated (for example, in a binary package providing both 32 and 64 bit support). More information can be found at: https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264 FILES
The string that the wrapper compilers insert into the command line before invoking the underlying compiler are stored in a text file cre- ated by Open MPI and installed to $pkgdata/mpicxx-wrapper-data.txt, where $pkgdata is typically $prefix/share/openmpi, and $prefix is the top installation directory of Open MPI. It is rarely necessary to edit this file, but it can be examined to gain insight into what flags the wrappers are placing on the command line. ENVIRONMENT VARIABLES
By default, the wrappers use the compilers that were selected when Open MPI was configured. These compilers were either found automati- cally by Open MPI's "configure" script, or were selected by the user in the CC, CXX, F77, and/or FC environment variables before "config- ure" was invoked. Additionally, other arguments specific to the compiler may have been selected by configure. These values can be selectively overridden by either editing the text files containing this configuration information (see the FILES sec- tion), or by setting selected environment variables of the form "OMPI_value". Valid value names are: CPPFLAGS Flags added when invoking the preprocessor (C or C++) LDFLAGS Flags added when invoking the linker (C, C++, or Fortran) LIBS Libraries added when invoking the linker (C, C++, or Fortran) CC C compiler CFLAGS C compiler flags CXX C++ compiler CXXFLAGS C++ compiler flags F77 Fortran 77 compiler FFLAGS Fortran 77 compiler flags FC Fortran 90 compiler FCFLAGS Fortran 90 compiler flags 1.4.5 Feb 10, 2012 mpicxx(1)
All times are GMT -4. The time now is 06:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy