11-18-2011
Is there more to the error message? Perhaps a warning of an unresolved symbol?
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I have installed "Freetype2" library in my SuSe Linux 9.3 version system. When Iam compiling a program, I am getting these below errors.
Undefined reference to "FT_Init_FreeType"
Undefined reference to "FT_Load_Char"
Please show me a solution? Thank you.
With regards,
Chandramouli (1 Reply)
Discussion started by: chandra80
1 Replies
2. UNIX for Dummies Questions & Answers
I need Help folks;
I'm very new to Java & i was trying to compile some java files & i got a lot of errors (see below), could some one tell me what am i doing wrong?
These are the files i need to compile:
AddCommentActionLogging.java
EditPageActionLogging.java
When i run:... (4 Replies)
Discussion started by: Katkota
4 Replies
3. Shell Programming and Scripting
Hi,
I have generated a Public/Private Key Pair in Solaris Unix (source) server and deployed the Public key in Windows 2003(target) server .ssh directory of user profile.
When i try to connect(ssh, scp, sftp) from Unix, i'm getting below error message.
Sun_SSH_1.1, SSH protocols 1.5/2.0,... (0 Replies)
Discussion started by: ajaykumarb
0 Replies
4. Programming
Hi guys.
I have a header file: unp.h like this:
#ifndef _UNP_H_
#define _UNP_H_
extern ssize_t readn(int filedes, void *buff, size_t nbytes);
extern ssize_t writen(int filedes, const void *buff, size_t nbytes);
extern void err_quit(const char *msg);
#define TRUE 1
#define FALSE 0
... (2 Replies)
Discussion started by: majid.merkava
2 Replies
5. Solaris
Hi Experts,
While trying to query nameserver using nslookup it is giving following error.
root@prod # nslookup 10.1.61.21
** server can't find 26.61.1.10.in-addr.arpa.: NXDOMAIN
root@prod #
(1)
/etc/hosts
10.1.61.2 prod
(2)I also added domain and namservers accordingly in... (6 Replies)
Discussion started by: sai_2507
6 Replies
6. Solaris
Hi guys i came across an error while compiling a c file in solaris using gcc. the error is,
Undefined first referenced
symbol in file
bind /var/tmp//ccAr8qAh.o
accept ... (4 Replies)
Discussion started by: rajeshb6
4 Replies
7. Solaris
i am installed solaris 10 latest release i want to install Veritas cluster in solaris and i already installed VXVM in it and it works fine but when i install cluser on solaris i display an error like this what does it mean ? explain in detailed.
2 Failed to call set_value for... (1 Reply)
Discussion started by: samiulla
1 Replies
8. Answers to Frequently Asked Questions
I tried to compile the files in basic_dump_ex using cygwin :
/cygdrive/c/WpdPack/Examples-pcap/basic_dump_ex
$make
but I got this :
cc -g -O -mno-cygwin -I ../../include -c -o basic_dump_ex.o basic_dump_ex.c
cc: error: unrecognized command line option ‘-mno-cygwin’... (6 Replies)
Discussion started by: steve120
6 Replies
9. UNIX for Beginners Questions & Answers
Hi
I am trying to compile a binary file (CASPER: Context-Aware Scheme for Paired-End Read) but I am getting the following error:
user@user-OptiPlex-780 make
g++ -O2 -Wall -fopenmp -c -o merge.o merge.c
merge.c:8:35: fatal error: boost/unordered_map.hpp: No such... (2 Replies)
Discussion started by: Xterra
2 Replies
10. UNIX for Beginners Questions & Answers
Hi,
I have downloaded gzipped source tarball of python3.7. I have tried to compile like below,
./configure --prefix=/directory
Compiling seems to be ok..But when running make all..Getting too many missing initializer warnings
/python3.6/Python-3.6.0/Modules/_cursesmodule.c: At top level:... (1 Reply)
Discussion started by: Sumanthsv
1 Replies
stio(3) Library Functions Manual stio(3)
NAME
stio - Routines that provide a binary read/write interface to the symbol table
SYNOPSIS
#include <syms.h>
long st_readbinary (filename, how)
char *filename;
char how;
long st_readst (fn, how, filebase, pchdr, flags)
long fn;
char how;
long filebase;
pCHDRR pchdr;
long flags;
void st_writebinary (filename, flags)
char *filename;
long flags;
void st_writest (fn, flags)
long fn;
long flags;
DESCRIPTION
The CHDRR structure (see stcu(3)) represents a symbol table in memory. A new CHDRR can be created by reading a symbol table in from disk.
The St_readbinary and st_readst routines read a symbol table in from disk.
The St_readbinary routine takes the file name of the symbol table and assumes the symbol table header HDRR occurs at the beginning of the
file. The St_readst routine assumes that its file number references a file positioned at the beginning of the symbol table header and that
the filebase parameter specifies where the object or symbol table file is based (for example, non-zero for archives).
The second parameter to the read routines can be `r' for read only or `a' for appending to the symbol table. Existing local symbol, line,
procedure, auxiliary, optimization, and local string tables can not be appended. If they did not exist on disk, they can be created. This
restriction stems from the allocation algorithm for those symbol table sections when read in from disk and follows the standard pattern for
building the symbol table.
The symbol table can be read incrementally. If pchdr is zero, st_readst assumes that no symbol table has been read yet; therefore, it
reads in the symbol table header and file descriptors. The flags argument is a bit mask that defines what other tables should be read.
St_p* constants for each table can be ORed. If flags equals `-1', all tables are read. If pchdr is set, the tables specified by flags are
added to the tables that have already been read. The value of pchdr can be gotten from st_current_pchdr (see stcu(3)).
Line number entries are encoded on disk, and the read routines expand them to longs.
If the version stamp is out of date, a warning message is issued to stderr. If the magic number in the HDRR is incorrect, st_error is
called. All other errors cause the read routines to read non-zero; otherwise, a zero is returned.
The St_writebinary and st_writest routines are symmetric to the read routines, excluding the how and pchdr parameters. The flags parameter
is a bit mask that defines what table should be written. St_p* constants for each table can be ORed. If flags equals `-1', all tables are
written.
The write routines write sections of the table in the approved order, as specified in the link editor (ld) specification.
Line numbers are compressed on disk.
The write routines start all sections of the symbol table on four-byte boundaries.
If the write routines encounter an error, st_error is called. After writing the symbol table, further access to the table by other routines
is undefined.
RELATED INFORMATION
stcu(3), stfe(3), stfd(3) delim off
stio(3)