11-22-2001
e.g. your souce file is mm.c
you can do it like this:
$ gcc -o libmm.so -shared mm.c
for more info man gcc(1).
10 More Discussions You Might Find Interesting
1. Programming
Hello everybody,
I am having major problems at the moment with shared libraries and I have to little knowledge of them to solve them. So please, please help me :)
Ok this is the problem:
I have a library A, which uses B and C, and C uses again D.
If I try to run A as plugin in apache,... (0 Replies)
Discussion started by: Micky
0 Replies
2. UNIX for Dummies Questions & Answers
I have a doubt about the shared libraries. Where do you set the path for the shared libaries, for the dynamic loader to locate. Any suggestion would be of great help. thanks (3 Replies)
Discussion started by: ramkumar_gr
3 Replies
3. Linux
How do i make a library shared
say i have a library a.so which i have just compiled.
I want to make it shared how do i make it
Next Queation is what is the difference between a.so.0 a.so.1 a.so.2 & a.so :rolleyes: (1 Reply)
Discussion started by: wojtyla
1 Replies
4. UNIX for Advanced & Expert Users
can someone explain whether my understanding is correct
lets suppose we have a program that uses library x.
if x is static then the code of x will be part of our program, so if we're going to have 5 executables of our program, then each executable will have x as part of it.
Also, x does not... (2 Replies)
Discussion started by: JamesByars
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am trying to create a shared library from a .c file using
gcc -c -fpic -I/usr/local/include Chksum.C -o Chksum.o
gcc -shared -o libtclcksum.so Chksum.o
when i try to load this shared library libtclcksum.so in tclsh
% load libtclcksum.so
I get the following error:
couldn't load... (1 Reply)
Discussion started by: archana485
1 Replies
6. Solaris
Please tell me how to manage the shared library on solaris 10!
which file to configure the library path?
which environment variable contains these paths ?
how to define the new library path?
thanks all! (2 Replies)
Discussion started by: quyetbm
2 Replies
7. AIX
Hi,
I have a problem about loaded shared libraries. I'm issuing ‘procldd' for a process and AIX shows me the loaded shared libraries. I'm collecting these libraries and counting their size. They were 350MB. After this, I'm issuing ‘ps vx' and I'm seeing that the process takes 130MB from AIX's... (1 Reply)
Discussion started by: jhatzics
1 Replies
8. Red Hat
hi,
while running the below query it gives the shared libraries prmblem,
$ cd /oracle/app/product/fmw/asinst_1/bin/
$ ./opmnctl status
/oracle/app/product/fmw/Oracle_IDM1/opmn/bin/opmn: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: Permission... (0 Replies)
Discussion started by: rahulsword
0 Replies
9. Solaris
Does anyone know whether it is possible to make self contained shared libraries ? (.so files). If so, what is the way to do it ?
---------- Post updated at 08:03 AM ---------- Previous update was at 07:56 AM ----------
On Solaris that is. (6 Replies)
Discussion started by: lkb
6 Replies
10. Programming
This is the first time that I created a dynamic library in linux and although the program works, I do not get the correct information about the library when executing ldd.
I explain the details:
1) Source code:
bye_fn.c:
#include <stdio.h>
#include "hello.h"
void bye (const char*... (9 Replies)
Discussion started by: jose_spain
9 Replies
LEARN ABOUT DEBIAN
fort77
FORT77(1) Linux Programmer's Manual FORT77(1)
NAME
fort77 - invoke f2c Fortran translator transparently, like a compiler
SYNOPSIS
fort77 [-c] [-g] [-v] [-k] [-P] [-cpp] [f2c option ...] [-L directory ...] [gcc-option ...] [link option ...] [-O optlevel] [-o out-
file] [-s] [-w] [-Wx,arg1[,arg2]...] file ...
DESCRIPTION
The fort77 script invokes the f2c command transparently, so it can be used like a real Fortran compiler. It can be used to compile For-
tran, C and assembler code, and to link it with the f2c libraries.
File arguments ending with .f are compiled as Fortran source files. Files which end with .P are passed through to f2c, and files ending
with .F are passed to the C preprocessor (invoked as "/lib/cpp -traditional") first. Any switches passed via -D will be passed to the pre-
processor. If the translation is successful, the resulting C files will be passed to cc for translation into an object file. Files ending
in .c, .C, .cc, .i, .s, .S, .m, .cc or .cxx are passed to the GNU C compiler directly; see gcc(1). All other files are passed to the
linker.
OPTIONS
-c Supress linking and produce an object ( .o ) file from each source file.
-g Include debugging information. -v Be verbose; supplying this twice will also tell the C compilers etc to be verbose.
-k Keep the C files generated by f2c around.
-cpp Pass Fortran code through the C preprocessor, as if filenames ended in .F.
-P Generate f2c .P files.
-Ldirectory
Include directory in the search for libraries in the final linking stage.
-o outfile
Send output to outfile.
-trapuv Have f2c generate code to trap uninitialized values.
-Wx,arg1[,arg2...]
Pass the argument[s] argi through to the subprocess x, where x can assume one of the following values: f for the f2c step, p for
the preprocessing step, c for the C compiler, a for the assembler (this is actually passed to the C compiler, too), and l for the
linker. As an example, defining a preprocessor constant for the C compilation step would be done with -Wc,-DUNIX=1. Specifying
the -f option to f2c would be done via -Wf,-f.
f2c option
fort77 passes through almost all f2c options: -C, -U, -u, -a, -E, -h, -P, -R, -r, -z, -I2, -I4, -onetrip, -!c, -!l, -!P, -!R, -ext,
-!bs, -W[n], -trapuv, -w8, -r8 and -w66.
gcc options
The following options are passed through to gcc: -f*, -W*, -U*, -A*, -m*, -S, -E, -v, -x, -pipe, -o, -I, -V, -b*, -p, -pg.
linker option
The options passed to the linking stage are -static, -shared, -v, -V, and -symbolic.
BUGS
To make debugging work, you need to set a breakpoint at MAIN__ before you start.
f2c This script automatically supplies the -I. option to f2c. Older versions of f2c may not support this.
This script is for the interaction of gcc and f2c; using it with another compiler will probably require modification.
The fort77 script does not strictly conform to Posix.2, because it acceppts long options with one leading slash. This is done for gcc com-
patibility.
SEE ALSO
f2c(1), cc(1), as(1), ld(1)
AUTHOR
Thomas Koenig, ig25@rz.uni-karlsruhe.de
Linux Nov 1996 FORT77(1)