On 24/10/14 02:43, Corinna Vinschen wrote:
> On Oct 22 20:57, Tom Schutter wrote:
>> On Wed 2014-10-22 11:23, Corinna Vinschen wrote:
>>> For your convenience I wrote new documentation. Since this is a TEST
>>> prerelease, the new documentation is not part of the official docs yet.
>>> Rather hav
On 10/23/2014 4:32 PM, Ken Brown wrote:
On 10/23/2014 11:37 AM, Corinna Vinschen wrote:
On Oct 23 08:04, Ken Brown wrote:
On 10/23/2014 7:31 AM, Jon TURNEY wrote:
On 20/10/2014 14:03, Ken Brown wrote:
Or is there some other plausible explanation for "impossible" crashes?
This can't just be a
Greetings, Thomas Wolff!
> I'm facing a number of issues with case-sensitivity which I've collected:
>
> There is a documented limitation on case-sensitivity using drive letter
> paths,
> also mentioned in https://sourceware.org/ml/cygwin/2013-08/msg00090.html
> (last item)
Greetings, Tom Schutter!
>> The major change in this new release is the new method to read account
>> (passwd and group) information from the Windows user databases directly,
>> without the requirement to generate /etc/passwd and /etc/group files to
>> generate Unix-like uid and gid.
> What do yo
Thank you -- that clears up a lot of my confusion.
- Original Message -
> From: Achim Gratz
> To: cygwin@cygwin.com
> Cc:
> Sent: Thursday, October 23, 2014 4:52 PM
> Subject: Re: run.exe flashes non-hidden console window in cygwin64 on
> Win7Pro-64
>
> John Wiersba writes:
>> Is th
John Wiersba writes:
> Is this not a bug in run.exe?
No, if anything it's a bug in Windows. Look in the archives at the
beginning of 2009 where this was discussed. You can at least hide the
window after it exists now, but the option of starting it out of sight
has been removed with Windows 7 and
On 10/23/2014 11:37 AM, Corinna Vinschen wrote:
On Oct 23 08:04, Ken Brown wrote:
On 10/23/2014 7:31 AM, Jon TURNEY wrote:
On 20/10/2014 14:03, Ken Brown wrote:
Or is there some other plausible explanation for "impossible" crashes?
This can't just be a result of a gdb bug, because in at least
> From: Doug Henderson
>
>On 21 October 2014 10:51, John Wiersba wrote:
>
>> I'm trying to use run.exe to avoid a flashing console window, but it is not
>> working on
>> my cygwin64 install on Win7Pro-64. This is a fresh install from 10/20/2014.
>> I've
>> attached my cygcheck.out. I've
On 21 October 2014 10:51, John Wiersba wrote:
> I'm trying to use run.exe to avoid a flashing console window, but it is not
> working on my cygwin64 install on Win7Pro-64. This is a fresh install from
> 10/20/2014. I've attached my cygcheck.out. I've tried the following windows
> shortcuts an
Today I have update my Cygwin and thus it started giving error at the
end of compiling. Using Compiler Mingw32 Libtool for cross platform
compiling
In function 'main':
xxx.c:315:3: warning: implicit declaration of function '_spawnv'
[-Wimplicit-function-declaration]
rval = _spawn
Thanks, Doug.
I use cygstart.exe to start windows programs (such as winword or notepad) from
a mintty/bash console in a way that allows the mintty console to be closed
while the windows application is still active.
I thought run.exe was meant to be used from shortcuts to run cygwin program
>
> From: Achim Gratz
>John Wiersba writes:
>> Maybe I'm confused. Isn't the purpose of run.exe to start a
>> cygwin program without creating a (visible) console window?
>
>The purpose of run is to start a Windows program that needs a console to
>exist and hide th
On 23 October 2014 06:24, John Wiersba > wrote:
> Maybe I'm confused. Isn't the purpose of run.exe to start a
> cygwin program without creating a (visible) console window?
> I can just start a cygwin program directly without the indirection of
> run.exe if I don't care about the random flashing co
Corinna Vinschen writes:
>> Yes, flags register corruption is exactly what Eli suggested in the other
>> bug report I cited.
>
> The aforementioned patch was supposed to fix this problem and it is
> definitely in the current 1.7.32 release...
Emacs uses a bunch of libraries and also messes itself
On 2014-10-22 11:23, Corinna Vinschen wrote:
>
> - Drop the current working directory from the default DLL search path in
> favor of Cygwin's /bin dir.
I'm not so comfortable with this one.
I use
PATH=/my/dir/bin:/usr/bin /my/otherdir/myprog
There is no DLL at all in /my/otherdir (this is the v
Achim Gratz writes:
> Corinna Vinschen writes:
>> In theory, no. The last OpenSSH update, 6.7p1-1, alreadyd contained
>> the upstream fix to work with local sshd accounts which have the
>> machine name prepended.
>
> I will check this tomorrow, I somehow missed that this patch was live.
> The entr
Tom Schutter writes:
> On Wed 2014-10-22 11:23, Corinna Vinschen wrote:
>> The major change in this new release is the new method to read account
>> (passwd and group) information from the Windows user databases directly,
>> without the requirement to generate /etc/passwd and /etc/group files to
>>
John Wiersba writes:
> Maybe I'm confused. Isn't the purpose of run.exe to start a
> cygwin program without creating a (visible) console window?
The purpose of run is to start a Windows program that needs a console to
exist and hide the console window created by windows if there is no
console tha
Am 23.10.2014 17:36, schrieb Corinna Vinschen:
On Oct 23 14:42, Thomas Wolff wrote:
Am 22.10.2014 16:00, schrieb Corinna Vinschen:
On Oct 22 09:01, Thomas Wolff wrote:
I'm facing a number of issues with case-sensitivity which I've collected:
There is a documented limitation on case-sensitivit
> More exact: stricmp is still available as exported symbol, and it will
> be available for a long time, to make sure existing executables continue
> to run. stricmp will just not be provided by the standard header files
> anymore.
Thanks, Corinna! I'll use strcasecmp() from now on.
--
Jim Re
On Oct 22 20:57, Tom Schutter wrote:
> On Wed 2014-10-22 11:23, Corinna Vinschen wrote:
> > For your convenience I wrote new documentation. Since this is a TEST
> > prerelease, the new documentation is not part of the official docs yet.
> > Rather have a look at
> >
> > https://cygwin.com/preli
On Oct 23 17:36, Corinna Vinschen wrote:
> On Oct 23 08:14, Eric Blake wrote:
> > On 10/23/2014 08:10 AM, Jim Reisert AD1C wrote:
> > > Apparently stricmp() is no longer in the library:
> > >
> > > ClubLog.cpp:593:34: error: 'stricmp' was not declared in this scope
> > > if (!stricmp(fiel
On Oct 23 08:04, Ken Brown wrote:
> On 10/23/2014 7:31 AM, Jon TURNEY wrote:
> >On 20/10/2014 14:03, Ken Brown wrote:
> >>Or is there some other plausible explanation for "impossible" crashes?
> >>This can't just be a result of a gdb bug, because in at least one case
> >>the assertion can be shown
On Oct 23 08:14, Eric Blake wrote:
> On 10/23/2014 08:10 AM, Jim Reisert AD1C wrote:
> > Apparently stricmp() is no longer in the library:
> >
> > ClubLog.cpp:593:34: error: 'stricmp' was not declared in this scope
> > if (!stricmp(field,"call")) {
> >
> > I realize that stricmp() is non
On Oct 23 14:42, Thomas Wolff wrote:
> Am 22.10.2014 16:00, schrieb Corinna Vinschen:
> >On Oct 22 09:01, Thomas Wolff wrote:
> >>I'm facing a number of issues with case-sensitivity which I've collected:
> >>
> >>There is a documented limitation on case-sensitivity using drive letter
> >>paths,
> >
On 10/23/2014 08:10 AM, Jim Reisert AD1C wrote:
> Apparently stricmp() is no longer in the library:
>
> ClubLog.cpp:593:34: error: 'stricmp' was not declared in this scope
> if (!stricmp(field,"call")) {
>
> I realize that stricmp() is non-standard. Is this going to be the
> situation g
Apparently stricmp() is no longer in the library:
ClubLog.cpp:593:34: error: 'stricmp' was not declared in this scope
if (!stricmp(field,"call")) {
I realize that stricmp() is non-standard. Is this going to be the
situation going forward with 1.7.33+? If so, what's the best
workaround?
Am 22.10.2014 16:00, schrieb Corinna Vinschen:
On Oct 22 09:01, Thomas Wolff wrote:
I'm facing a number of issues with case-sensitivity which I've collected:
There is a documented limitation on case-sensitivity using drive letter
paths,
also mentioned in https://sourceware.org/ml/cygwin/2013-08
> From: Andrey Repin
>To: Doug Henderson ; cygwin@cygwin.com
>Sent: Wednesday, October 22, 2014 9:28 PM
>Subject: Re: run.exe flashes non-hidden console window in cygwin64 on
>Win7Pro-64
>
>>> Andrey, the flashing console flashes very quickly and I don't know how to
>>> slow it down.
>>> It ap
On 10/23/2014 7:31 AM, Jon TURNEY wrote:
On 20/10/2014 14:03, Ken Brown wrote:
Or is there some other plausible explanation for "impossible" crashes?
This can't just be a result of a gdb bug, because in at least one case
the assertion can be shown to be valid by using printf instead of gdb.
[*]
On 20/10/2014 14:03, Ken Brown wrote:
Or is there some other plausible explanation for "impossible" crashes?
This can't just be a result of a gdb bug, because in at least one case
the assertion can be shown to be valid by using printf instead of gdb.
[*] By "impossible" I mean that examination o
> > Have you tried changing the shortcut to cause it to open the window
> > minimized? I vaguely remember doing something like that with the
> > cygwin.bat clone I used to start a (non-X windows) rxvt window.
>
> That may at least alleviate the window flashing in the face of a user.
Yeah, that do
Well I am using cygwin for my continuous build/test integration system.
And I meet a lot of issue with the use of the mounted NAS
Because the behaviours are not repeatable it is hard to see a pattern,
sometimes it does work, sometimes not...
First to describe the context :
- I have cygwin insta
33 matches
Mail list logo
