This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Doubtful about unison
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 1 Mar 2011 07:20:26 +0000
- Subject: Re: Doubtful about unison
- References: <ikf9e3$ub2$1@dough.gmane.org> <ikfe1p$f00$1@dough.gmane.org> <ikgf2f$vtm$1@dough.gmane.org> <fggnm61cfbkp0fm6jm0lvrns74bk56bls4@4ax.com> <ikgjlh$tk7$1@dough.gmane.org> <aamnm61uhbmgbrq007c6oag7cd7n9hpdt2@4ax.com> <ikgt6p$ubn$1@dough.gmane.org> <4D6BFD09.8020600@gmx.de>
On 28 February 2011 19:52, Matthias Andree wrote:
> Am 28.02.2011 20:31, schrieb Olivier Lefevre:
>
>> Yes but no danger here: it dies right away with an error popup that
>> says "The program entry point [I am translating from the german; I
>> might be a little off] "__ctype_ptr__" was not found in cygwin1.dll"
>>
>> Looks like it was wrongly linked or compiled. Or maybe there's a
>> mismatch between what it was complied against and my own Cygwin? I
>
> No, instead, it was wrongly installed by yourself.
>
>> only just installed Unison but I haven't updated anything else, least
>> of all Cygwin base (which has gone wrong for me in the past), in many
>> months.
>
> Which is the problem: the unison command was compiled against a newer
> cygwin1.dll than yours.
To be fair, setup.exe ought to be able to resolve or warn about such
version dependencies. Unfortunately the infrastructure for that isn't
in place, as it would require version requirements to be expressed in
packages' setup.hint files (rather than in their READMEs, as they are
at the moment).
Andy
--
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