12-02-2009
PCC-F-NOERRFILE, unable to open error message file
Hi,
I was compiling few C programs in the unix server and getting the following error message
HTML Code:
rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent
proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE
INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE INCLUDE=/home/a0xxx28/PVT/UT/INCLUDE DEFINE=SQL DEFINE=AIRFLITE_REL_3
DEFINE=PFM -DPFM_PVTDT iname=costdistDB.pc
PCC-F-NOERRFILE, unable to open error message file, facility PR2
*** Error exit code 1"
Can anybody guide me to resolve this issue?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am trying to build a tuxedo server which in turn depends on several Pro*C programs. I am doing it on HP-UX system.
It looks to me that the ORACLE_HOME is set properly.
But I am getting error message when trying to build.
PCC-F-NOERRFILE, unable to open error message file, facility PR2
exit... (1 Reply)
Discussion started by: asutoshch
1 Replies
2. Programming
While compiling and executing i get the following error.
Error at line 1200, column 1 in file xxx.pc
{
1
PCC-S-02201,Encountered the symbol "{" when expecting one of the following:
; , = < [
please help (1 Reply)
Discussion started by: musavir19
1 Replies
3. UNIX for Dummies Questions & Answers
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@
@ (6 Replies)
Discussion started by: bobo
6 Replies
4. Solaris
I am using the "find" command below and it respond with the error message " find: cannot open /: Stale NFS file handle"
what does it mean?
what can I do about it?
Need advice, thanks.
below are the command that I enter, the respond and the error message:
root@ScripServer:/# find / -name... (1 Reply)
Discussion started by: ezsurf
1 Replies
5. UNIX for Advanced & Expert Users
I am working on a unix server.
I killed all the processes with my id on the machine.
After that I tried to delete a file, I got an error:-
file not removed.Text File busy.
Deletion of directory prompted:-
Directory not empty.
Can anyone help me regarding this...???
Thanks,
Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies
6. UNIX for Dummies Questions & Answers
I get this message when I write myshell.c program "VM pagefault:SIGSEGV bad add 0x0 err 0x4 nopage read myshell PM: ciredump signal 11 for 1725 /myshell memory fault (core dumped)"
/* RCS information: $Id: myshell.c,v 1.2 2006/04/05 22:46:33 elm Exp $ */
#include <stdio.h>
#include <unistd.h>... (1 Reply)
Discussion started by: rosecomp
1 Replies
7. Solaris
Hello guys,
Thanks for all your precious tips.
I hope you can give me some advice again.
This time I am having an issue with a SUN FIRE V240 (SOLARIS 10).
The server doesn't boot, normally , first we had a file system error
====================+FIRST ERROR... (6 Replies)
Discussion started by: feg
6 Replies
8. Red Hat
Hi,
I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5,
example
vi test
it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies
9. UNIX for Dummies Questions & Answers
I am trying to direct a AIX display to my XWindows and I am at a dead end now!
So this what I've done so far:
1. In putty settings, I set "Enable X11 forwarding" and also set "X diplay location" to "localhost:0" (without quotes, of course)
2. Via putty, connected to my AIX server
3. On... (1 Reply)
Discussion started by: shoefiend
1 Replies
10. Shell Programming and Scripting
Hi,
I am trying to open small size file only in vi editor on solaris or Linux machine
but it giving message "Terminal too wide" and then I have to come out.
As shown below:-
-rwxr-x--- 1 rkycadm rkycprd 2445 Sep 12 04:06
$ vi file.txt
Terminal too wide
:q!
----------... (2 Replies)
Discussion started by: RahulJoshi
2 Replies
LEARN ABOUT DEBIAN
dcl2inc
DCL2INC(1) General Commands Manual DCL2INC(1)
NAME
dcl2inc - postprocess ftnchek .dcl files to create separate INCLUDE files
SYNOPSIS
dcl2inc *.dcl
DESCRIPTION
dcl2inc postprocessing declaration files output by ftnchek(1), replacing unique COMMON block definitions by Fortran INCLUDE statements.
For each input .dcl file, a modified output .dcn file is produced, together with include files named by the COMMON block name, with file-
name extension .inc.
In addition, dcl2inc produces on stdout a list of Makefile dependencies for the UNIX make(1) utility. These can be appended to the project
Makefile to ensure that any subsequent changes to .inc files provoke recompilation of source files that include them.
dcl2inc warns about COMMONs which differ from their first occurrence, and simply copies them to the output .dcn file, instead of replacing
them with an INCLUDE statement. Thus, any COMMON statements that are found in the output .dcn files should be examined carefully to deter-
mine why they differ: they may well be in error.
Replication of identical data, and bugs arising from subsequent modification of only part of it, is a significant reason why Fortran pro-
gramming projects should require that COMMON declarations occur in separate include files, so that there is only a single point of defini-
tion of any global object.
Even though the Fortran INCLUDE statement was tragically omitted from the 1977 Standard, it has long been implemented by virtually all com-
piler vendors, and is part of the 1990 Standard. In practice, there is therefore no portability problem associated with use of INCLUDE
statements, provided that one avoids nonportable file names. As long as the code obeys Fortran's limit of six-character alphanumeric
names, the filenames generated by dcl2inc will be acceptable on all current popular operating systems.
Fortran's default, or IMPLICIT, variable typing is deprecated in modern programming languages, because it encourages sloppy documentation,
and worse, bugs due to misspelled variables, or variables that have been truncated because they extend past column 72. If all variables
used are explicitly typed, and a compiler option is used to reject all program units with untyped variables, variable spelling and trunca-
tion errors can be eliminated.
Variable declarations that have been produced automatically by a tool like ftnchek(1) or pfort(1) have a consistent format that facilitates
application of stream editors (e.g. to change array dimensions or rename variables), and simple floating-point precision conversion tools
like d2s(1), dtoq(1), dtos(1), qtod(1), s2d(1), and stod(1).
CAVEAT
The current version (2.9) of ftnchek(1) does not produce Fortran EQUIVALENCE statements in .dcl files, so you must be careful to preserve
them when replacing original declarations with new ones from .dcl or .dcn files.
SEE ALSO
d2s(1), dtoq(1), dtos(1), ftnchek(1), make(1), pfort(1), qtod(1), s2d(1), stod(1).
AUTHOR
Nelson H. F. Beebe, Ph.D.
Center for Scientific Computing
Department of Mathematics
University of Utah
Salt Lake City, UT 84112
Tel: +1 801 581 5254
FAX: +1 801 581 4148
Email: <beebe@math.utah.edu>
Version 1.00 12 March 1995 DCL2INC(1)