11-15-2006
I received the following error message after attempting this.
Attempt:
ln -f libvxvm.so /usr/shlib/libvxvm.so
Error Message:
ln: libvxvm.so and /usr/shlib/libvxvm.so are located on different file systems.
Anyones help is greatly appreciated.
Jason
10 More Discussions You Might Find Interesting
1. Programming
Hi mates,
I am trying to copile and link to C programs with command:
cc file1,file2
but i raises the error "file not found" ... am i doing the right way?
any suggestion will be appreciated.
thanks
abdul (4 Replies)
Discussion started by: abdul
4 Replies
2. Shell Programming and Scripting
i am trying to link the text files that i generated from my shell script to an html page, to that i can view them using a browser, like internet explorer.
i want to open the text files in html page when i enter a command to view the text file from the shell command.
please could anyone help... (1 Reply)
Discussion started by: alexd
1 Replies
3. Programming
Hi
I'm getting
ld: fatal: option -h and building a dynamic executable are incompatible
ld: fatal: Flags processing errors
When I run
ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o
after running
gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c
I'm... (6 Replies)
Discussion started by: laho
6 Replies
4. Solaris
I'm trying to call a C mod from COBOL but I'm currently having difficulty linking my COBOL program with a C module that I've just developed. I've tried using cbllink -v -l -k -BSF CMPCACVN.cbl test.lib but I've got an error that states cbllink: not found. I've also tried using buildclient -C -w -o... (0 Replies)
Discussion started by: soulfactory2002
0 Replies
5. UNIX for Dummies Questions & Answers
hi,
This is the first time I work in a big C project. All source code files are located in say directory /source/pp and all header files are in /include/pp. I've created a link to both of these directories from my home dir, say /home/ss. So in the /home/ss dir I have the /source/pp and /include/pp... (1 Reply)
Discussion started by: bruins2005
1 Replies
6. UNIX for Dummies Questions & Answers
Getting the following error ,
ld: /opt/syncsort39/lib/libsyncsort.sl: Mismatched ABI. 64-bit PA shared library found in 32-bit link.
Is there any difference in the ld options in opt file while linking a 64 bit shared library ? Or is the problem because we are trying to link both 32 bit and 64... (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
7. Programming
Dear friends,
First off all , let me apologize for my inexperience. I am just starting use of Linux and gcc .
Actually I ve some .c files in the present directory , and now I am
giving
+vc <my_file1.c> <my.file2.c> <myfile3.c>.
All the c files are in present directory.... (2 Replies)
Discussion started by: user_prady
2 Replies
8. Shell Programming and Scripting
I used to program ksh a while back, but I've been off in Oracle/Windows land (for clients -- not by choice) for so long that I can't remember what should be an easy thing. Here's the scenario:
1)Find all files and directories beneath some directory point (A).
2)If directory, make the... (7 Replies)
Discussion started by: scyphers
7 Replies
9. Shell Programming and Scripting
I have 2 txt files, 1.txt and 2.txt which contain the paths to files that need to be linked.
Example 1.txt:
/root/001/folder2/image4.nii.gz
/root/002/folder2/image4.nii.gz
Example 2.txt:
/root/001/folder2/image5.nii.gz
/root/002/folder2/image5.nii.gz
Each line represents images from... (7 Replies)
Discussion started by: LeftoverStew
7 Replies
10. Programming
Basically my problem is that when I try to compile anything using ./configure && make, it fails because of linker errors. I can reproduce the behavior I'm getting as follows:
I have the two following files
main.c:
#include <stdio.h>
extern void func(void);
int
main(int argc, char... (5 Replies)
Discussion started by: MarshallBanana
5 Replies
LN(1) General Commands Manual LN(1)
NAME
ln - make links
SYNOPSIS
ln [ -s ] sourcename [ targetname ]
ln [ -s ] sourcename1 sourcename2 [ sourcename3 ... ] targetdirectory
DESCRIPTION
A link is a directory entry referring to a file; the same file (together with its size, all its protection information, etc.) may have
several links to it. There are two kinds of links: hard links and symbolic links.
By default ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are
effective independent of the name used to reference the file. Hard links may not span file systems and may not refer to directories.
The -s option causes ln to create symbolic links. A symbolic link contains the name of the file to which it is linked. The referenced
file is used when an open(2) operation is performed on the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2)
must be done to obtain information about the link. The readlink(2) call may be used to read the contents of a symbolic link. Symbolic
links may span file systems and may refer to directories.
Given one or two arguments, ln creates a link to an existing file sourcename. If targetname is given, the link has that name; targetname
may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified,
the link will be made to the last component of sourcename.
Given more than two arguments, ln makes links in targetdirectory to all the named source files. The links made will have the same name as
the files being linked to.
SEE ALSO
rm(1), cp(1), mv(1), link(2), readlink(2), stat(2), symlink(2)
4th Berkeley Distribution April 10, 1986 LN(1)