Sponsored Content
Top Forums Programming Linking problem while linking to shared library Post 48633 by laho on Friday 12th of March 2004 03:49:30 AM
Old 03-12-2004
Question Linking problem while linking to shared library

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 running on
SunOS RELEASE: 5.8
ld: Software Generation Utilities - Solaris-ELF (4.0)
gcc, g++ - GNU project C and C++ Compiler (gcc-2.95)

Can anyone please help me!!!

BR Lars
 

10 More Discussions You Might Find Interesting

1. Programming

Runtime Linking shared Objects

I'm runtime linking (dlopen and dlsym) to a shared object (library) I've created and after a number of function calls into the library the program core dumps (Illegal operation). This only occurs during runtime linking. If I use the same library and dynamically link during compile time everything... (3 Replies)
Discussion started by: dneely
3 Replies

2. Programming

Linking with shared objects

hi all ! Do I need all the shared objects to be present while compiling my code which has reference to a only one shared object, which in turn refers to another shared object. for example I want to compile example.c which refers to sample.so sample.so has refrence to anothersample.so do... (2 Replies)
Discussion started by: disclaimer
2 Replies

3. UNIX for Dummies Questions & Answers

Link error while linking a shared library in unix

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

4. AIX

linking problem

hello, Is the code compiled under Visual Age C++ Broker (a third party library) - can be used to link against a code compiled from gcc compiler. I have a problem in building xerces in AIX Please reply. Regards, Parthasarathy (1 Reply)
Discussion started by: Parthasarathy
1 Replies

5. Solaris

g++ linking problem...

I use Solaris 10, compiling with a custom g++ (3.4.6) and GNU binutils (2.17). Things have gone well on two different systems, but when I tried moving to a third, it all fell over. Basically, it is now using the CC linker, but I need to use options not available to it. I believe I have found the... (0 Replies)
Discussion started by: Elric of Grans
0 Replies

6. AIX

Help while linking the library in AIX

Hi, I have one library(libfoo.a) that is folder /home/xyz and my c program is in /home/xyz/cprog. Whenever I issue cc command cc -o test test.c -lfoo , i get the error /usr/bin/ld: cannot find -lfoo. echo $PATH has already listing of /home/xyz variable, even LIBPATH also has same entry... (0 Replies)
Discussion started by: rishisoft1
0 Replies

7. Programming

Library linking with GMP

I am trying to set up the gnu multiple precision arithmetic library for some c++ programming I have to do. I am using a system with mac osx 10.6.3 and do NOT have root user access. I'm trying to use gmp 5.0.1. Since I don't have root user access, I had to install to a different directory Thus... (3 Replies)
Discussion started by: bluejayek
3 Replies

8. Programming

Compiling and linking Shared Libraries.

I have one C program which contains a function call. I have been given some .so and .h files. I want to know how to compile and link the c program with .so files. I tried following: $ gcc My_program.c libCommon.so My_program.c: In function āmainā: My_program.c:11: warning: parameter names... (3 Replies)
Discussion started by: junaid.nehvi
3 Replies

9. OS X (Apple)

Linking to a shared library

I'm trying to get Valgrind to work with an openmpi application in OS X. However I want to hardcode the path to a shared library called libmpiwrap-amd64-darwin.so into my application so that it is available at runtime. In Linux this is relatively simple, I would just add the option... (0 Replies)
Discussion started by: Valgrinder
0 Replies

10. Programming

Linking problem

Hi! We recently updated the server (server is a big word, it's really just a desktop with Ubuntu that we access with ssh) on which we compile our code. Since the update my code won't compile. The linker is complaining about missing references from almost all .so that I'm linking from. It... (0 Replies)
Discussion started by: philippevk
0 Replies
TCC(1)																	    TCC(1)

NAME
tcc - Tiny C Compiler SYNOPSIS
usage: tcc [options] [infile1 infile2...] [-run infile args...] DESCRIPTION
TCC options are a very much like gcc options. The main difference is that TCC can also execute directly the resulting program and give it runtime arguments. Here are some examples to understand the logic: "tcc -run a.c" Compile a.c and execute it directly "tcc -run a.c arg1" Compile a.c and execute it directly. arg1 is given as first argument to the "main()" of a.c. "tcc a.c -run b.c arg1" Compile a.c and b.c, link them together and execute them. arg1 is given as first argument to the "main()" of the resulting program. "tcc -o myprog a.c b.c" Compile a.c and b.c, link them and generate the executable myprog. "tcc -o myprog a.o b.o" link a.o and b.o together and generate the executable myprog. "tcc -c a.c" Compile a.c and generate object file a.o. "tcc -c asmfile.S" Preprocess with C preprocess and assemble asmfile.S and generate object file asmfile.o. "tcc -c asmfile.s" Assemble (but not preprocess) asmfile.s and generate object file asmfile.o. "tcc -r -o ab.o a.c b.c" Compile a.c and b.c, link them together and generate the object file ab.o. Scripting: TCC can be invoked from scripts, just as shell scripts. You just need to add "#!/usr/local/bin/tcc -run" at the start of your C source: #!/usr/local/bin/tcc -run #include <stdio.h> int main() { printf("Hello World "); return 0; } TCC can read C source code from standard input when - is used in place of infile. Example: echo 'main(){puts("hello");}' | tcc -run - OPTIONS
-v Display current TCC version, increase verbosity. -print-search-dirs Print the name of the configured installation directory and a list of program and library directories tcc will search. -c Generate an object file. -o outfile Put object file, executable, or dll into output file outfile. -Bdir Set the path where the tcc internal libraries can be found (default is PREFIX/lib/tcc). -bench Output compilation statistics. -run source [args...] Compile file source and run it with the command line arguments args. In order to be able to give more than one argument to a script, several TCC options can be given after the -run option, separated by spaces. Example: tcc "-run -L/usr/X11R6/lib -lX11" ex4.c In a script, it gives the following header: #!/usr/local/bin/tcc -run -L/usr/X11R6/lib -lX11 #include <stdlib.h> int main(int argc, char **argv) { ... } Preprocessor options: -Idir Specify an additional include path. Include paths are searched in the order they are specified. System include paths are always searched after. The default system include paths are: /usr/local/include, /usr/include and PREFIX/lib/tcc/include. (PREFIX is usually /usr or /usr/local). -Dsym[=val] Define preprocessor symbol sym to val. If val is not present, its value is 1. Function-like macros can also be defined: -DF(a)=a+1 -Usym Undefine preprocessor symbol sym. Compilation flags: Note: each of the following warning options has a negative form beginning with -fno-. -funsigned-char Let the "char" type be unsigned. -fsigned-char Let the "char" type be signed. -fno-common Do not generate common symbols for uninitialized data. -fleading-underscore Add a leading underscore at the beginning of each C symbol. Warning options: -w Disable all warnings. Note: each of the following warning options has a negative form beginning with -Wno-. -Wimplicit-function-declaration Warn about implicit function declaration. -Wunsupported Warn about unsupported GCC features that are ignored by TCC. -Wwrite-strings Make string constants be of type "const char *" instead of "char *". -Werror Abort compilation if warnings are issued. -Wall Activate all warnings, except -Werror, -Wunusupported and -Wwrite-strings. Linker options: -Ldir Specify an additional static library path for the -l option. The default library paths are /usr/local/lib, /usr/lib and /lib. -lxxx Link your program with dynamic library libxxx.so or static library libxxx.a. The library is searched in the paths specified by the -L option. -shared Generate a shared library instead of an executable. -soname name set name for shared library to be used at runtime -static Generate a statically linked executable (default is a shared linked executable). -rdynamic Export global symbols to the dynamic linker. It is useful when a library opened with "dlopen()" needs to access executable symbols. -r Generate an object file combining all input files. -Wl,-Ttext,address Set the start of the .text section to address. -Wl,--oformat,fmt Use fmt as output format. The supported output formats are: "elf32-i386" ELF output format (default) "binary" Binary image (only for executable output) "coff" COFF output format (only for executable output for TMS320C67xx target) -Wl,-rpath=path Set custom library search path Debugger options: -g Generate run time debug information so that you get clear run time error messages: " test.c:68: in function 'test5()': dereferencing invalid pointer" instead of the laconic "Segmentation fault". -b Generate additional support code to check memory allocations and array/pointer bounds. -g is implied. Note that the generated code is slower and bigger in this case. Note: -b is only available on i386 for the moment. -bt N Display N callers in stack traces. This is useful with -g or -b. Note: GCC options -Ox, -fx and -mx are ignored. SEE ALSO
gcc(1) AUTHOR
Fabrice Bellard 2012-07-21 TCC(1)
All times are GMT -4. The time now is 03:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy