05-12-2008
C Question compilation error
What does the following mean:
state_field state_abvr[] = {
"AL","ALABAMA",
"AK","ALASKA",
.
.
.
};
extern state_field state_abvr[];
issues we
I am facing following compilation issue
bosdf9d1:root make
CC -I/bto/bcs/shared/include -I/bto/sys/BCS/usr/include -I/usr/include -I/bto/bcs/archive/maint -I/usr/local/include -lc -lPW -I/usr/include/X11R5 -I/usr/include/Motif1.2 -c cd_main.c
CC: "cd_globals.c", line 28: error: state_field state_abvr: state_field is not a type name (1314)
CC: "cd_globals.c", line 82: error: syntax error: type expected for array state_abvr (1447)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [3] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [8] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [3] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [7] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [3] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [8] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [3] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [9] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [3] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [11] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [3] (int expected) (1106)
CC: "cd_globals.c", line 28: error: bad initializer type for ::state_abvr: char [9] (int expected) (1106)
CC: sorry, too many errors
*** Error exit code 1
Stop.
please help me
10 More Discussions You Might Find Interesting
1. Programming
Hi All,
I facing the following compilation error; when I implementing the following logic.
ostrstream ostr;
ostr << (( scAxsm.getRecord( i ).getField( 2 ).getShort())%12)!=0?(( scAxsm.getRecord( i ).getField( 2 ).getShort())/12+1)
: (( scAxsm.getRecord( i ).getField( 2 ).getShort())/12) <<... (1 Reply)
Discussion started by: sweta
1 Replies
2. Programming
Hi,
While trying compile a C++ file in UNIX with gcc whose make rule involves the usage of
/usr/ccs/bin/as, I get the following error:
/usr/ccs/bin/as: No such file or directory
/usr/ccs/bin/as: error: write error on output file "<filename>.o"
*** Error code 1
clearmake: Error: Build... (2 Replies)
Discussion started by: smanu
2 Replies
3. Programming
Hey, can I #define something outside the source file ?
I have a C program which uses #ifdef..
#ifdef ABC
... do this..
#else
... that ...
#endif
The usual way that I know of defining ABC is in the source/header file
#define ABC
But is there any other way to do that ? Maybe as... (2 Replies)
Discussion started by: the_learner
2 Replies
4. Programming
I am compiling a software xchm on solaris 10.
First i run './configure'
There is no error.
But when i start compiling using 'gmake'
following error shown
/usr/local/include/wx-2.6/wx/x11/brush.h: In copy constructor `wxBrush::wxBrush(const wxBrush&)':... (3 Replies)
Discussion started by: mansoorulhaq
3 Replies
5. Linux
Hello every one,
here i am attempting to compile a c++ module using gcc.it is throwing a error .
error:
====
> make -S dummyCHARGP
/usr/local/bin/gcc -g -DDEBUG -DMAT -I. -I/swtemp/usbs/cc/unix-ce/root/subsys/lib/Linux/ -I/opt/dce/include -I/opt/dce/include/dce ... (12 Replies)
Discussion started by: mannam srinivas
12 Replies
6. HP-UX
hello everyone,
here i am attempting to compile a c++ submodule.OS is HP-UX.
here i am getting the following error.
======================================
"Make: Don't know how to make compile. Stop."
===================================
could you pls somebody suggest why this error is... (2 Replies)
Discussion started by: mannam srinivas
2 Replies
7. Programming
Hello,
I am trying to compile a C program from Cygwin and it gives ld: not found -user32 error .. I searched for library libuser32.so and was not able locate it..
When i create only object file using gcc -c option it gets created successfully .. When i use gcc -o option , executable is not... (4 Replies)
Discussion started by: shafi2all
4 Replies
8. Programming
state_field state_abvr = {
"AL","ALABAMA",
"AK","ALASKA",
"AZ","ARIZONA",
"AR","ARKANSAS",
"CA","CALIFORNIA",
"CO","COLORADO",
"CT","CONNECTICUT",
"DE","DELAWARE",
"DC","DISTRICT-OF-COLUMBIA",
"FL","FLORIDA",
"GA","GEORGIA",
"HI","HAWAII",
"ID","IDAHO",
"IL","ILLINOIS",... (1 Reply)
Discussion started by: jagan_kalluri
1 Replies
9. Programming
I am getting the below given errors for the following program though all the variables have been declared and used appropriately. Please Help. The environment is AIX.
Error:
------
"gbsizeprofile.c", line 67.4: 1506-275 (S) Unexpected text 'void' encountered.
"gbsizeprofile.c", line 67.10:... (2 Replies)
Discussion started by: yschd
2 Replies
10. Programming
i am on red hat Linux .
package hiveudf;
import org.apache.hadoop.hive.ql.exec.UDF;
import org.apache.hadoop.io.Text;
public class lowercaseudf extends UDF {
public Text evaluate(final Text s) {
if (s == null) { return null;}
return new... (4 Replies)
Discussion started by: boncuk
4 Replies
LEARN ABOUT XFREE86
lfcompile64
lfcompile64(5) Standards, Environments, and Macros lfcompile64(5)
NAME
lfcompile64 - transitional compilation environment
DESCRIPTION
All 64-bit applications can manipulate large files by default. The transitional interfaces described on this page can be used by 32-bit and
64-bit applications to manipulate large files.
In the transitional compilation environment, explicit 64-bit functions, structures, and types are added to the API. Compiling in this
environment allows both 32-bit and 64-bit applications to access files whose size is greater than or equal to 2 Gbyte ( 2**31 bytes).
The transitional compilation environment exports all the explicit 64-bit functions (xxx64()) and types in addition to all the regular func-
tions (xxx()) and types. Both xxx() and xxx64() functions are available to the program source. A 32-bit application must use the xxx64()
functions in order to access large files. See the lf64(5) manual page for a complete listing of the 64-bit transitional interfaces.
The transitional compilation environment differs from the large file compilation environment, wherein the underlying interfaces are bound
to 64-bit functions, structures, and types. An application compiled in the large file compilation environment is able to use the xxx()
source interfaces to access both large and small files, rather than having to explicitly utilize the transitional xxx64() interface calls
to access large files. See the lfcompile(5) manual page for more information regarding the large file compilation environment.
Applications may combine objects produced in the large file compilation environment with objects produced in the transitional compilation
environment, but must be careful with respect to interoperability between those objects. Applications should not declare global variables
of types whose sizes change between compilation environments.
For applications that do not wish to conform to the POSIX or X/Open specifications, the 64-bit transitional interfaces are available by
default. No compile-time flags need to be set.
Access to Additional Large File Interfaces
Applications that wish to access the transitional interfaces as well as the POSIX or X/Open specification-conforming interfaces should use
the following compilation methods and set whichever feature test macros are appropriate to obtain the desired environment (see stan-
dards(5)).
o Set the compile-time flag _LARGEFILE64_SOURCE to 1 before including any headers.
o Use the getconf(1) command with one or more of the following arguments:
+------------------+----------------------------------------+
| argument | purpose |
|LFS64_CFLAGS | obtain compilation flags necessary to |
| | enable the transitional compilation |
| | environment |
|LFS64_LDFLAGS | obtain link editor options |
|LFS64_LIBS | obtain link library names |
|LFS64_LINTFLAGS | obtain lint options |
+------------------+----------------------------------------+
EXAMPLES
In the following examples, the transitional compilation environment is accessed by invoking the getconf utility with one of the arguments
listed in the table above. The additional large file interfaces are accessed either by specifying -D_LARGEFILE64_SOURCE or by invoking the
getconf utility with the arguments listed above.
The example that uses the form of command substitution specifying the command within parentheses preceded by a dollar sign can be executed
only in a POSIX-conforming shell such as the Korn Shell (see ksh(1)). In a shell that is not POSIX-conforming, such as the Bourne Shell
(see sh(1)) and the C Shell (see csh(1)), the command must be enclosed within grave accent marks.
Example 1: An example of compiling a program using transitional interfaces such as lseek64() and fopen64():
$ c89 -D_LARGEFILE64_SOURCE
$(getconf LFS64_CFLAGS) a.c
$(getconf LFS64_LDFLAGS)
$(getconf LFS64_LIBS)
Example 2: An example of running lint on a program using transitional interfaces:
% lint -D_LARGEFILE64_SOURCE
`getconf LFS64_LINTFLAGS` ...
`getconf LFS64_LIBS`
SEE ALSO
getconf(1), lseek(2), fopen(3C), lf64(5), standards(5)
SunOS 5.10 26 Jan 1998 lfcompile64(5)