Re: [ANNOUNCEMENT] Updated: csih-0.1.7-1

On Aug 21 23:11, Charles Wilson wrote: > Corinna Vinschen wrote: > > >> There are actually two questions: (a) should csih_check_access be > >> checking that the Administrators group has the desired access?, and (b) > >> are extended ACLs *actually* masked by the "other" bits? > > > > a) Actually,

Re: [ANNOUNCEMENT] Updated: cygutils-1.2.7-1

Charles Wilson wrote: >The cygutils package has been updated to 1.2.7. This adds a 'rename' >utility ... > >Changes from version 1.2.6-1 >- rename.exe added (contributed by Christopher Faylor) >... Dear all, I've started using cygwin relatively recently, and I have cygutils 1.3.2-1 installed. Thi

Re: [ANNOUNCEMENT] Updated: cygutils-1.2.7-1

s/between version 1.2.6-1 and 1.3.2-1/between version 1.2.7-1 and 1.3.2-1/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

Re: [ANNOUNCEMENT] Updated: cygutils-1.2.7-1

Sam Kuper wrote: > 1) Was the rename utility removed from cygutils at some point between > version 1.2.6-1 and 1.3.2-1, or is my version of cygutils somehow > corrupt? > 2) If it was removed, why, and is there some other way I can obtain > the rename utility under cygwin? (NB. please don't just su

Re: [ANNOUNCEMENT] Updated: cygutils-1.2.7-1

Brian Dessent wrote: > Everything is in the announcements. It was moved out of cygutils in > 1.3.0 and into util-linux: And, additionally, next time try: $ cygcheck -p rename.exe Found 3 matches for rename.exe. util-linux/util-linux-2.12r-2 Random collection of Linux utilities util-linux/util

Re: [ANNOUNCEMENT] Updated: cygutils-1.2.7-1

2008/8/22 Brian Dessent <[EMAIL PROTECTED]>: > Brian Dessent wrote: > >> Everything is in the announcements. It was moved out of cygutils in >> 1.3.0 and into util-linux: > > And, additionally, next time try: > > $ cygcheck -p rename.exe > Found 3 matches for rename.exe. > util-linux/util-linux-2.

Re: [ANNOUNCEMENT] Updated: csih-0.1.7-1

Corinna Vinschen wrote: > See Eric's comments. Especially the $var -eg "foo" is probably not > a good idea. OK...I'm sure I /did/ try it that way, but got an error of some kind (related to fun_call, not the -eq test). But I'll try it again. Maybe I fat-fingered something the first time. BTW, "f

Re: [ANNOUNCEMENT] Updated: cygutils-1.2.7-1

Sam Kuper wrote: > 1) Was the rename utility removed from cygutils at some point between > version 1.2.6-1 and 1.3.2-1, or is my version of cygutils somehow > corrupt? > 2) If it was removed, why, and is there some other way I can obtain > the rename utility under cygwin? (NB. please don't just sug

Cygwin compiler and linker options

Just doing some searches on the internet, there seems to be an awful lot of misinformation / misunderstanding about what the various Cygwin-gcc compiler and linker flags do. For example, I saw one article that said that that flag -mno-cygwin causes an executable to be generated which does *not* r

Cygwin Secure Shell Version 1.5.25-15 Request for U.S. Export Information 19399845 08222008

GE Aviation is in the process of reviewing your software product, Secure Shell Version 1.5.25-15 In order to determine whether the software is subject to Federal Export Administration Regulations (EAR), we are requesting that you provide the Export Control Classification Number (ECCN) that classifi

RE: Cygwin compiler and linker options

John Emmas wrote on Friday, August 22, 2008 1:54 PM:: > Just doing some searches on the internet, there seems to be an awful > lot of misinformation / misunderstanding about what the various > Cygwin-gcc compiler and linker flags do. > > For example, I saw one article that said that that flag -mn

Re: Cygwin compiler and linker options

Phil Betts wrote: It would be nice if the cygwin-specific options were documented in the gcc info file, but they don't appear to be. Don't expect -mno-cygwin to appear there soon either, because my understanding is that the -mno-cygwin option will be removed soon because of the surprising num

Re: Cygwin Secure Shell Version 1.5.25-15 Request for U.S. Export Information 19399845 08222008

On Fri, Aug 22, 2008 at 10:13:13AM -0400, TSG Software Licensing (GE Infra, Aviation) wrote: >GE Aviation is in the process of reviewing your software product, >Secure Shell Version 1.5.25-15 >In order to determine whether the software is subject to Federal Export >Administration Regulations (EAR)

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 03:52:35PM +0100, Phil Betts wrote: >John Emmas wrote on Friday, August 22, 2008 1:54 PM:: > >> Just doing some searches on the internet, there seems to be an awful >> lot of misinformation / misunderstanding about what the various >> Cygwin-gcc compiler and linker flags do.

Re: Having trouble with syslog-ng using lots of CPU

On 08/22/2008, Grav Yam wrote: In fact, I actually thought about emailing you or Corinna directly about this, but I didn't know if that was proper list etiquette. Sending email to the list is the recommended method of communication so you made the right call. -- Larry Hall

Re: Cygwin compiler and linker options

Christopher Faylor wrote: Phil is 100% correct here. It's heartening to see someone so thoroughly getting it after having to so frequently deal with the misconceptions about -mno-cygwin. Confusion about -mwindows is new though. I'm counting the days until -mno-cygwin disappears. It is a blig

Re: Cygwin compiler and linker options

Guys, Whilst I only signed up to this mailing list a couple of days ago, I can naturally understand your frustration if this topic ( -mno-cygwin) is dropping up over & over again and (apparently) being widely misunderstood. What I don't accept is that you have any right to castigate people for no

Re: Cygwin compiler and linker options

On 08/22/2008, John Emmas wrote: Whilst I only signed up to this mailing list a couple of days ago, I can naturally understand your frustration if this topic ( -mno-cygwin) is dropping up over & over again and (apparently) being widely misunderstood. What I don't accept is that you have any right

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 12:45:43PM -0400, Larry Hall (Cygwin) wrote: > On 08/22/2008, John Emmas wrote: >> Whilst I only signed up to this mailing list a couple of days ago, I can >> naturally understand your frustration if this topic ( -mno-cygwin) is >> dropping up over & over again and (apparent

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 11:32:24AM -0400, Ralph Hempel wrote: > Christopher Faylor wrote: > >> Phil is 100% correct here. It's heartening to see someone so thoroughly >> getting it after having to so frequently deal with the misconceptions >> about -mno-cygwin. Confusion about -mwindows is new th

Re: Having trouble with syslog-ng using lots of CPU

On Fri, Aug 22, 2008 at 11:19:34AM -0400, Larry Hall (Cygwin) wrote: > On 08/22/2008, Grav Yam wrote: >>In fact, I actually thought about emailing you or Corinna directly >>about this, but I didn't know if that was proper list etiquette. > >Sending email to the list is the recommended method of com

Re: Cygwin compiler and linker options

Christopher Faylor wrote: . As one of "those people" I wonder if it will still be possible to generate executables that do not depend on cygwin DLLs using cygwin's gcc? No, we're changing the laws of the universe to make this a physical impossibility. At your first attempt to generate a mingw

Re: Cygwin compiler and linker options

Ralph Hempel wrote: Christopher Faylor wrote: . As one of "those people" I wonder if it will still be possible to generate executables that do not depend on cygwin DLLs using cygwin's gcc? No, we're changing the laws of the universe to make this a physical impossibility. At your first attempt

Compiling gcc for cygwin

I figured I would take the liberty of informing anyone from the cygwin community that might not be on the gcc mailing lists. After a recent merge of the "tuples" branch of gcc to the mainline gcc, gcc stopped being compilable by the 3.4.4 compiler that comes with cygwin. There are two bugs for th

Re: Compiling gcc for cygwin

NightStrike wrote: > If cygwin ever wants to be able to support newer gcc compilers, > something needs to be done in this area. There are several options, That's a quite a misleading statement to make. Everything is fine for a native 4.4 using 3.4 as the bootstrap compiler. That's the whole po

Re: cygwin 1.7.0-28: Broken pipe signal broken?

linux but Windows thwarted me. It should now, at least, behave like 1.5.*. With cygwin 1.7.0-29 and 20080822, SIGPIPE and write now behave like 1.5.*. But ... Not quite. Now, with cygwin 1.7.0-29, parallel make is breaking, when trying to use a fifo on fd3 for communication between th

Re: cygwin 1.7.0-28: Broken pipe signal broken?

On Fri, Aug 22, 2008 at 08:31:07PM +0200, Christian Franke wrote: > ... I could also reproduce this problem. Unfortunately, I can't. A simple test cause would be appreciated. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems

Re: Cygwin compiler and linker options

Ralph Hempel wrote: what I think I hear you saying is that when -mno-cygwin is fully deprecated I'll need to build a cross compiler for native Windows executables Or, you could install MinGW. Cygwin and MinGW will coexist, side by side, without conflict, if you arrange it so only one is in

Re: Cygwin compiler and linker options

Warren Young wrote: Ralph Hempel wrote: what I think I hear you saying is that when -mno-cygwin is fully deprecated I'll need to build a cross compiler for native Windows executables Or, you could install MinGW. Cygwin and MinGW will coexist, side by side, without conflict, if you arrange

Re: Cygwin compiler and linker options

Ralph Hempel wrote: I know I can install MinGW, but keeping track of their releases and having to download custom versions of this and that to get all the parts to play nicely together is such a huge PITA. Building cross-compilers is easier? -- Unsubscribe info: http://cygwin.com/ml/#uns

Re: Cygwin compiler and linker options

Warren Young wrote: Ralph Hempel wrote: I know I can install MinGW, but keeping track of their releases and having to download custom versions of this and that to get all the parts to play nicely together is such a huge PITA. Building cross-compilers is easier?

Re: Cygwin compiler and linker options

On Fri, Aug 22, 2008 at 04:00:06PM -0400, Ralph Hempel wrote: > arren Young wrote: >>Ralph Hempel wrote: >>>what I think I hear you saying is that when -mno-cygwin is fully >>>deprecated I'll need to build a cross compiler for native Windows >>>executables >>Or, you could install MinGW. Cygwin and

man: cygwin 1.7.0 and special filename chars

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Currently man(1) and perl work around Cygwin's inability to handle illegal DOS filename characters by substituting '.' for '::', IOW: $ man ExtUtils::Depends will display ExtUtils.Depends.3pm, which is created by perl on Cygwin instead of ExtUtils:

Re: cygwin 1.7.0-28: Broken pipe signal broken?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 8/22/2008 1:22 PM: > On Fri, Aug 22, 2008 at 08:31:07PM +0200, Christian Franke wrote: >> ... I could also reproduce this problem. > > Unfortunately, I can't. > > A simple test cause would be appreciated. The paral

[ANNOUNCEMENT] Updated: mercurial-1.0.2-1 -- Fast, lightweight distributed source control management system

PACKAGE DESCRIPTION === Homepage: http://www.selenic.com/mercurial/ License : GPL Distributed, efficient Python based source control system. Mercurial is designed for efficient handling of very large distributed projects. Features include: CHANGES SINCE LAST RELEASE =

cygport branched for cygwin-1.7

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have just branched cygport. 1.5 support will be maintained in branches/cygwin-1.5, which will soon be a stable 0.4.0. As of today, this branch will only run on 1.5. Further development of this branch will be mostly bug fixes, and will be supporte

Re: Cygwin compiler and linker options

John Emmas skrev: Guys, Whilst I only signed up to this mailing list a couple of days ago, I can naturally understand your frustration if this topic ( -mno-cygwin) is dropping up over & over again and (apparently) being widely misunderstood. What I don't accept is that you have any right to cast

Re: cygwin 1.7.0-28: Broken pipe signal broken?

On Fri, Aug 22, 2008 at 02:51:09PM -0600, Eric Blake wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >According to Christopher Faylor on 8/22/2008 1:22 PM: >> On Fri, Aug 22, 2008 at 08:31:07PM +0200, Christian Franke wrote: >>> ... I could also reproduce this problem. >> >> Unfortunately

Re: Cygwin compiler and linker options

I thought I should point out that "gcc -v -help" says: % gcc -v --help 2>&1 | grep no-cygwin -mno-cygwin Use the Mingw32 interface cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation:

Re: man: cygwin 1.7.0 and special filename chars

"Yaakov (Cygwin Ports)" wrote: > 1) Completely remove the /::/./ substitution in both man and perl for 1.7; > 2) Have man look for both '.' and '::'. How about 3) Perpetuate the s/::/./ workaround in Cygport so that manpages continue to be generated with '.'. Rationale: Support for : in filenam

Re: Cygwin compiler and linker options

- Original Message - From: "Warren Young" <[EMAIL PROTECTED]> Subject: Re: Cygwin compiler and linker options It's not impossible to have them both in the PATH, but I've come across enough strange behavior that I don't do that anymore. I posted about how to keep the two separate withou