Sponsored Content
Operating Systems Solaris expected identifier before numeric constant Post 302490990 by jim mcnamara on Wednesday 26th of January 2011 10:48:46 AM
Old 01-26-2011
As a general comment - this kind of problem usually arises because .h (include files)
code uses "guard" define statments so that just the correct statements are actually included by cpp. So, I would guess that one of those define statements is at fault.

The configure utility usually sets these values correctly for you.

And there really is no way for us to "look" at it since the build is particular to your system.
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Perl code to differentiate numeric and non-numeric input

Hi All, Is there any code in Perl which can differentiate between numeric and non-numeric input? (11 Replies)
Discussion started by: Raynon
11 Replies

2. Shell Programming and Scripting

Constant mirroring

I'm not sure how to best explain what I'd like to do, so let me give an example. I used to work in a department that deals with internet security. This department had an "internal" website (only people in the building can get on it) and an "external" website (anyone in the world can get on it --... (1 Reply)
Discussion started by: sstevens
1 Replies

3. Solaris

-sh: is not an identifier

Hi , I am getting the following message when log into my unix account in sun solaris (version5.9)server. -sh: ORACLE_HOME=/apps/oracle/product/10.2.0/client_1: is not an identifier The ORACLE_HOME is set in .profile file. Another thing is that SID is also set inside .profile like... (4 Replies)
Discussion started by: megh
4 Replies

4. Shell Programming and Scripting

not an identifier

Hi I have already gone through this topic on this forum, but still i am getting same problem. I am using solaris 10. my login shell is /usr/bash i have got a script as below /home/gyan> cat 3.cm #!/usr/bin/ksh export PROG_NAME=rpaa001 if i run this script as below , it works fine... (3 Replies)
Discussion started by: gyanibaba
3 Replies

5. UNIX for Dummies Questions & Answers

Find and Replace random numeric value with non-numeric value

Can someone tell me how to change the first column in a very large 17k line file from a random 10 digit numeric value to a non numeric value. The format of lines in the file is: 1702938475,SNU022,201004 the first 10 numbers always begin with 170 (6 Replies)
Discussion started by: Bahf1s
6 Replies

6. Shell Programming and Scripting

is not an identifier

Hi Guys... I am using the following codes in my script: SID_L=`cat /var/opt/oracle/oratab|grep -v "^#"|cut -f1 -d: -s` SID_VAR=$SID_L for SID_RUN in $SID_VAR do ORACLE_HOME=`grep ^$SID_RUN /var/opt/oracle/oratab | \ awk -F: '{print $2}'` ;export ORACLE_HOME export... (2 Replies)
Discussion started by: Phuti
2 Replies

7. Programming

String Constant C

I wonder string constant exists permanently or temporary. For example, printf("hello, world"); the function printf access to it is through a pointer. Does it mean storage is allocated for the string constant to exist permanently in memory? :confused: (4 Replies)
Discussion started by: kris26
4 Replies
AUTOHEADER(1)						      General Commands Manual						     AUTOHEADER(1)

NAME
autoheader2.13 - creates a template file of C #define's for use by configure. SYNOPSIS
autoheader2.13 [ --help | -h ] [ --localdir=dir | -l dir ] [ --macrodir=dir | -m dir ] [ --version ] DESCRIPTION
The autoheader2.13 program can create a template file of C #define statements for configure to use. If configure.in invokes AC_CON- FIG_HEADER(FILE), autoheader2.13 creates FILE.in; if multiple file arguments are given, the first one is used. Otherwise, autoheader2.13 creates config.h.in. If you give autoheader2.13 an argument, it uses that file instead of configure.in and writes the header file to the standard output instead of to config.h.in. If you give autoheader2.13 an argument of -, it reads the standard input instead of configure.in and writes the header file to the standard output. autoheader2.13 scans configure.in and figures out which C preprocessor symbols it might define. It copies comments and #define and #undef statements from a file called acconfig.h, which comes with and is installed with Autoconf. It also uses a file called acconfig.h in the current directory, if present. If you AC_DEFINE any additional symbols, you must create that file with entries for them. For symbols defined by AC_CHECK_HEADERS, AC_CHECK_FUNCS, AC_CHECK_SIZEOF, or AC_CHECK_LIB, autoheader2.13 generates comments and #undef statements itself rather than copying them from a file, since the possible symbols are effectively limitless. The file that autoheader2.13 creates contains mainly #define and #undef statements and their accompanying comments. If ./acconfig.h con- tains the string @TOP@, autoheader2.13 copies the lines before the line containing @TOP@ into the top of the file that it generates. Simi- larly, if ./acconfig.h contains the string @BOTTOM@, autoheader2.13 copies the lines after that line to the end of the file it generates. Either or both of those strings may be omitted. An alternate way to produce the same effect is to create the files FILE.top (typically config.h.top) and/or FILE.bot in the current direc- tory. If they exist, autoheader2.13 copies them to the beginning and end, respectively, of its output. Their use is discouraged because they have file names that contain two periods, and so can not be stored on MS-DOS; also, they are two more files to clutter up the direc- tory. But if you use the --localdir=DIR option to use an acconfig.h in another directory, they give you a way to put custom boilerplate in each individual config.h.in. autoheader2.13 accepts the following options: --help -h Print a summary of the command line options and exit. --localdir=DIR -l DIR Look for the package files aclocal.m4 and acconfig.h (but not FILE.top and FILE.bot) in directory DIR instead of in the current directory. --macrodir=DIR -m DIR Look for the installed macro files and acconfig.h in directory DIR. You can also set the AC_MACRODIR environment variable to a directory; this option overrides the environment variable. --version Print the version number of Autoconf and exit. SEE ALSO
autoconf2.13(1), autoreconf2.13(1), autoscan2.13(1), autoupdate2.13(1), ifnames2.13(1) AUTHORS
David MacKenzie, with help from Franc,ois Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor, Roland McGrath, Noah Friedman, David D. Zuhn, and many others. This manpage written by Ben Pfaff <pfaffben@debian.org> for the Debian GNU/Linux autoconf2.13 package. Autoconf AUTOHEADER(1)
All times are GMT -4. The time now is 07:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy