Re: grep treating my text files as binary!

[Warren Young]

On Dec 25, 2014, at 11:41 AM, Thomas Wolff  wrote:

> In any case the argument is quite artificial since the new behaviour
> hits many files that are in fact text files.

Please define the term “text file” in a way that allows a C programmer to write 
a program that automatically does the correct thing for all members of the 
class “text file” without involving locales, or an equivalent mechanism.

Just because you, the human, can use your superior pattern matching skills to 
see that a file is a “text file” doesn’t mean that a relatively dumb program 
like grep(1) can.  You can’t expect someone to build an AI system into grep(1) 
just to get automatic locale detection.

If grep runs into a byte sequence that makes it think it is not legal for your 
current locale, it must treat the file as raw bytes, unless you give it -a.

If you don’t like this behavior, say “alias grep=grep -a” in your ~/.bashrc, 
and forget the change ever happened.  It’ll be on you when some non-text file 
gets treated as text and grep spams your terminal with binary garbage, though.

This isn’t really a Cygwin problem.  It just happens to affect it more than 
other *ix systems because there are two sets of rules on the same system, and 
they may conflict.  But, if I go and copy a UTF-16LE file to a Linux box, I’m 
not going to complain to the grep bug list when grep doesn’t automatically do 
the right thing with it while $LANG contains UTF-8.

Ultimately, the proper solution is to use UTF-8 on all systems you use Cygwin 
on.  Many Unicode-aware native Windows programs that deal with text files can 
cope with UTF-8.  

If you have one of those that demands UTF-16LE, iconv(1) can make the 
conversion for you.
--
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: ld.exe segfault when compiling Box Backup

[Larry Hall (Cygwin)]

On 12/24/2014 10:09 AM, Chris Wilson wrote:

Dear Cygwin Developers,

I've been successfully building official Windows releases of Box Backup
using Cygwin and its MinGW compilers for many years. (MinGW alone doesn't
provide enough POSIX compatibility to run the test suite). Now I'm trying to
build a new release on Windows 7 with 64-bit MinGW compilers and running
into a problem where ld.exe is crashing during compilation.

I narrowed down the test case to two files, and this command:

Chris@win7-64bit-vm /tmp
$ x86_64-w64-mingw32-g++ BackupClientInodeToIDMap.o libqdbm.a
collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped

You can download those two files here:
http://gcc.flexdns.net/bugreport/BackupClientInodeToIDMap.o
http://gcc.flexdns.net/bugreport/libqdbm.a

Compiles that don't include both of those files appear to work OK, so it's
something about them. BackupClientInodeToIDMap.o is one of the few parts of
Box Backup (perhaps the only part) that depends on qdbm.

Note that I ran cygcheck after downgrading to an older binutils to see if
that would help, but it didn't. I get the same symptoms with "GNU ld (GNU
Binutils) 2.24.51.20140411" installed (mingw64-x86_64-binutils
2.24.0.3.85cf705-1).

I don't really know how to investigate this any further. I know very little
about ld. Any help would be gratefully appreciated. Thanks!


If you haven't already, I recommend checking out this issue at the Mingw-w64
site (http://mingw-w64.sourceforge.net).  The Cygwin packages really come
from them and they are the maintainers.  They are best equipped to help you
with this issue.


--
Larry

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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: RFD: cygwin ACLs: NFS or POSIX model: ease in adapting to CIFS ACLs?

[Linda Walsh]

Larry Hall (Cygwin) wrote:

On 12/21/2014 06:25 PM, Linda Walsh wrote:

I seem to remember that the cygwin ACL's were based on NFS acls not
the POSIX ACL's.  


I can't speak to the specific issues you're raising or shed any light
on whether they are actually issues with Cygwin.  As far as the Cygwin
implementation is concerned, I believe the links below shed some light
on the original implementation and the direction things are heading.
At this time, the first link still refers to a test version of the
Cygwin package, though the version number is different.




Hope this helps.

---
Indeed, though not in the details, but that may not be necessary depending
on what this means:


   - Revamp Solaris ACL implementation to more closely work like
 POSIX ACLs are supposed to work. Finally implement a CLASS_OBJ 
emulation.

 Update getfacl(1)/setfacl(1) accordingly.
---
Not very specific, but may have addressed any issues in that area.

The part that looks a bit more "hairy" are the auto-RID-UID mappings
and how those will work with existing UID/RID mappings coming from
a samba server...  Specifically, will cygwin support UID's > 32 bit?

I found to cleanly separate various login & service types into contiguous
blocks was good to multiply by large numbers.  I'm thinking cygwin already
supports the longer numbers or things like 'TRUSTED INSTALLER' wouldn't show
with the right owner or be changeable in cygwin...

Thanks for the reply...






--
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: windows application manifest in gnu cpp application built on cygwin

[LMH]

Andrey Repin wrote:
> Greetings, LMH!
> 
>> Can someone point me to a reference for linking a windows 7 compatible
>> application manifest when building a program with GNU cpp under cygwin?
>> I have found some examples of the manifest files I need, but no examples
>> of the syntax for including a manifest in the make file, where the file
>> should go, etc.
> 
> Default manifest is already built in unless you provide custom one.
> For including, it's just included, like any other resource.
> 
> 
> --
> WBR,
> Andrey Repin (anrdae...@yandex.ru) 21.12.2014, <04:56>
> 
> Sorry for my terrible english...
> 
> 
> --
> 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
> 
> 

Thanks for the reply,

I tried to use ManifestView to look at the manifest, but ManifestVeiw
can't seem to find a manifest to display. I'm not sure why that would
be. I have also looked at the binary with a text editor and cannot find
any html code or the word manifest. I would like to confirm the
existence of a manifest and am looking for another tool that might work
better.

I presume I need mingw64-x86_64-windows-default-manifest-6.4-1 installed
in the cygwin package manager. Is that correct?

Is there documentation somewhere that describes the gnu c++ default
manifest? I couldn't find anything with a search.

LMH

--
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

[ANNOUNCEMENT] Updated: par-1.52-4

[David Levine]

par-1.52-4 is now available.  par is a paragraph reformatter, vaguely
similar to fmt, but better.

changes:
1) Added multibyte character support.


  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com  cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

--
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