comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: IDLWAVE and call-external
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDLWAVE and call-external [message #50434] Mon, 02 October 2006 09:58 Go to previous message
JD Smith is currently offline  JD Smith
Messages: 850
Registered: December 1999
Senior Member
On Mon, 02 Oct 2006 01:54:25 -0700, Nicola wrote:

>
>> I'd guess paths as well. Are you relying on the .so file to be in the
>> current path? IDLWAVE doesn't do anything to affect this, so it must be
>> path setup. Try starting Emacs from a shell where it is working, and
>> attempt again. It *should* work.
>>
>> JD
>
> You are right.....
> Actually starting emacs from a shell all works fine whereas starting from
> start bar (KDE envirorment) does not work properly. I can't understand the
> reason (the library is incluced in my LD_LIBRARY_PATH in my .bash_profile
> file) but maybe this is not more a question for this newsgroup (but if
> someone has some suggestion is welcommed!) Regards


Because starting from the command bar doesn't inherit the shell
environment variable LD_LIBRARY_PATH... it never even runs the shell, just
the Emacs executable directly.

Try putting LD_LIBRARY_PATH in your .login and logging out and in. The
entire session should inherit the variable then. You can always check
within IDL like:

IDL> print,getenv('LD_LIBRARY_PATH')

JD
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Still having problems with combining a contour and a line plot objects
Next Topic: 4D visualization

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:47:01 PDT 2025

Total time taken to generate the page: 0.00380 seconds