DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type; q=dns; s=default; b=I7POLz7YHrTB+/xh
	1WDPAqBxQS8HT/umTVIYLkj1x/dBsfUIPt6iI58QrnAvDp5gRIOK0B9gKv0QmMTZ
	JPeaUgR0UY2+ai7octsgPd4Qrv4R2eaaaKMuFO9PPqm9gVal5XNuoCB5XkIWguwB
	YH1rR+U2BiwaAS2FAeL8hqrSja8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: octave: cannot open shared object file: No such file or directory
Date: Sat, 25 Jan 2014 07:36:21 +0100
Lines: 22
Message-ID: <87siscbmai.fsf@Rainer.invalid>
References: <loom.20140125T001029-429@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Paul writes:
> However, I recently started to get the following message when sending 
> expressions to octave:
>
>    /usr/bin/octave-3.6.2.exe: error while loading shared libraries: ?:
>    cannot open shared object file: No such file or directory

I'm almost certain that Octave can't find its lapack libraries.  The
standard profile scripts add this to the very end of the path and
depending on what is in your windows path you may hide them.  There are
also two environment variables (sorry, can't check right now) that need
to be set for lapack to be happy and you may not source the
/etc/profile.d script that sets them depending on how you start bash.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple