g95: undefined symbol

From: Dominique Orban (Dominique.Orban_at_polymtl.ca)
Date: 12/16/04 

Date: Thu, 16 Dec 2004 13:32:27 GMT

Hello,

I am building shared libraries to be loaded from within Python. I don't
believe my question is Python-specific and I am most likely missing
something obvious. The libraries are made of F77, F90 and C source code.

library1.so contains only F77 and F90 code and this F90 code has defined
modules.

library2.so contains an F90 interface to the code in library1.so and a C
interface to Python. When i compile it, i specify where to find module
information.

All compiles well and runs well with the Intel compiler.
All compiles well with g95, but when i try to run an example using
library2.so, i get

        undefined symbol '_g95_section_info'

'nm' reveals that this symbol is indeed undefined in library2.so, but is
defined in library1.so.

As an additional clue, when i merge all the sources making up
library1.so and library2.so into a single library, all compiles and runs
well. I can't reasonably keep them merged though, for licensing reasons.

I must have missed something obvious, but what it is just isn't striking
me. I would really appreciate any help.

Thanks in advance,
Dominique

Relevant Pages

  • Re: Pythons garbage collection was Re: Python reliability
    ... >>> Has anyone looked into using a real GC for python? ... A strategy based on PURE reference counting just ... > extensions, and with correct implementations, both refcounting and GC are ... > Lucky those existing C libraries were written to use python's refcounting! ...
    (comp.lang.python)
  • Re: Python component model
    ... other libraries. ... application domains like Scientific Python. ... dearth of Web frameworks as a benefit, I think you'd see less activity ... near-blessing of Django: it's almost nonsensical. ...
    (comp.lang.python)
  • Re: Why Lisp is not popular with average programmers
    ... are multiple implementations of Common Lisp, the "fragmentation" of which you speak can simply not exist in in Common Lisp ... ... the implementations differ on these. ... But, there are compatibility libraries that you can use rather than your implementation's primitives, and have your code portable across implementations. ... Python seems horribly "fragmented" as well. ...
    (comp.lang.lisp)
  • Re: How Common Lisp sucks
    ... web server up and running using Python takes substantially less effort ... You're right, it's not an advantage of the language itself, but it's ... the effort required to locate the right libraries ... I think a lot of the advances that happen in programming languages ...
    (comp.lang.lisp)
  • Re: Why Lisp is not popular with average programmers
    ... If I want SMTP client support in my script, Python has it out of the box. ... In Python, the whole thing seems packaged together into a coherent whole, whereas in Lisp, it seems more like an exercise in trying to put square pegs in round holes. ... Libraries does not a language make. ...
    (comp.lang.lisp)