05-08-2008
Not able to compile .pcc (Pro*C++) file
Hello,
I use Omniworks build environment for compiling pro*c++(filename.pcc) files which would result in .filename.cc. I am not able get these files due some misplacement in environment... Could anyone explain the environment variable linked to it .. I know few like LIB_PATH,LD_LIBRARY_PATH and ORACLE_HOME (which contains pro*c precompiler)..
Shafi
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
this is the seventh problem i'm having with samba.
for some reason, i cannot logon to the domain.
i've created user accounts... and i was able to establish a connection between
the samba server (my PDC) and my workstations by logging in as "root."
however now when i try to logon it gives... (5 Replies)
Discussion started by: xyyz
5 Replies
2. 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
3. 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
4. Programming
Hi,
How to precompile the c program which has proc statements within it.
If it is only c, I will use the following cmd
cc filename.c -o output
so please tell me what command I have to use for precompilation.
I beleave that this is not an oracle or proc forum, but still I hope will... (1 Reply)
Discussion started by: sweta
1 Replies
5. Programming
I am trying to compile the pro*C file but gives errors. It says it encountered "std" while it was expecting ; , = ( $ $ORACLE_HOME/bin/proc tradewind/dataaccess/Blob.pcc
Pro*C/C++: Release 10.2.0.3.0 - Production on Fri May 9 11:10:54 2008
Copyright (c) 1982, 2005, Oracle. All rights... (0 Replies)
Discussion started by: shafi2all
0 Replies
6. Shell Programming and Scripting
I am unable to compile the programs, I am able to compile .pc to .c but later part of the compilation from .c to executalbe i am unable to do.
Here is the way i am doing
make -f $LIB_LIB/makefile.templ sample
I am getting the following errors, which environment and where to set to point... (1 Reply)
Discussion started by: satvd
1 Replies
7. Shell Programming and Scripting
How do I compile a test file to test functionality of my script? (1 Reply)
Discussion started by: Pauline mugisha
1 Replies
8. Shell Programming and Scripting
Hi,
I was compiling few C programs in the unix server and getting the following error message
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 ... (1 Reply)
Discussion started by: kavithakuttyk
1 Replies
9. UNIX for Dummies Questions & Answers
I have just installed OpenBSD on a 333MHz PPC iMac G3. It has a 6GB HDD that has been partitioned as 1GB MacOS 8.5.1, 3GB MacOS X 10.3.9, 2GB OpenBSD 4.8. I now need to install a bootloader so that my computer can recognize the OpenBSD partition at startup. I have been trying to install... (0 Replies)
Discussion started by: t04st3r
0 Replies
10. Programming
hello everybody! I have the source code(C) about a flat file system with shell,directory service,file service and blockservice.But I don t know how to compile this.Can anyone inform me?I connect to a remote system of Unix...Actually I have 4 files,system.c direct.c blockserv.c and fileserv.c.:( (4 Replies)
Discussion started by: sonia13
4 Replies
LEARN ABOUT MOJAVE
environment.d
ENVIRONMENT.D(5) environment.d ENVIRONMENT.D(5)
NAME
environment.d - Definition of user session environment
SYNOPSIS
~/.config/environment.d/*.conf
/etc/environment.d/*.conf
/run/environment.d/*.conf
/usr/lib/environment.d/*.conf
/etc/environment
DESCRIPTION
The environment.d directories contain a list of "global" environment variable assignments for the user environment. systemd-environment-d-
generator(8) parses them and updates the environment exported by the systemd user instance to the services it starts.
It is recommended to use numerical prefixes for file names to simplify ordering.
For backwards compatibility, a symlink to /etc/environment is installed, so this file is also parsed.
CONFIGURATION DIRECTORIES AND PRECEDENCE
Configuration files are read from directories in /etc/, /run/, and /lib/, in order of precedence. Each configuration file in these
configuration directories shall be named in the style of filename.conf. Files in /etc/ override files with the same name in /run/ and
/lib/. Files in /run/ override files with the same name in /lib/.
Packages should install their configuration files in /lib/. Files in /etc/ are reserved for the local administrator, who may use this logic
to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic
order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the
lexicographically latest name will take precedence. It is recommended to prefix all filenames with a two-digit number and a dash, to
simplify the ordering of the files.
If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null
in the configuration directory in /etc/, with the same filename as the vendor configuration file. If the vendor configuration file is
included in the initrd image, the image has to be regenerated.
CONFIGURATION FORMAT
The configuration files contain a list of "KEY=VALUE" environment variable assignments, separated by newlines. The right hand side of these
assignments may reference previously defined environment variables, using the "${OTHER_KEY}" and "$OTHER_KEY" format. It is also possible
to use "${FOO:-DEFAULT_VALUE}" to expand in the same way as "${FOO}" unless the expansion would be empty, in which case it expands to
DEFAULT_VALUE, and use "${FOO:+ALTERNATE_VALUE}" to expand to ALTERNATE_VALUE as long as "${FOO}" would have expanded to a non-empty value.
No other elements of shell syntax are supported.
Each KEY must be a valid variable name. Empty lines and lines beginning with the comment character "#" are ignored.
Example
Example 1. Setup environment to allow access to a program installed in /opt/foo
/etc/environment.d/60-foo.conf:
FOO_DEBUG=force-software-gl,log-verbose
PATH=/opt/foo/bin:$PATH
LD_LIBRARY_PATH=/opt/foo/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
XDG_DATA_DIRS=/opt/foo/share:${XDG_DATA_DIRS:-/usr/local/share/:/usr/share/}
SEE ALSO
systemd(1), systemd-environment-d-generator(8), systemd.environment-generator(7)
systemd 237 ENVIRONMENT.D(5)