Login or Register to Ask a Question and Join Our Community


OS X (Apple)

Linking to a shared library

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) Linking to a shared library
# 1  
Old 02-18-2011
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 -Wl,"-rpath=/PATH_TO_LIB_FILE" to my compiler (mpicc). This doesn't work in OS X however. How can I hardcode the path into my executable?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

Add shared members from library to same library in a different directory

I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message. add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies

2. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

3. 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

4. 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

5. Shell Programming and Scripting

How to change a Makefile from building static library to shared library?

Hi: I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library) Thanks. (1 Reply)
Discussion started by: cpthk
1 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. 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

8. 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

9. Programming

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... (6 Replies)
Discussion started by: laho
6 Replies

10. 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
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

tk_main

Tk_Main(3)						       Tk Library Procedures							Tk_Main(3)

__________________________________________________________________________________________________________________________________________________

NAME

       Tk_Main - main program for Tk-based applications

SYNOPSIS

       #include <tk.h>

       Tk_Main(argc, argv, appInitProc)

ARGUMENTS

       int argc (in)				  Number of elements in argv.

       char *argv[] (in)			  Array of strings containing command-line arguments.

       Tcl_AppInitProc *appInitProc (in)	  Address  of  an  application-specific  initialization procedure.  The value for this argument is
						  usually Tcl_AppInit.
_________________________________________________________________

DESCRIPTION

       Tk_Main acts as the main program for most Tk-based applications.  Starting with Tk 4.0 it is not called main anymore because it is part	of
       the Tk library and having a function main in a library (particularly a shared library) causes problems on many systems.	Having main in the
       Tk library would also make it hard to use Tk in C++ programs, since C++ programs must have special C++ main functions.

       Normally each application contains a small main function that does nothing but invoke Tk_Main.  Tk_Main then does all the work of  creating
       and running a wish-like application.

       When  it  is  has  finished  its own initialization, but before it processes commands, Tk_Main calls the procedure given by the appInitProc
       argument.  This procedure provides a "hook" for the application to perform its own initialization, such	as  defining  application-specific
       commands.  The procedure must have an interface that matches the type Tcl_AppInitProc:
	      typedef int Tcl_AppInitProc(Tcl_Interp *interp);
       AppInitProc is almost always a pointer to Tcl_AppInit; for more details on this procedure, see the documentation for Tcl_AppInit.

KEYWORDS

       application-specific initialization, command-line arguments, main program

Tk									4.0								Tk_Main(3)