Recent cygport and cygwin-specific READMEs [Was: Re: GCC-4.7.2-2: Go/No-go?]
Andy Koppe
andy.koppe@gmail.com
Sun Apr 14 20:22:00 GMT 2013
On 14 April 2013 04:45, Yaakov (Cygwin/X) wrote:
> On 2013-04-13 00:55, Andy Koppe wrote:
>>
>> Cygport prints ">>> mintty requires:" at the end, which is correct as
>> it doesn't require anything beyond the Cygwin DLL, but there's no
>> setup.hint.
>
>
> As Corinna already pointed out, this is a sign that the setup.hint
> generation succeeded, and in this case the requires: line is blank (and
> rightfully so, since mintty uses only cygwin1.dll and Win32 APIs). If it
> had failed, there would have been a warning about a missing .hint file
> instead.
>
>
>> I've also tried installing cygport from git master but got this after
>> running ./autogen.sh && make:
>>
>> make: *** No rule to make target `data/gnuconfig/config.guess', needed
>> by `all-am'. Stop.
>
>
> This is one quirk of git that I've never understood: git clone does not
> expand submodules by default without the --recursive flag. Run "git
> submodule update --init" to get these after a clone.
Yep, that did it.
> BTW:
>
>> _CYGPORT_RESTRICT_postinst_doc_=1
>
>
> Variables beginning with an underscore are for internal use only. This
> should be RESTRICT=postinstall-doc. But what problem did you encounter to
> necessitate this?
Took me a while to remember, but it's there to stop the LICENSE file
from being installed, because that's the same as
/usr/share/doc/common-licenses/GPL-3.0. RESTRICT=postinstall-doc
didn't do this, but RESTRICT=postinst_doc does.
Thanks,
Andy
More information about the Cygwin-apps
mailing list