cosign-discuss at umich.edu
general discussion of cosign development and deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
thanks for that, I assumed something like that was the reason. I have no
problems with libtool being packaged up. I was getting a problem when
generating it from the m4 but I think was because it had /r/n in it because
I looked at in windows (silly me).
Information Technology Systems and Services
The University of Auckland
Phone: +64 9 3737 599 extn 86499
Mobile: +64 21 757 096
From: Mark Montague [mailto:markmont@xxxxxxxxx]
Sent: Thursday, 22 April 2004 2:16 a.m.
To: Brett Lomas
Cc: 'Cosign Discussion'
Subject: Re: Libtool
On Wed, 21 Apr 2004, Brett Lomas wrote:
> just a question, why do you build a libtool in libsnet for the main cosign
> distro? Is it because libtool is not installed on all OS?
I'm the person that twisted the cosign developers' arms into
including libtool for libsnet, so let me try to answer your
libtool indeed does not come standard with all OSs (e.g., Solaris)
and requiring everyone to install libtool first would be an obstacle to
installing cosign. Also, if libtool is installed on the system
already, it may or may not be a recent enough version for cosign's
needs. But, most importantly, building libtool is what just about
all other open source and GNU packages that use libtool do. Finally,
for cosign/libsnet, libtool has been included with cosign and libsnet
in the manner specified by the libtool manual. See
Is the way cosign/libset is using libtool causing a problem for you
in your environment? Is there anything we can do to help?
LS&A Information Technology
The University of Michigan