Dynamic Linking Problems with Intel Compiler
Jeff Hagelberg
jnh at llnl.gov
Fri Sep 10 12:54:26 EDT 2004
More information about the Python-list mailing list
Fri Sep 10 12:54:26 EDT 2004
- Previous message (by thread): Build a project from the script using popen3
- Next message (by thread): Dynamic Linking Problems with Intel Compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm trying to create a python module which can be used by a python interpreter embedded inside a fortran program I have. To do this, I first created python wrappers for all the functions in my fortran program using f2py. I then start an embedded python interpreter in c code which I link against the fortran program. I invoke the fortran program with a filename containing python code. This file is passed to the c code which passes it on to the python interpreter which executes it, causing the python module to be imported and allowing the python code to control the fortran application. At least, that is the idea. The python module I am creating is called mirandaInternal.so. It contains the python wrappers, but is not linked against object files for the main fortan program. The idea is that those symbols should be resolved at run-time. The problem is that for some reason the symbols are not able to be resolved. I am using gcc to do the c compiling and ifort (the intel fortran compiler) to do the fortran compiling and all of the linking. I have tried using the "-Bdynamic" flag when linking both the executable and the shared library for the module, but that has not seemed to help. Has anyone have any suggestions as to what I need to do to the the dynamic linking to work properly? Thanks in advance, Jeff Hagelberg
- Previous message (by thread): Build a project from the script using popen3
- Next message (by thread): Dynamic Linking Problems with Intel Compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list