Yes, thanks, that's something I hadn't looked into. For legacy reasons, my
code was being built with the option -flat_namespace. I don't remember the
reason why, but many years ago that option was needed for the code to run
on the mac. The code is made up of several shared objects that have
depende
On Wed, Sep 5, 2018 at 4:37 PM, David Grote wrote:
>
> Hi - I have recently come across this problem. On my mac, I build a Fortran
> code, producing a shared object, that I import into Python along with numpy.
> This had been working fine until recently when I started seeing sag faults
> deep insi
Hi Matthew - Do you have any comment in this?
Thanks!
Dave
On Wed, Sep 5, 2018 at 5:01 PM Charles R Harris
wrote:
>
>
> On Wed, Sep 5, 2018 at 5:38 PM David Grote wrote:
>
>>
>> Hi - I have recently come across this problem. On my mac, I build a
>> Fortran code, producing a shared o
On Wed, Sep 5, 2018 at 5:38 PM David Grote wrote:
>
> Hi - I have recently come across this problem. On my mac, I build a
> Fortran code, producing a shared object, that I import into Python along
> with numpy. This had been working fine until recently when I started seeing
> sag faults deep insi
Hi - I have recently come across this problem. On my mac, I build a Fortran
code, producing a shared object, that I import into Python along with
numpy. This had been working fine until recently when I started seeing sag
faults deep inside the Fortran code, usually in Fortran print statements. I
tr
