I've made a new version of the mingw-runtime available for download.
For a list of changes see:
http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/mingw/ChangeLog?rev=1.447&cvsroot=src
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, lo
On Aug 16 13:54, Martin Dorey wrote:
> -58 fixed a repeatable crash I was seeing in fork on every machine on
> which I ran a particular big hairy application
> (http://software.jessies.org/terminator). Nothing new there, so I only
> spam you with my thanks because the machines in question were all
On Aug 17 00:09, Angelo Graziosi wrote:
> Gulp! In this context, the translation of 'Nessuno' should be 'None' and
> NOT 'Nobody' :-(
>
> I resend correcting, for the sake of completeness... :-)
>
>
> Messaggio Originale
> Oggetto: Cygwin-1.7 and 'Nobody' group
>
>
> Usually, i
Corinna Vinschen wrote:
After all these years I was sure that now everyone was aware of the
fact that the group "None" or whatever it's called in other languages
is not a bug in Cygwin, but an actual Windows group.
I didn't mean a bug, but a different behavior under 1.7.
I have noticed that th
On Aug 16 12:55, Charles Wilson wrote:
> Colin Harrison wrote:
> > I am getting a stderr/pipe problem with some CUI's ~line 398 in run.c
> > (1.1.11 run + your patch)
> > bForceUsingPipes = (os_version >= 0x0501);
>
> #$!%#
>
> > I made this = FALSE to fix for 2003 server..not tried on Windows 7
On Aug 16 17:11, Andy Koppe wrote:
> 2009/8/14 Corinna Vinschen:
> >> I tried it again briefly last night. It only happened when logged in
> >> as an administrator, not as a limited user. That's with UAC enabled.
> >> Didn't try disabling. Reproduced both with 'rxvt' and 'mintty -u', and
> >> timed
On Aug 17 10:47, Angelo Graziosi wrote:
> Now, since them have been created by setup-1.7.exe (called from
> Start/Run), I would expect that, after the changes 513 --> 544 etc. in
> /etc/passwd, they belong to Administrators etc. (as the do in Cygwin-1.5
> and for the other files in 1.7). Evidently,
Hi,
Corinna wrote:
> However, would others be so kind to test this on non-W7 systems
I built run from cvs + Corinna's patch with MinGW (for native Windows) and
tested on Windows 2003 server.
Tests OK for me..my Big List Of Dodgy CUIs appear to be happy bunnies now :)
Thanks,
Colin
--
Problem r
Hi!
How can I build Cygwin packages?
--
Att.
Bruno Galindro da Costa
bruno.galin...@gmail.com
Florianópolis - SC
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: h
Version 1.35-1 of cppcheck has been uploaded, following the upstream release.
cppcheck is a tool for static C/C++ code analysis. It tries to detect
bugs that your C/C++ compiler don't see.
The goal is no false positives.
cppcheck is versatile. You can check non-standard code that includes
variou
On 8/17/2009 4:47 AM, Corinna Vinschen wrote:
On Aug 16 12:55, Charles Wilson wrote:
Colin Harrison wrote:
I am getting a stderr/pipe problem with some CUI's ~line 398 in run.c
(1.1.11 run + your patch)
bForceUsingPipes = (os_version >= 0x0501);
#$!%#
I made this = FALSE to fix for 2003 ser
On Aug 17 08:18, Ken Brown wrote:
> On 8/17/2009 4:47 AM, Corinna Vinschen wrote:
>> I'm not sure this a generic enough solution, there's probable more
>> necessary. However, would others be so kind to test this on non-W7
>> systems as well as with other applications like emacs?
>
> Works for me o
Corinna Vinschen wrote:
> Oh well. The above shortcut as well as your startxwin.bat script don't
> work on W7. Only a shortcut like this
>
> C:\cygwin-1.7\bin\run.exe emacs-X11 --display=127.0.0.1:0.0
>
> works and allows to start emacs.
So, here's another approach that seems to work for me
On Aug 17 11:36, Charles Wilson wrote:
> Corinna Vinschen wrote:
>
> > Oh well. The above shortcut as well as your startxwin.bat script don't
> > work on W7. Only a shortcut like this
> >
> > C:\cygwin-1.7\bin\run.exe emacs-X11 --display=127.0.0.1:0.0
> >
> > works and allows to start emacs.
--On 17 August 2009 15:57 +0200 Corinna Vinschen wrote:
The [...] as well as your startxwin.bat script don't work on W7.
On any NT-class Windows, calling a *.bat file causes a 16-bit sub-system to
be spawned, and the .bat file is interpreted within the 16-bit command
interpreter.
Given tha
Hi,
Chuck wrote:
> So, here's another approach that seems to work for me
I needed to #include to compile this with MinGW (to find
SHGFI_EXETYPE)
However, then I get (on Windows 2003) an 'Unable to write to standard error'
with my CUI plink.
Thanks,
Colin
--
Problem reports: http://cyg
Robin Walker wrote:
" --On 17 August 2009 15:57 +0200 Corinna Vinschen wrote:
" > The [...] as well as your startxwin.bat script don't work on W7.
" On any NT-class Windows, calling a *.bat file causes a 16-bit sub-system to
" be spawned, and the .bat file is interpreted within the 16-bit command
On 8/17/2009 12:36 PM, Corinna Vinschen wrote:
On Aug 17 11:36, Charles Wilson wrote:
Corinna Vinschen wrote:
Oh well. The above shortcut as well as your startxwin.bat script don't
work on W7. Only a shortcut like this
C:\cygwin-1.7\bin\run.exe emacs-X11 --display=127.0.0.1:0.0
works and
--On 17 August 2009 17:52 + Stephan Mueller wrote:
Robin Walker wrote:
" On any NT-class Windows, calling a *.bat file causes a 16-bit
sub-system to " be spawned, and the .bat file is interpreted within the
16-bit command " interpreter.
"
" Given that Cygwin 1.7 no longer supports Windows
On Mon, Aug 17, 2009 at 07:16:17PM +0100, Robin Walker wrote:
>--On 17 August 2009 17:52 + Stephan Mueller wrote:
>
>> Robin Walker wrote:
>> " On any NT-class Windows, calling a *.bat file causes a 16-bit
>> sub-system to " be spawned, and the .bat file is interpreted within the
>> 16-bit com
Colin Harrison wrote:
> Hi,
>
> Chuck wrote:
>> So, here's another approach that seems to work for me
>
> I needed to #include to compile this with MinGW (to find
> SHGFI_EXETYPE)
>
> However, then I get (on Windows 2003) an 'Unable to write to standard error'
> with my CUI plink.
Okay, so her
Jim Reisert AD1C wrote:
I can't control how the ZIP file gets created, but I do expect that
when I unzip a file, that the .exe will actually execute without
having to change permissions!
I guess it comes down to a question of whether *.exe implies chmod +x.
It doesn't in any "native" *ix pack
Charles Wilson wrote:
> If we already HAVE true console handles, then we shouldn't FreeConsole
> and try to recreate our own...
OK, how about this? Seems to work on Vista(cyg1.5, cyg1.7, mingw) x
gui/cui/bat.
The basic idea is to try and re-use whatever console is available, if
any, when run is
popen misbehaves when various std fds are closed.
Test program:
#include
#include
#include
#include
#include
#include
#include
#include
static FILE *tty;
static void
dump (const char *s, int fd)
{
fprintf (tty, "%s: fd %d: %s\n", s, fd,
dup2 (fd, fd) == fd
On Mon, Aug 17, 2009 at 03:45:23PM -0700, Eric Blake wrote:
>popen misbehaves when various std fds are closed.
And, who among us could have not seen that coming?
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: htt
CGF wrote:
" On Mon, Aug 17, 2009 at 07:16:17PM +0100, Robin Walker wrote:
" >--On 17 August 2009 17:52 + Stephan Mueller wrote:
" >
" >> Robin Walker wrote:
" >> " On any NT-class Windows, calling a *.bat file causes a 16-bit
" >> sub-system to " be spawned, and the .bat file is interpreted
On 08/17/2009 12:32 PM, Warren Young wrote:
Jim Reisert AD1C wrote:
I can't control how the ZIP file gets created, but I do expect that
when I unzip a file, that the .exe will actually execute without
having to change permissions!
I guess it comes down to a question of whether *.exe implies c
Hi,
Chuck wrote:
> OK, how about this? Seems to work on Vista(cyg1.5, cyg1.7, mingw)
xgui/cui/bat.
Applied your latest patch to run's cvs and built with MinGW, for native
Windows.
Works for me on Windows 2003 Server.
Tested as before and with 'run CUIs' in batch files (*.bat) and shortcut
file
28 matches
Mail list logo
