X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4B474A8E.6050807@towo.net>
Date: Fri, 08 Jan 2010 16:09:02 +0100
From: Thomas Wolff <towo AT towo DOT net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: cygwin-apps AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] updated: orpie-1.5.1-2
References: <announce DOT it3ek51ib2uuta0qmqj48dh488cv29h0jj AT 4ax DOT com> 	 <4B471746 DOT 2040602 AT towo DOT net> <416096c61001080447w1794cc4cr519c41945173d28d AT mail DOT gmail DOT com> <mtgek555n1sf7sqh34ri02kv2otet4t9ln AT 4ax DOT com>
In-Reply-To: <mtgek555n1sf7sqh34ri02kv2otet4t9ln@4ax.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

[ last section relevant for cygwin-apps, not sure whether this was an 
acceptable excuse for cross-posting :-\  ]

Andrew Schulman wrote:
>> 2010/1/8 Thomas Wolff:
>>     
>>>
>>> Works well in the cygwin console; in mintty, however, it just reports:
>>> /usr/bin/orpie.exe: error while loading shared libraries: ?: cannot open
>>> shared object file: No such file or directory
>>> It *does* work in a cygwin 1.5 mintty, though, so it's not a limitation
>>> related to Windows console/pty incompatibilites, unless something got
>>> changed here.
>>>       
>> Same here, but only in an existing mintty window. Orpie works fine in
>> a newly opened mintty.
>>
>> And the difference appears to be in the PATH: in the new session it
>> has an additional /usr/lib/lapack at the end.
>>     
>
> OK, sorry about this.  I think a few things are conspiring:
>
> * cygport didn't tell me that orpie depends on lapack, and I had forgotten
> that it does, and stupidly removed it from setup.hint.
>   
That's strange as lapack was installed with orpie for me.

> * In order for lapack to work, you have to have /usr/lib/lapack in your
> $PATH.  IMO that's a bug, but the lapack maintainer told me a couple of
> years ago that it's a wontfix.
>   
This is done by /etc/profile.d/lapack0.*sh which also got installed, so 
as Andy pointed out, it works if only you start a new login shell.

> So Thomas, please try this:  install lapack, and add /usr/bin/lapack to
> your $PATH.  Then retry orpie, and let me know if that fixes the problem.
>   
Thanks, but it was fixed already as mentioned above, no need to amend 
personal PATH settings.


I'm just thinking whether it's worth to handle this situation in 
general, something like:
If a package (lapack actually, in this case) modifies the profile 
environment so shell restarts are needed,
there might be a package option to have setup present a popup warning...
But maybe it's not worth the effort, given the general advice "don't 
start setup from shell" (which I regularly violate) which - on the other 
hand - is somewhat similar to the unpleasant "Close all applications 
before installing" of typical Windows installers...

Thanks anyway for this nice package.
Thomas

--
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