From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
Date: Fri, 21 Feb 2020 02:18:00 -0000 [thread overview]
Message-ID: <CAD8GWst5LGjE3iP8HLnnzARMiqONrUy=Fph95O9gPZTZZVgofQ@mail.gmail.com> (raw)
In-Reply-To: <20200221110600.adf918ed5dbc4fce5a1067f3@nifty.ne.jp>
On 2/20/20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 20:48:17 -0500
> Lee wrote:
>> On 2/20/20, Takashi Yano wrote:
>> > On Thu, 20 Feb 2020 16:28:26 -0500
>> > Lee wrote:
>> >> For whatever it's worth, the only problem I've noticed with 3.1.4 was
>> >> ansi control character handling and that was fixed by importing this
>> >> bit into the registry:
>> >>
>> >> -------------
>> >> Windows Registry Editor Version 5.00
>> >>
>> >> [HKEY_CURRENT_USER\Console]
>> >> "VirtualTerminalLevel"=dword:00000001
>> >> -------------
>> >
>> > In what situation is registry modification obove necessary?
>>
>> see http://cygwin.com/ml/cygwin/2020-01/msg00217.html
>
> I cannot reproduce that. Without setting VirtualTerminalLevel,
> I got:
> [yano@Express5800-S70 ~...build/cmake]$ cmake ../..
> -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr/local
> -DBUILD_SHARED_LIB:BOOL=YES -DTIDY_RC_NUMBER=next.2020.01.24
> -- The C compiler identification is GNU 7.4.0
> -- The CXX compiler identification is GNU 7.4.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++.exe
> -- Check for working CXX compiler: /usr/bin/c++.exe -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- *** Debug Logging is NOT enabled.
> -- *** Building support for runtime configuration files.
> -- *** Also building DLL library SHARED, version 5.7.28, date 2019.07.08
> -- *** Generating man tidy.1 custom commands...
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /home/yano/tidy/tidy-html5/build/cmake
> [yano@Express5800-S70 ~...build/cmake]$ make
> Scanning dependencies of target tidy-share
> [ 1%] Building C object CMakeFiles/tidy-share.dir/src/access.c.o
> [ 3%] Building C object CMakeFiles/tidy-share.dir/src/attrs.c.o
> [ 5%] Building C object CMakeFiles/tidy-share.dir/src/istack.c.o
> [ 7%] Building C object CMakeFiles/tidy-share.dir/src/parser.c.o
> [ 8%] Building C object CMakeFiles/tidy-share.dir/src/tags.c.o
> [ 10%] Building C object CMakeFiles/tidy-share.dir/src/entities.c.o
> [ 12%] Building C object CMakeFiles/tidy-share.dir/src/lexer.c.o
> [ 14%] Building C object CMakeFiles/tidy-share.dir/src/pprint.c.o
> [ 16%] Building C object CMakeFiles/tidy-share.dir/src/charsets.c.o
> [ 17%] Building C object CMakeFiles/tidy-share.dir/src/clean.c.o
> [ 19%] Building C object CMakeFiles/tidy-share.dir/src/message.c.o
> [ 21%] Building C object CMakeFiles/tidy-share.dir/src/config.c.o
> [ 23%] Building C object CMakeFiles/tidy-share.dir/src/alloc.c.o
> [ 25%] Building C object CMakeFiles/tidy-share.dir/src/attrdict.c.o
> [ 26%] Building C object CMakeFiles/tidy-share.dir/src/buffio.c.o
> [ 28%] Building C object CMakeFiles/tidy-share.dir/src/fileio.c.o
> [ 30%] Building C object CMakeFiles/tidy-share.dir/src/streamio.c.o
> [ 32%] Building C object CMakeFiles/tidy-share.dir/src/tagask.c.o
> [ 33%] Building C object CMakeFiles/tidy-share.dir/src/tmbstr.c.o
> [ 35%] Building C object CMakeFiles/tidy-share.dir/src/utf8.c.o
> [ 37%] Building C object CMakeFiles/tidy-share.dir/src/tidylib.c.o
> [ 39%] Building C object CMakeFiles/tidy-share.dir/src/mappedio.c.o
> [ 41%] Building C object CMakeFiles/tidy-share.dir/src/gdoc.c.o
> [ 42%] Building C object CMakeFiles/tidy-share.dir/src/language.c.o
> [ 44%] Building C object CMakeFiles/tidy-share.dir/src/messageobj.c.o
> [ 46%] Building C object CMakeFiles/tidy-share.dir/src/sprtf.c.o
> [ 48%] Linking C shared library cygtidy-5.dll
> [ 48%] Built target tidy-share
> Scanning dependencies of target tidy-static
> [ 50%] Building C object CMakeFiles/tidy-static.dir/src/access.c.o
> [ 51%] Building C object CMakeFiles/tidy-static.dir/src/attrs.c.o
> [ 53%] Building C object CMakeFiles/tidy-static.dir/src/istack.c.o
> [ 55%] Building C object CMakeFiles/tidy-static.dir/src/parser.c.o
> [ 57%] Building C object CMakeFiles/tidy-static.dir/src/tags.c.o
> [ 58%] Building C object CMakeFiles/tidy-static.dir/src/entities.c.o
> [ 60%] Building C object CMakeFiles/tidy-static.dir/src/lexer.c.o
> [ 62%] Building C object CMakeFiles/tidy-static.dir/src/pprint.c.o
> [ 64%] Building C object CMakeFiles/tidy-static.dir/src/charsets.c.o
> [ 66%] Building C object CMakeFiles/tidy-static.dir/src/clean.c.o
> [ 67%] Building C object CMakeFiles/tidy-static.dir/src/message.c.o
> [ 69%] Building C object CMakeFiles/tidy-static.dir/src/config.c.o
> [ 71%] Building C object CMakeFiles/tidy-static.dir/src/alloc.c.o
> [ 73%] Building C object CMakeFiles/tidy-static.dir/src/attrdict.c.o
> [ 75%] Building C object CMakeFiles/tidy-static.dir/src/buffio.c.o
> [ 76%] Building C object CMakeFiles/tidy-static.dir/src/fileio.c.o
> [ 78%] Building C object CMakeFiles/tidy-static.dir/src/streamio.c.o
> [ 80%] Building C object CMakeFiles/tidy-static.dir/src/tagask.c.o
> [ 82%] Building C object CMakeFiles/tidy-static.dir/src/tmbstr.c.o
> [ 83%] Building C object CMakeFiles/tidy-static.dir/src/utf8.c.o
> [ 85%] Building C object CMakeFiles/tidy-static.dir/src/tidylib.c.o
> [ 87%] Building C object CMakeFiles/tidy-static.dir/src/mappedio.c.o
> [ 89%] Building C object CMakeFiles/tidy-static.dir/src/gdoc.c.o
> [ 91%] Building C object CMakeFiles/tidy-static.dir/src/language.c.o
> [ 92%] Building C object CMakeFiles/tidy-static.dir/src/messageobj.c.o
> [ 94%] Building C object CMakeFiles/tidy-static.dir/src/sprtf.c.o
> [ 96%] Linking C static library libtidys.a
> [ 96%] Built target tidy-static
> Scanning dependencies of target tidy
> [ 98%] Building C object CMakeFiles/tidy.dir/console/tidy.c.o
> [100%] Linking C executable tidy.exe
> [100%] Built target tidy
> Scanning dependencies of target man
> Generate /home/yano/tidy/tidy-html5/build/cmake/tidy-help.xml
> Generate /home/yano/tidy/tidy-html5/build/cmake/tidy-config.xml
> Generate tidy.1
> [100%] Built target man
>
> Isn't this right behaviour?
yes, that looks good.
I had that weird
-- Build files have been written to: /source/tidy/tidy-html5/build/cmake
e
[ 1%] o
[ 3%]
[ 5%] o
[ 7%]
[ 8%] o
[ 10%] o
that didn't happen after making the registry change -- and that was
the only change I made.
I'll try backing out the registry change & see if it still happens.
Lee
>
> --
> Takashi Yano <takashi.yano@nifty.ne.jp>
>
> --
> 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
>
>
--
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
next prev parent reply other threads:[~2020-02-21 2:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 13:50 KARL BOTTS
2020-02-20 18:50 ` Andrey Repin
2020-02-20 21:28 ` Lee
2020-02-21 0:20 ` Takashi Yano
2020-02-21 1:16 ` Brian Inglis
2020-02-21 1:27 ` Takashi Yano
2020-02-21 1:35 ` Brian Inglis
2020-02-21 1:50 ` Takashi Yano
2020-02-21 2:13 ` Lee
2020-02-21 2:01 ` Lee
2020-02-21 1:49 ` Lee
2020-02-21 2:06 ` Takashi Yano
2020-02-21 2:18 ` Lee [this message]
2020-02-21 2:47 ` Lee
2020-02-21 9:41 ` Takashi Yano
2020-02-21 11:13 ` Paul Moore
2020-02-21 14:26 ` Lee
2020-02-21 21:34 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD8GWst5LGjE3iP8HLnnzARMiqONrUy=Fph95O9gPZTZZVgofQ@mail.gmail.com' \
--to=ler762@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).