Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
To: cygwin AT cygwin DOT com
Subject: Re: guile package problem
References: <091220051503 DOT 5702 DOT 432598CD000274CA0000164622007601800A050E040D0C079D0A AT comcast DOT net>
From: Jan Nieuwenhuizen <janneke AT gnu DOT org>
Date: Sat, 24 Sep 2005 19:45:54 +0200
In-Reply-To: <091220051503.5702.432598CD000274CA0000164622007601800A050E040D0C079D0A@comcast.net> (Eric  Blake's message of "Mon, 12 Sep 2005 15:03:41 +0000")
Message-ID: <87u0ga9x65.fsf@peder.flower>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes

Eric Blake writes:

> Since I am now the sharutils maintainer, I wanted to try building
> sharutils from CVS.  But bootstrapping a fresh checkout requires
> autogen, so I gave a try at compiling autogen-5.7.2.  Compilation
> failed because guile-1.6.7-1 has a broken /usr/lib/libguile.la,
> generated by libtool 1.5.10 (it references cygguile.dll.a instead
> of libguile.dll.a, and has a dependency on
> /home/mingw/cygwin/root/usr/lib/libguile-ltdl.la, which does not
> exist).  Now that libtool 1.5.20 is available, can guile be repackaged
> to use the newer libtool and fix the packaging bug?

Thanks for the report, I'll have a look.

Jan.

-- 
Jan Nieuwenhuizen <janneke AT gnu DOT org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

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