05-21-2008
Pro*c compilation error
Hi,
Recently our codes have been migrated to new server, whenever we compile any pro*c programs we receive the following
errorl. please help
>> make -f lib_util.mk all
CC= ucbcc 4Compiling lib_util
### command line files and options (expanded):
### -xO3 -DNULL=0 -v -o lib_util.o -L/opt/oracle/product/10.2.0/precomp/lib/ -L/opt/oracle/product/10.2.0/lib/ -c lib_util.c -I. -I./include
### ucbcc: Note: NLSPATH = /opt/SUNWspro/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
/opt/SUNWspro/prod/bin/acomp -Qy -N /tmp/acomp.14994.2.ir -I. -I./include -g "/opt/SUNWspro/prod/bin/acc -O -DNULL=0 -v -L/opt/oracle/product/10.2.0/precomp/lib/ -L/opt/oracle/product/10.2.0/lib/ -c -I. -I./include -c" -b -Xa -D__SunOS_5_10 -D__SUNPRO_C=0x570 -Dunix -Dsun -Dsparc -D__unix -D__sun -D__sparc -D__BUILTIN_VA_ARG_INCR -D__SVR4 -D__RESTRICT -D__PRAGMA_REDEFINE_EXTNAME -I/opt/SUNWspro/prod/include/cc -O3 -DNULL=0 -destination_ir=iropt -i lib_util.c -o /tmp/acomp.14994.1.s -r /tmp/acomp.14994.0.ir
"lib_util.c", line 117: warning: no explicit type given
"lib_util.c", line 119: warning: no explicit type given
"lib_util.c", line 121: warning: no explicit type given
"lib_util.c", line 122: warning: no explicit type given
"lib_util.c", line 123: warning: no explicit type given
/opt/SUNWspro/prod/bin/iropt -N/tmp/acomp.14994.2.ir -O3 -xarch=generic -xcache=generic -xchip=generic -F -xvector=no -xprefetch=auto,explicit -xprefetch_level=1 -I -o /tmp/iropt.14994.3.ir -is /tmp/acomp.14994.1.s /tmp/acomp.14994.0.ir
compiler(iropt) error: FCALL with no root
rm /tmp/acomp.14994.0.ir
rm /tmp/acomp.14994.1.s
rm /tmp/acomp.14994.2.ir
rm /tmp/iropt.14994.3.ir
*** Error code 1
The following command caused the error:
ucbcc -O -DNULL=0 -v -o lib_util.o -L/opt/oracle/product/10.2.0/precomp/lib/ -L/opt/oracle/product/10.2.0/lib/ -c lib_util.c -I. -I./include
make: Fatal error: Command failed for target `lib_util.o'
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
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
4. 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
5. 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
6. Programming
Hi,
Recently our codes have been migrated to new server, whenever we compile any pro*c programs we receive the following
errorl. please help
>> make -f lib_util.mk all
CC= ucbcc 4Compiling lib_util
### command line files and options (expanded):
### -xO3 -DNULL=0 -v -o lib_util.o... (0 Replies)
Discussion started by: satvd
0 Replies
7. AIX
Hi,
I have AIX 5.3 and my code is written in proc . i am getting following error during compilation
Please help?////.....
[H[2J:-d:
Compiling with RMS
cc -w -q32 -qidirfirst -ISource/Header -I/usr/vacpp/include -q32 -DRMS -DDISEC -DDBG -DBIGENDIAN -DBIT32 -c -q32... (0 Replies)
Discussion started by: ajaysahoo
0 Replies
8. Programming
I'm running a query similar to the one that I'm describing below -:
_______________________________
EXEC SQL INSERT INTO TABLE1
( C1
,C2
,C3
,C4 )
(SELECT DISTINCT B.V1
,B.V2
,( SELECT D.V3 FROM TABLE2 D WHERE D.V3 = C.V4)
,B.V4
FROM TABLE2 B ,TABLE3 C
WHERE B.V3 = C.V4) ;... (1 Reply)
Discussion started by: maheshp
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
This is my first post to this forum. I have been facing a strange compilation error message. When I try to make a pro*C file on HP-UX ( uname -a shows HP-UX aopc7449 B.11.11 U 9000/800 2416083493 unlimited-user license),
::: Linking...
/usr/ccs/bin/ld: profls.o: Not a valid object file... (5 Replies)
Discussion started by: asutoshch
5 Replies
10. 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
LEARN ABOUT V7
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)