Re: Request update GCC
On Sat, 24 Jun 2017 19:21:57, Steven Penny wrote: gcc-core, gcc-g++ == - version: 5.4.0-1 - version: 6.3.0-1 [test] - Jonathan Yong (JonY) mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-g++ === - version: 5.4.0-3 - Jonathan Yong (JonY) mingw64-i686-gcc-core, mingw64-i686-gcc-g++ === - version: 5.4.0-4 - Jonathan Yong (JonY) http://cygwin.com/ml/cygwin/2017-06/msg00310.html Now that the issue with readline has been resolved, thanks to great work by Corinna and Eric, I wanted to revist some other of my issues. I am reposting this because it is a new month. Some work was done on this in June and July, but I still do not see even a test version with the mingw64-*-gcc-* packages. I use Cygwin quite a bit, but when I can I prefer to build Windows native versions of programs, this way I can share them without worrying about the Cygwin DLL. Can we please release at least test versions of the mingw64-*-gcc-* packages? -- 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
Re: gawk 4.1.4: CR separate char for CRLF files
On 08/09/2017 06:03 AM, Eric Blake wrote: > On 08/09/2017 03:37 AM, Jannick wrote: > >> Which is a pretty much of a pain when there is no easy fallback solution >> provided in case a major change is applied. ... >> This is - to say the least - unpleasant in the light of what Cygwin claims >> to be, namely 'a large collection of GNU and Open Source tools which provide >> functionality similar to a Linux distribution on Windows' (from the top of >> the start website www.cygwin.com). > > On Linux, nothing strips CR automatically. So on Cygwin, we behave the > same - nothing strips CR automatically on binary mounted data. > > And the fact that the change was made AND ANNOUNCED back in February, > but you are now only 6 months later complaining about it, is telling. It was pointed out to me off-list that my reply can easily be mis-read in a much more negative tone than I intended, so I'm apologizing for coming across as mean (yes, I know, https://cygwin.com/acronyms/#WJM). I think I was trying to emphasize that complaints about the behavior change at the time of the change were expected (and there was indeed a reaction, although I was pleasantly surprised at the time that it was limited to just a few threads, so apparently not many people were negatively impacted - and that's a good thing). But complaints about the behavior after six months are a bit unexpected. But I guess not everyone keeps their software up-to-date on quite as frequent a schedule, so I shouldn't have been as surprised or reacted as harshly. At any rate, my advice continues to be the same: how would you deal with CRLF on a Linux system? That's the ideal way to also deal with it on Cygwin (we used to have gratuitous incompatibilities between the systems where the same command line on Linux did not have the same result as on Cygwin; but the change back in February was to get rid of those incompatibilities, even if it breaks scripts that were unwisely relying on the incompatibilities). -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] Updated: Git v2.14.0-1
Version 2.14.0-1 of Git has been uploaded and should be coming soon to a mirror near you. This update includes the following packages: - git - git-cvs - git-debuginfo - git-email - git-gui - gitk - git-p4 - git-svn This is an update to the latest upstream release. For a full list of the upstream changes in this release, please refer to the upstream changelogs: https://git.kernel.org/cgit/git/git.git/tree/Documentation/RelNotes https://kernel.googlesource.com/pub/scm/git/git.git/+/master/Documentation/RelNotes/ https://github.com/gitster/git/tree/master/Documentation/RelNotes Enjoy! Adam -- 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
Updated: Git v2.14.0-1
Version 2.14.0-1 of Git has been uploaded and should be coming soon to a mirror near you. This update includes the following packages: - git - git-cvs - git-debuginfo - git-email - git-gui - gitk - git-p4 - git-svn This is an update to the latest upstream release. For a full list of the upstream changes in this release, please refer to the upstream changelogs: https://git.kernel.org/cgit/git/git.git/tree/Documentation/RelNotes https://kernel.googlesource.com/pub/scm/git/git.git/+/master/Documentation/RelNotes/ https://github.com/gitster/git/tree/master/Documentation/RelNotes Enjoy! Adam
Re: gawk 4.1.4: CR separate char for CRLF files
On 08/09/2017 03:37 AM, Jannick wrote: > Which is a pretty much of a pain when there is no easy fallback solution > provided in case a major change is applied. E.g. for sed - if I understand > the reference to sed in https://cygwin.com/ml/cygwin/2017-08/msg00033.html > correctly - a separate switch '-b' is added. Incorrect. 'sed -b' has always existed, but did NOT do what you wanted (it forced CR to be treated as a separate character; where what you want is to ignore CR if it appears before LF). In fact, the coordinated change made back in February to all of grep, sed, and awk, was that all three programs now default to what used to be possible only through 'sed -b', because silently stripping CR can corrupt data when you are not expecting it, while requiring the user to explicitly strip CR when they know they are working with CRLF line endings is less magic (fewer downstream patches, and more obvious in looking at a script that the script knows what it is doing). If your data lives on a text mount (instead of a binary mount), then you still get CR stripping for free. If your data comes from a pipeline rather than the file system, then you can add a d2u or other CR-stripping tool in the pipeline. > This is - to say the least - unpleasant in the light of what Cygwin claims > to be, namely 'a large collection of GNU and Open Source tools which provide > functionality similar to a Linux distribution on Windows' (from the top of > the start website www.cygwin.com). On Linux, nothing strips CR automatically. So on Cygwin, we behave the same - nothing strips CR automatically on binary mounted data. And the fact that the change was made AND ANNOUNCED back in February, but you are now only 6 months later complaining about it, is telling. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org signature.asc Description: OpenPGP digital signature
RE: gawk 4.1.4: CR separate char for CRLF files
Hi Roger,
On Wed, 9 Aug 2017 07:03:24 +, Roger Krebs wrote:
> I've added a BEGIN section at the beginning awk sript file setting the
record
> separator explicitly for the input file (RS) as well as for the output
file (ORS):
>
> BEGIN {
> RS="\r\n"
> ORS="\r\n"
> }
> {
>... your script
> }
>
> Especially the RS parameter wasn't necessary in the past but now it is.
Which is a pretty much of a pain when there is no easy fallback solution
provided in case a major change is applied. E.g. for sed - if I understand
the reference to sed in https://cygwin.com/ml/cygwin/2017-08/msg00033.html
correctly - a separate switch '-b' is added. For the latest gawk version I
cannot see anything like that which means that all of our awk scripts run
against cygwin's gawk do break without any tweak unless I am missing
anything here.
This is - to say the least - unpleasant in the light of what Cygwin claims
to be, namely 'a large collection of GNU and Open Source tools which provide
functionality similar to a Linux distribution on Windows' (from the top of
the start website www.cygwin.com). Again, admittedly I did not dive into the
discussion and the substance of the reasoning to make this move to gawk |
sed | grep.
Now I can see the following *easy* solutions to the very situation here
(input only for now):
1 - Inserting the BEGIN section as you suggested into more than 1k scripts
(not feasible due to additional regression test workload)
2 - Calling 'gawk -vRS=\r\n -vORS=\r\n' instead of 'gawk' (hack to turn back
the additional the latest gawk's complexity, wrapper needed)
3 - Wrapping a d2u/u2d pipe solution (additional app and wrapper needed
again)
4 - Using another compiled version of gawk which does *not* disable the
out-of-the-box gawk feature to swallow CRs (cf., e.g.,
http://git.savannah.gnu.org/cgit/gawk.git/tree/awkgram.y#n3543), i.e.
without the artificial obstacle to now know the EOL type of the input file
ahead of running gawk.
> It works in all my cases. The only disadvantage: you have to know what
kind
... plus the disadvantage to systematically amend all the scripts instead of
having an external solution
> of files you want to handle in the awk script. The same awk script will
not
> work for DOS files as well as for linux files.
... another issue originated by the change and which didnt exist before.
> Best
>
> Roger
Please don't get me wrong, but this raises a real issue here and I am not
sure which rationale other than 'let's get more of the Linux-feel' drove the
decision.
All the best,
J.
> -Ursprüngliche Nachricht-
> Von: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] Im
> Auftrag von Jannick
> Gesendet: Mittwoch, 9. August 2017 02:48
> An: cygwin@cygwin.com
> Betreff: RE: gawk 4.1.4: CR separate char for CRLF files
>
> On Tue, 08 Aug 2017 16:23:40 -0700 (PDT), Steven Penny wrote:
> > On Wed, 9 Aug 2017 01:15:08, "Jannick" wrote:
> > > the current version 4.1.4 of gawk appears to unpleasantly treat CR
> > > for CRLF files, i.e. CR is not gracefully swallowed, but is a
> > > separate
> character.
> > >
> > > This makes some, if not all, of the scripts we are working with here
> > > useless, unless the input files are converted to LF which certainly
> > > is not feasible. IIRC the issue did not show up some versions back.
> > >
> > > Is this a bug - or am I missing something here?
> >
> > Learn to read:
> >
> > http://cygwin.com/ml/cygwin/2017-08/msg00033.html
>
> Thanks - quickly done.
>
> The link reveals that CRLF/LF conversion is now mandatory to work with
> cygwin's gawk on DOS machines. As far as I can see there is no legacy
> solution like for, e.g., sed (-b switch) to have an easy solution for the
issue,
> especially when invoking gawk from makefiles (piping).
>
> I consider this bad news while admittedly not fully understanding the
whole
> background of the move which is not necessary for now.
--
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
AW: gawk 4.1.4: CR separate char for CRLF files
Hi,
I've added a BEGIN section at the beginning awk sript file setting the record
separator explicitly for the input file (RS) as well as for the output file
(ORS):
BEGIN {
RS="\r\n"
ORS="\r\n"
}
{
... your script
}
Especially the RS parameter wasn't necessary in the past but now it is.
It works in all my cases. The only disadvantage: you have to know what kind of
files you want to handle in the awk script. The same awk script will not work
for DOS files as well as for linux files.
Best
Roger
-Ursprüngliche Nachricht-
Von: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] Im Auftrag von
Jannick
Gesendet: Mittwoch, 9. August 2017 02:48
An: cygwin@cygwin.com
Betreff: RE: gawk 4.1.4: CR separate char for CRLF files
On Tue, 08 Aug 2017 16:23:40 -0700 (PDT), Steven Penny wrote:
> On Wed, 9 Aug 2017 01:15:08, "Jannick" wrote:
> > the current version 4.1.4 of gawk appears to unpleasantly treat CR for
> > CRLF files, i.e. CR is not gracefully swallowed, but is a separate
character.
> >
> > This makes some, if not all, of the scripts we are working with here
> > useless, unless the input files are converted to LF which certainly is
> > not feasible. IIRC the issue did not show up some versions back.
> >
> > Is this a bug - or am I missing something here?
>
> Learn to read:
>
> http://cygwin.com/ml/cygwin/2017-08/msg00033.html
Thanks - quickly done.
The link reveals that CRLF/LF conversion is now mandatory to work with
cygwin's gawk on DOS machines. As far as I can see there is no legacy
solution like for, e.g., sed (-b switch) to have an easy solution for the
issue, especially when invoking gawk from makefiles (piping).
I consider this bad news while admittedly not fully understanding the whole
background of the move which is not necessary for now.
--
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
