It's not a Pro*C problem. It's a linking problem. Since you are dealing with a lot of variables: complex make file, multiple source files, precompilers, etc - there are too many things to rule out for us to get a good solution
So, I'll make a simple suggestion that may not be the best solution but has the highest probability of working:
Somewhere near the top of your OrdItmpopulate.pc file (before you invoke "msg_open" or any of the other calls that are causing errors) put the following:
NOTE: exfcns.c has to exist either in the current directory or in one of the directories specified to the proc (pro*C precompiler) command. The directories specified with -I
I would place exfcns.c in the current directory and add
as another proc command line parameter.
I'm trying to compile a FTP_API program. To do this you must use the libftp.so libary. But that libary has references which are not defined. Has anyone had this problems and how is it corrected??
The command line looks like this:--------------------------------------------
# cc ftpstock.c -lftp... (5 Replies)
Hello, I have never had a successful compile on the 2.6 kernel. On every arch in which I try to compile gcc I get either "i686-pc-cygwin-ar command not found or "i686-suse-linux-ar command not found. This always happens during the make process after configure checks for ar and finds it's just ar.... (2 Replies)
hello everyone,
here i attempting to compile a c++ module .
I am using the following command
make -d dummyCHARGP.
i am using the gcc compiler .my os is HP-UX 11.11.
here i am getting the following errors.
errors:
=======
/swtemp/usbs/cc/unix-ce/root/subsys/include/main.h:146:... (1 Reply)
Hi all,
Apologies if this is the wrong forum for this question, if it is, could some one point me to the right one please.
I am trying to compile bind-9.5.1b1 on Solaris 10
Get the error when try to configure:
checking for OpenSSL library... using OpenSSL from /usr/local/lib and... (5 Replies)
First of all, I'd like to preface this post by relaying that I have considerable experience with FreeBSD but I'm a Linux newb. I've been attempting to compile linux-2.6.29.3 from source and I'm having some problems and have a few newb questions...
a) First of all, my kernel won't boot, it fails... (0 Replies)
I want to compile a shell script so that anyone can run it on any linux platform without being able to view its content. Is there any way to do this?
Thanks in advance
---------- Post updated at 12:00 PM ---------- Previous update was at 11:35 AM ----------
shc creates a stripped binary ... (2 Replies)
I have the following lines of script to run sequentially(i.e one after the other as arranged). how can I compile it to one shell script of the form DATABASE.sh
awk '$2~/eaw/{BSC=$3}{print BSC,$0}' RXMOP.log | grep GSM | awk '{print $1,$2,$3,$5}'>TX.data
sed 's/RXOTX/RXORX/g' TX.data>RX.data
sed... (4 Replies)
i've got an older white macbook running 10.4.11. about 5 years old i think.
trying to install ffmpeg in 2 different ways. having errors on both.
first tried this one:
ffmpeg installation on Mac OSX
and i got this error when i got down to "make" on the ffmpeg itself
make(350) malloc: ***... (1 Reply)
I'm trying to write a script that can compile my students' homework submissions in bulk. My students' c code is buried in a file path that looks like this:
./Homework\ X/Doe, John/Submission\ Attachments
Where I'm struggling is determining how to navigate to each of the submission attachment... (11 Replies)
Hello friends,
Am trying to compile and build Handbrake 0.9.9 on my redhat box but getting the below errors.
Same errors when I compile the source from github and also from the official web site.
# uname -a
Linux blah.com 2.6.18-274.el5 #1 SMP Fri Jul 8 17:36:59 EDT 2011 x86_64 x86_64... (0 Replies)
Discussion started by: prvnrk
0 Replies
LEARN ABOUT HPUX
cd
cd(1) General Commands Manual cd(1)NAME
cd - change working directory
SYNOPSIS
[directory]
DESCRIPTION
If directory is not specified, the value of shell parameter is used as the new working directory. If directory specifies a complete path
starting with or directory becomes the new working directory. If neither case applies, tries to find the designated directory relative to
one of the paths specified by the shell variable. has the same syntax as, and similar semantics to, the shell variable. must have execute
(search) permission in directory.
exists only as a shell built-in command because a new process is created whenever a command is executed, making useless if written and pro-
cessed as a normal system command. Moreover, different shells provide different implementations of as a built-in utility. Features of as
described here may not be supported by all the shells. Refer to individual shell manual entries for differences.
If is called in a subshell or a separate utility execution environment such as:
(which invokes on accessible directories) does not affect the current directory of the caller's environment. Another usage of as a stand-
alone command is to obtain the exit status of the command.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multi-byte character code sets are supported.
Environment Variables
The following environment variables affect the execution of
The name of the home directory,
used when no directory operand is specified.
A colon-separated list of pathnames that refer to directories.
If the directory operand does not begin with a slash character, and the first component is not dot or dot-dot, searches
for directory relative to each directory named in the variable, in the order listed. The new working directory is set
to the first matching directory found. An empty string in place of a directory pathname represents the current direc-
tory. If is not set, it is treated as if it was an empty string.
EXAMPLES
Change the current working directory to the directory from any location in the file system:
Change to new current working directory residing in the current directory:
or
Change to directory residing in the current directory's parent directory:
Change to the directory whose absolute pathname is
Change to the directory relative to home directory:
RETURN VALUE
Upon completion, exits with one of the following values:
The directory was successfully changed.
An error occurred. The working directory remains unchanged.
SEE ALSO csh(1), pwd(1), ksh(1), sh-posix(1), sh(1), chdir(2).
STANDARDS CONFORMANCE cd(1)