On Tue, 5 Aug 2003, David Thompson wrote:
The dxexec is not thread safe, so I would suggest just trying to
link it with xlC not xlC_r. I think you're on the right track and
some combination with the c++ compiler is going to solve your
problem.
I tried compiling dxexec with xlC. I got the
Hi,
Thanks for your e-mail.
You may want to look at our autoconf template for building modules
that we contributed as mentioned on opendx.org.
Yes, we based our modules on your template. Thank you - it is very
useful. The template works great for C modules. Our module, however,
is written
I presume you mean the module, not dxexec. Yes, I tried a few things
for exporting, all to no avail: -bexpall, -bexpfull, an export
file (-bE:file_name) with only DXEntry and the module name,
m_ImportHDF5Field, and finally I made libtool generate an export
file for me.
Actually, I meant the
You may want to look at our autoconf template for building modules
that we contributed as mentioned on opendx.org. Also, you need to
make sure that you export the symbols when building the dxexec for
AIX. I remember once having a similar problem and it was because the
-bE was not included when
Hi,
Last week I sent you an e-mail about my problem with running a
loadable C++ module on AIX
(http://opendx.npaci.edu/mail/opendx-dev/2003.07/msg00079.html). So
far I have not resolved the problem. I am writing again to report my
further problems and to ask you for help.
As the module did not
