04-29-2010
The static link is telling you, in so many words, that the runtime code does not exist in the .a file(s) used to make a static link - the archive does not have the entry point for the getaddrinfo() call.
10 More Discussions You Might Find Interesting
1. Programming
I like to compile a cxx file with g++ compiler.
I tried with option
g++ -I<include path> -L<library path> source-file
but ending with compilation error in /usr/local/bin/gcc-lib/.../crt1.o
I think the libraries are not taken from proper path
How to compile a cxx file with libraries... (1 Reply)
Discussion started by: ls1429
1 Replies
2. Programming
Hi
Where is the default location of libs to search, when we specify any lib in dlopen function.
And if we want to specify a custom location, how will we do it?
thanks. (1 Reply)
Discussion started by: sumsin
1 Replies
3. Shell Programming and Scripting
Hello all
my project is contains 2 directories, 2 directories are building library and one for the executable that using the libes from the other 2
Now what im doing is compiling first the 2 libs directories and then the main directory. But I will like to automate the process and to be able ... (0 Replies)
Discussion started by: umen
0 Replies
4. Programming
hello everybody!
I m compiling some program with the g++ on AIX 5.3 and it needs some library that i didn't find them i am new with the AIX here is the compilation error :
g++ -Daix -fpic -o printps -lxercesc1_1 -L/oracle/OraHome/lib32/ -L/epost2/blitz/lib -lhmltods -lhmltops -lgeneric... (0 Replies)
Discussion started by: eternalflame
0 Replies
5. AIX
I think the default extension on AIX is .a
so for dynamic lib "libabc.a", we can simply link against it by specifying "-labc"
but here I have a dylib which been built by some one else called "libxyz.so" on AIX. once I say "-lxyz" the linker is only looking for libxzy.a but not .so after that.... (2 Replies)
Discussion started by: acerlinux
2 Replies
6. AIX
Hi ,
I need some inputs on runtime or shared libs for an application(s) in AIX .
i have a requirement saying i need to rehost all the production applications into new AIX OS .
Here Source and target oS is AIX but with different versions
so for this i need to identify what are the... (1 Reply)
Discussion started by: naren_chella
1 Replies
7. Shell Programming and Scripting
How would I go about writing a 'Mad Libs' type program using Ruby?
Any examples would be greatly appreciated.
Thanks! (0 Replies)
Discussion started by: greeky
0 Replies
8. SuSE
Hi All,
I wanted to install an rpm package on two suse 10 systems. It installed successfully on one system but on the other it throws an error like
error: Failed dependencies:
rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by linuxProj-1-1.noarch
Now this means that rpnm... (4 Replies)
Discussion started by: dirshah
4 Replies
9. AIX
I want to create a shared lib with certain libs statically linked to it. I can generate a fully shared lib as follows:
gcc -maix64 -DHAVE_CONFIG_H -I. -I./src -DHAVE_OPENSSL -I/usr/include/openssl -I/usr/include -I/usr/include/apr-1 -D_LARGEFILE64_SOURCE -I/usr/java8_64/include -shared -o... (0 Replies)
Discussion started by: amandeepgautam
0 Replies
10. UNIX for Advanced & Expert Users
Hello. I am looking for all the necessary packages required to be able to compile libXft.
I tried to compile libXft-2.1.8.2$ and the error message was:
checking for XRENDER... checking for XRENDER... checking for X... no
checking X11/extensions/Xrender.h usability... no
checking... (1 Reply)
Discussion started by: colt
1 Replies
link(1) General Commands Manual link(1)
NAME
link, unlink - Creates an additional directory entry for an existing file
SYNOPSIS
link file1 file2
unlink file
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link: XCU5.0
unlink: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The link command performs the link() system call to create an additional directory entry for an existing file, file1. In effect, the
underlying file then has two names, file1 and file2 (either of these arguments can be a pathname). The old and new entries share equal
access rights to the underlying file.
The unlink command performs the unlink() system call to remove a link to file created by link. The unlink command removes the directory
entry specified by the file parameter and, if the entry is a hard link, decrements the link count of the file referenced by the link.
You should be familiar with the link() and unlink() system calls before you use these commands.
The link and unlink commands do not issue error messages when the associated system call is unsuccessful.
NOTES
The link and unlink commands cannot be used to link and unlink directories.
EXIT STATUS
The link and unlink commands both exit with the following: The link() or unlink() system call succeeded. Too few or too many arguments
specified. The link() or unlink() system call failed.
SEE ALSO
Commands: fsck(8), ln(1)
Functions: link(2), unlink(2)
link(1)