Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Fri, 19 Sep 2003 09:05:22 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Jan Nieuwenhuizen cc: cygwin AT cygwin DOT com Subject: Re: Packaging error in the latest libguile12-1.6.4-12 ? In-Reply-To: <87d6dxt4rn.fsf@peder.flower> Message-ID: References: <8765jp84e2 DOT fsf AT vzell-de DOT de DOT oracle DOT com> <87d6dxt4rn DOT fsf AT peder DOT flower> Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 19 Sep 2003, Jan Nieuwenhuizen wrote: > Volker Zell writes: > > > libguile-srfi-srfi-13-14-v-1.la > > libguile-srfi-srfi-4-v-1.la > > libguilereadline-v-12.la > > > > whereas they should be instead under /usr/lib (in the package > > guild-devel-1.6.4-12) I think. > > No, this is correct. These are dlopened and need to be in PATH. Try: > > guile -c '(use-modules (srfi srfi-4) (srfi srfi-13) (srfi srfi-14))' > > Jan. Aren't the names a bit misleading, then? The .la files are supposed to be libtool library files, i.e., plain text. If they are dlopened, they should be named .dll, right? Or am I missing something? It's ok to keep dlls in one directory (or even package), and import libs (.la) in another (as long as the .la files reflect this fact). In fact, since there's a guile-devel package, shouldn't the libtool import libs belong there? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/