Sponsored Content
Full Discussion: unresolved symbol ???
Top Forums UNIX for Dummies Questions & Answers unresolved symbol ??? Post 56695 by svennie on Friday 8th of October 2004 06:21:12 AM
Old 10-08-2004
ldd ncftp
sh. file not found.

there isn't a command like that..perhaps different unix versions.

also there isn't a file called "inet_ntop"...I think the program is

incompatible.

but no problem anymore, have another program that works fine. thx...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

timer_gettime unresolved error

I have used get_time() in my program but when I try to compile it it is giving the following error: ld: Unresolved: timer_gettime (5 Replies)
Discussion started by: basavaraj_m
5 Replies

2. Programming

c++ unresolved symbol

I have this problem: # make gcc -g -D_REENTRANT -DDISABLE_MJPEG=1 -I. -o encmain.o -c encmain.cc ld: 0711-317 ERROR: Undefined symbol: std::string::_Rep::_S_max_size collect2: ld returned 8 exit status but from /usr/local/include/g++v3/bits/basic_string.h : namespace... (0 Replies)
Discussion started by: thalex
0 Replies

3. Programming

Unresolved Symbol on HP UX & oracle7

Hi everyone, I have a problem. I do not succeed to linking the oracle7's library for my .so and a Unresolved Symbol :sqlcxt error returns me when I call program. this is my makefile. cc -Ae -I/usr/include/curses_colr -L/usr/lib -DUSE_TERMIOS -D_FILE64 -DDYNAMIC_LIBRARIES_SUPPORTED... (2 Replies)
Discussion started by: luckycs
2 Replies

4. Programming

How To Find Unresolved symbol in shared library?

1 . I use Digital Unix V4.0F 2 . I compile a programe which use a shared library . But when I run it( prog.out) , the shell told me that "Fatal Error : /sbin/loader : unresolved symbol in lib3cZap.so" But When I compile proj.out and lib3cZap.so , the compiler said nothing . And I ls -l... (1 Reply)
Discussion started by: chenhao_no1
1 Replies

5. Programming

unresolved symbol on AIX 5.2

Hi, want to port an executable from AIX 5.3 to AIX 5.2. This seems to be no problem, when i build one executable. But in another case i have to link one library statically and the rest is loaded at runtime. This works for AIX 5.3 but on AIX 5.2 i get the following error ... (2 Replies)
Discussion started by: pm_user
2 Replies

6. HP-UX

Unresolved symbol problem

Hi I am trying to make an executable which has informix esqlc and .per files. I am using informix version 9.3. The make is successful, but when i execute, i get an error message /usr/lib/dld.sl: Unresolved symbol: ibm_lib4gl_loadint4 (code) from RVprnrecvr Abort(coredump) I searched for... (4 Replies)
Discussion started by: venkatakrishnan
4 Replies

7. UNIX for Advanced & Expert Users

database connection (unresolved sqlcxt)

i have a little pro*c code (as shown below) to connect an oracle database. (in unix solaris platform) in the preprocessor compilation step everything is ok. but when i try to compile the code using cc i get the error below: ld: Unresolved: sqlcxt i think there is a problem while linking... (3 Replies)
Discussion started by: gfhgfnhhn
3 Replies

8. AIX

Unresolved symbols

Hello experts , i have some strange problem, i wanted to create a shared object in AIX 5.3 for which i have compiled all my .cxx to .o which worked fine and then i created the .so from them , but when i do nm -Bo sample.so , i have many unresolved symbol, including printf... (0 Replies)
Discussion started by: vin_pll
0 Replies

9. Solaris

/usr/lib/passwdutil.so.1: symbol __nsl_fgetspent_r: referenced symbol not found

deleteing post (0 Replies)
Discussion started by: dshakey
0 Replies
LD(1)							      General Commands Manual							     LD(1)

NAME
ld - loader SYNOPSIS
ld [ option ] file ... DESCRIPTION
Ld combines several object programs into one, resolves external references, and searches libraries. In the simplest case several object files are given, and ld combines them, producing an object module which can be either executed or become the input for a further ld run. (In the latter case, the -r option must be given to preserve the relocation bits.) The output of ld is left on a.out. This file is made executable only if no errors occurred during the load. The argument routines are concatenated in the order specified. The entry point of the output is the beginning of the first routine. If any argument is a library, it is searched exactly once at the point it is encountered in the argument list. Only those routines defin- ing an unresolved external reference are loaded. If a routine from a library references another routine in the library, and the library has not been processed by ranlib(1), the referenced routine must appear after the referencing routine in the library. Thus the order of programs within libraries may be important. If the first member of a library is named `__.SYMDEF', then it is understood to be a dictio- nary for the library such as produced by ranlib; the dictionary is searched iteratively to satisfy as many references as possible. The symbols `_etext', `_edata' and `_end' (`etext', `edata' and `end' in C) are reserved, and if referred to, are set to the first location above the program, the first location above initialized data, and the first location above all data respectively. It is erroneous to define these symbols. Ld understands several options. Except for -l, they should appear before the file names. -s `Strip' the output, that is, remove the symbol table and relocation bits to save space (but impair the usefulness of the debugger). This information can also be removed by strip(1). -u Take the following argument as a symbol and enter it as undefined in the symbol table. This is useful for loading wholly from a library, since initially the symbol table is empty and an unresolved reference is needed to force the loading of the first routine. -lx This option is an abbreviation for the library name `/lib/libx.a', where x is a string. If that does not exist, ld tries `/usr/lib/libx.a'. A library is searched when its name is encountered, so the placement of a -l is significant. -x Do not preserve local (non-.globl) symbols in the output symbol table; only enter external symbols. This option saves some space in the output file. -X Save local symbols except for those whose names begin with `L'. This option is used by cc(1) to discard internally generated labels while retaining symbols local to routines. -r Generate relocation bits in the output file so that it can be the subject of another ld run. This flag also prevents final defini- tions from being given to common symbols, and suppresses the `undefined symbol' diagnostics. -d Force definition of common storage even if the -r flag is present. -n Arrange that when the output file is executed, the text portion will be read-only and shared among all users executing the file. This involves moving the data areas up to the first possible 4K word boundary following the end of the text. -i When the output file is executed, the program text and data areas will live in separate address spaces. The only difference between this option and -n is that here the data starts at location 0. -o The name argument after -o is used as the name of the ld output file, instead of a.out. -e The following argument is taken to be the name of the entry point of the loaded program; location 0 is the default. -O This is an overlay file, only the text segment will be replaced by exec(2). Shared data must have the same layout as in the program overlaid. -D The next argument is a decimal number that sets the size of the data segment. FILES
/lib/lib*.a libraries /usr/lib/lib*.a more libraries a.out output file SEE ALSO
as(1), ar(1), cc(1), ranlib(1) BUGS
LD(1)
All times are GMT -4. The time now is 05:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy