-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I propose (again) to add gamin to the distribution. gamin is a portable
replacement for FAM, and is used by recent versions of GLib as part of
the new GIO library. This version includes the patches discussed last
time plus some more.
Earlier
On Dec 19 11:04, Frank Seelisch wrote:
Corinna,
yes, I did. Thanks for the hint.
We're still in prep for packaging Singular 3-1-0...
To be honest; I'm new to X Server related stuff, so still a bit clueless. I
will contact Oliver (Wienand), in order to get this done asap.
Cool.
Thanks,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jari Aalto wrote:
I'm lacking working X to check the compilation results. If someone would
be interested in maintaining nedit, I'd be happy to orphan it.
Seeing no response, I'd rather take the package then the continued bug
reports:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The GNOME-2.x version of libart_lgpl has been rebuilt, with the package
names changing from libart_lgpl2{,-devel} to libart_lgpl_2{_2,-devel}.
This was done to better accommodate parallel installation with the
gnome-libs-1.4 version of the same
Hi,
Jon wrote
* The patch to really fix -silent-dup-error
I don't get this? How does this manifest itself, perhaps my test is
different?
(I don't have server lock file(s))
Thanks
Colin
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
Colin Harrison wrote:
Hi,
Jon wrote
* The patch to really fix -silent-dup-error
I don't get this? How does this manifest itself, perhaps my test is
different?
(I don't have server lock file(s))
Yes, I think this due to the lock file code.
OsInit() does a LockServer() before OsVendorInit()
Hi,
Can't think what the option achieves anyway.
You can't run duplicate display-numbers, so warning the user is **always** a
good idea.
Maybe an idea too-far, but I've never used -silent-dup-error, it is a little
daft..so lets just ditch it?
Thanks
Colin
--
Unsubscribe info:
Hi,
For the script merchants, who want to force a run, just to test the water.
(Who think itÂ’s a good idea to test Xmas tree light sockets with a wet
finger).
We could have a '-silent-running' flag to suppress all output, MessageBoxes
(but not any smoke).
Thanks
Colin
Can't think what the
Jon TURNEY wrote on Tuesday, December 16, 2008 6:48 PM::
Gionatan Danti wrote:
Hi all,
I have a question regarding CygWin/X.
I would like to know if there is a method to scale a window, similar
to what is possible with UltraVNC and its scaling option.
To be more clear, I will explain my
Jon TURNEY wrote on Tuesday, December 16, 2008 6:48 PM::
Gionatan Danti wrote:
Hi all,
I have a question regarding CygWin/X.
I would like to know if there is a method to scale a window, similar
to what is possible with UltraVNC and its scaling option.
To be more clear, I will explain my
Colin Harrison wrote:
Can't think what the option achieves anyway.
You can't run duplicate display-numbers, so warning the user is **always** a
good idea.
Maybe an idea too-far, but I've never used -silent-dup-error, it is a little
daft..so lets just ditch it?
The usefulness is that you can
Rodrigo Medina wrote:
To the X11 mantainer:
I am trying to compile the last version of
xdvik (22.84.14) with X11R7.
The execution of xdvi-xaw3d stops with Segmentation fault.
Using gdb I have determined that the failure is due to the
function XtGetApplicationResources() of the Xt library.
Hi,
Jon wrote
The usefulness is that you can write a script that does:
Good point..its been years since I stated a server+client with a script like
that :)
An easily addable option is to just suppress/redirect MessageBoxes (i.e. no
popups demanding OK to be clicked).
Or just keep MessageBoxes
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2008-12-19 12:15:33
Modified files:
winsup/cygwin : ChangeLog path.cc
Log message:
* path.cc (path_conv::check): Handle incoming DOS paths non-POSIXy,
always case-insensitive, always
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2008-12-19 14:31:40
Modified files:
winsup/cygwin : ChangeLog fhandler_registry.cc
Log message:
* fhandler_registry.cc (perf_data_files): New table.
(PERF_DATA_FILE_COUNT): New
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2008-12-19 19:09:51
Modified files:
cygwin : ChangeLog pinfo.cc strace.cc
cygwin/include/sys: strace.h
Log message:
* pinfo.cc (pinfo_basic): New class.
CVSROOT:/cvs/src
Module name:src
Changes by: ironh...@sourceware.org 2008-12-20 03:55:37
Modified files:
winsup/mingw : ChangeLog msvcrt.def.in
Log message:
2008-12-16 Danny Smith dannysm...@users.sourceforge.net
* msvcrt.def.in
The command 'ls /proc/registry/HKEY_PERFORMANCE_DATA' returns garbage,
because the registry functions don't work or work different for this
(pseudo-)key.
This patch fixes the directory listing and allows access to the raw
binary counter data, e.g.
All Global values, except Costly values:
On Dec 19 14:58, Christian Franke wrote:
* fhandler_registry.cc (perf_data_files): New table.
(PERF_DATA_FILE_COUNT): New constant.
(fhandler_registry::exists): Add check for HKEY_PERFORMANCE_DATA
value names.
(fhandler_registry::fstat): For
On Fri, Dec 19, 2008 at 1:58 PM, Christian Franke wrote:
(fhandler_registry::fill_filebuf): Use larger buffer to speed up
access to HKEY_PERFORMANCE_DATA values. Remove check for possible
subkey. Add RegCloseKey ().
+ /* RegQueryValueEx () opens
Chris January wrote:
On Fri, Dec 19, 2008 at 1:58 PM, Christian Franke wrote:
(fhandler_registry::fill_filebuf): Use larger buffer to speed up
access to HKEY_PERFORMANCE_DATA values. Remove check for possible
subkey. Add RegCloseKey ().
+ /*
Can anyone explain why the installer began recommending using *nix line
ending conventions? DOS-compatible endings have always just worked
for me and I've heard of lots of problems doing it the now-recommended
way. See
From: gustav gus...@indiana.edu
Date: Thu, 11 Dec 2008 21:50:53 -0500 (EST)
If you still use Emacs' original Rmail with POP under Cygwin, you may
have noticed that it doesn't work. The reason is that Rmail tries to
create a file with a : in its name, which Cygwin can't do. A simple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cygport has been updated to 0.4.3 for Cygwin 1.5, and 0.9.4 for 1.7,
with similar changes to both:
* Requires libtool-2.2 throughout.
* cygpatch() tries with and without --binary.
* lndirs() uses lndir(1) unconditionally.
* Override pushd and popd
Hello David,
* On Thu, Dec 18, 2008 at 05:42:20PM -0900 David Abrahams wrote:
Can anyone explain why the installer began recommending using *nix line
ending conventions? DOS-compatible endings have always just worked
for me and I've heard of lots of problems doing it the now-recommended
When i run a Fuijitsu Cobol program it requires environmental variables
starting with the @ sign.
SET @CBR_CONSOLE=SYSTEM
When I try and set these in a bash shell I get the following.
$ export @CBR_CONSOLE=SYSTEM
-bash: export: `...@cbr_console=system': not a valid identifier
Is there any
From: Spiro Trikaliotis
Hello David,
* On Thu, Dec 18, 2008 at 05:42:20PM -0900 David Abrahams wrote:
Can anyone explain why the installer began recommending using *nix
line ending conventions? DOS-compatible endings have
always just worked
for me and I've heard of lots of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been added to the distribution:
*** gamin-0.1.10-1
*** libfam0-0.1.10-1
*** libfam-devel-0.1.10-1
*** libgamin1_0-0.1.10-1
*** libgamin1-devel-0.1.10-1
*** python-gamin-0.1.10-1
gamin is a portable drop-in replacement
On Dec 18 20:53, Lawrence Mayer wrote:
Is there any way to get noacl functionality when using MS-DOS destination
paths?
My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
C:\cygwin\bin\mkdir.exe /c/foo
creates directory C:\foo with NTFS default permissions inherited
Hi community,
As my (probably) last action before the New Year break (I'll be offline
most of the time until January the 7th), I just uploaded a new Cygwin
1.7 test release, 1.7.0-36.
As announced in my first message about the 1.7 test, just download
http://cygwin.com/setup-1.7.exe and use that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to AMADE Paul Bernard on 12/19/2008 12:40 AM:
updated asciidoc
the asciddoc executable in /usr/bin is empty and does nothing
how should I correct this?
Indeed, so it is :( Probably due to the fact that asciidoc 8.3.1 switched
from a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to David Abrahams on 12/18/2008 7:42 PM:
Can anyone explain why the installer began recommending using *nix line
ending conventions?
Because Unix line endings work out of the box with more programs, and
because it is faster, and because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Steve Rainbird on 12/19/2008 2:22 AM:
When i run a Fuijitsu Cobol program it requires environmental variables
starting with the @ sign.
That is inherently non-portable. POSIX states that Other characters may
be permitted by an
On Dec 19 14:14, Corinna Vinschen wrote:
[...] As usual, please report bugs and problems to the mailing
list cygwin AT
Erm... the mailing list cygwin AT cygwin DOT com.
I also forgot to repeat the pointer to the new online documentation:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new version of the asciidoc package, asciidoc 8.3.1-2, is now available
for download, replacing the broken 8.3.1-1 and leaving 8.2.7-1 as previous.
NEWS:
=
This is a repackage of a new upstream release, which fixes my packaging
bug caused by
On Dec 17 09:39, Andrew Schulman wrote:
After a reboot, I ran
strace -o strace.txt c:\cygwin-1.7\bin\bash.exe --login
and observed the error in the shell that started. The strace output is at
http://home.comcast.net/~aschulman2/cygwin-1.7/strace.txt.bz2 .
Thanks for the strace.
On 12/19/2008 3:27 AM, Eli Zaretskii wrote:
I guess this is an ample opportunity to call for volunteers to come on
board and help maintaining the Cygwin build of Emacs. As of now, the
Cygwin build has some known ``stability issues'' (read: it sometimes
crashes during the build or in routine
On Dec 19 09:38, Andrew Schulman wrote:
On Dec 17 09:39, Andrew Schulman wrote:
After a reboot, I ran
strace -o strace.txt c:\cygwin-1.7\bin\bash.exe --login
and observed the error in the shell that started. The strace output is at
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
Me too, and like you and the OP report, it just works 99.44% of the time.
Of course, since it's not the 21st century yet, many Unixoid programs are
still unable to handle text files properly, hence the remaining 0.66%.
100 - 99.44 =
On Fri, Dec 19, 2008 at 06:34:19AM -0700, Eric Blake wrote:
According to David Abrahams on 12/18/2008 7:42 PM:
Can anyone explain why the installer began recommending using *nix line
ending conventions?
Because Unix line endings work out of the box with more programs, and
because it is faster,
on Fri Dec 19 2008, Eric Blake ebb9-AT-byu.net wrote:
By the way, the program 'd2u' is your friend.
I'm on *nix now to avoid all such issues, but yeah, when I have to run
Cygwin in a VM, it's a thing to keep in mind.
Thanks for all the responses everyone.
--
Dave Abrahams
BoostPro Computing
Mark J. Reed wrote:
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
Me too, and like you and the OP report, it just works 99.44% of the
time. Of course, since it's not the 21st century yet, many Unixoid
programs are still unable to handle text files properly, hence the
remaining
Date: Fri, 19 Dec 2008 10:21:06 -0500
From: Ken Brown kbrown at cornell dot edu
CC: eliz at gnu dot org
On 12/19/2008 3:27 AM, Eli Zaretskii wrote:
I guess this is an ample opportunity to call for volunteers to come on
board and help maintaining the Cygwin build of Emacs. As of now,
From: Andrew DeFaria
Mark J. Reed wrote:
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
Me too, and like you and the OP report, it just works
99.44% of the
time. Of course, since it's not the 21st century yet, many Unixoid
programs are still unable to handle text files
Working (strace2):
pwdgrp::load: \etc\passwd curr_lines 20308
Failing (strace1):
pwdgrp::load: \etc\passwd curr_lines 520
So Cygwin thinks there are only 520 lines in the file, even though it
knows that the filesize is 2490367 bytes.
OK, good. Curious that the bad behavior only
On Dec 19 10:29, Gary R. Van Sickle wrote:
From: Andrew DeFaria
Mark J. Reed wrote:
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
Me too, and like you and the OP report, it just works
99.44% of the
time. Of course, since it's not the 21st century yet, many Unixoid
On 12/19/2008 11:19 AM, Eli Zaretskii wrote:
Yes, Angelo deserves a lot of kudos for his efforts, but unfortunately
much more is needed. For example, even though it is possible to build
a Cygwin version now, if you are willing to install specific versions
of development tools, the following
On Dec 19 12:01, Andrew Schulman wrote:
Working (strace2):
pwdgrp::load: \etc\passwd curr_lines 20308
Failing (strace1):
pwdgrp::load: \etc\passwd curr_lines 520
So Cygwin thinks there are only 520 lines in the file, even though it
knows that the filesize is 2490367
I tested it, and it fixes the error. Nice hunting.
Sure? Did it occur reliably so far and now it doesn't? I thought
it only occurs intermittently. Maybe you could test a while longer...
The error was occurring reliably on the first, and only the first, login shell
after each reboot. I
On Dec 19 12:25, Andrew Schulman wrote:
I tested it, and it fixes the error. Nice hunting.
Sure? Did it occur reliably so far and now it doesn't? I thought
it only occurs intermittently. Maybe you could test a while longer...
The error was occurring reliably on the first, and only
Hello,
I have a cygwin environment, running some software I am writing to talk
to some serial devices.
Somehow, trying to debug why I could not see printf output to console, I
ran a serial port sniffer and voila all of my printf commands are
writing on the serial port.
Any idea how to fix
From: Alex Martin
Hello,
I have a cygwin environment, running some software I am
writing to talk to some serial devices.
Somehow, trying to debug why I could not see printf output to
console, I ran a serial port sniffer and voila all of my
printf commands are writing on the serial
On Fri, Dec 19, 2008 at 2:30 PM, Gary R. Van Sickle wrote:
From: Alex Martin
Hello,
I have a cygwin environment, running some software I am
writing to talk to some serial devices.
Somehow, trying to debug why I could not see printf output to
console, I ran a serial port sniffer and voila
[Followups set to -talk due to apropos but not-necessarily-Cygwin-specific
devolution of the discussion]
From: Corinna Vinschen
On Dec 19 10:29, Gary R. Van Sickle wrote:
From: Andrew DeFaria
Mark J. Reed wrote:
On Fri, Dec 19, 2008 at 4:42 AM, Gary R. Van Sickle wrote:
Me
Well, I was using a port monitor to debug some of the traffic between my
serial device, and my software, when I noticed the output accidentally.
I am not sure when the behavior started. It used to work fine, I was
using printf to debug things, then I turned off all of those printf
statements,
From: Alex Martin
Well, I was using a port monitor to debug some of the traffic
between my serial device, and my software, when I noticed the
output accidentally.
I am not sure when the behavior started. It used to work
fine, I was using printf to debug things, then I turned off
Matt Wozniski wrote:
On Fri, Dec 19, 2008 at 2:30 PM, Gary R. Van Sickle wrote:
From: Alex Martin
Hello,
I have a cygwin environment, running some software I am
writing to talk to some serial devices.
Somehow, trying to debug why I could not see printf output to
console, I ran a serial port
From: Alex Martin
Gary R. Van Sickle wrote:
From: Alex Martin
Well, I was using a port monitor to debug some of the
traffic between
my serial device, and my software, when I noticed the output
accidentally.
I am not sure when the behavior started. It used to work
fine, I was
Gary R. Van Sickle wrote:
From: Alex Martin
Well, I was using a port monitor to debug some of the traffic
between my serial device, and my software, when I noticed the
output accidentally.
I am not sure when the behavior started. It used to work
fine, I was using printf to debug things,
Alex Martin wrote:
Gary R. Van Sickle wrote:
snip
A few gaps that need filling before anything better than SWAGs can
come your
way:
- Is this app a Cygwin app,
No, it is a windows app.
I am using cygwin primarily because I get the /dev/ttyS* devices.
If you're using /dev/ttyS*,
Ken Brown wrote:
And I think Angelo has built CVS versions of emacs 23 with it
Yes, I confirm. I build Emacs-23 weekly.
In the last year many things have changed, and in better.
Now it bootstraps in less than 20 minutes (before, more than an hour).
Also, some strange bootstrap failure
Good afternoon,
Corinna Vinschen wrote:
[...]
Fixed in CVS.
[...]
Closing the loop: I got the cygwin update today and it works for me.
Thanks!
--Glenn S.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
On Dec 18 20:53, Lawrence Mayer wrote:
Is there any way to get noacl functionality when using MS-DOS destination
paths?
My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
C:\cygwin\bin\mkdir.exe /c/foo
creates directory C:\foo with NTFS default permissions inherited from
Lawrence Mayer wrote:
On Dec 18 20:53, Lawrence Mayer wrote:
Is there any way to get noacl functionality when using MS-DOS
destination
paths?
My etc/fstab file (below) applies noacl for UNIX destination paths e.g.
C:\cygwin\bin\mkdir.exe /c/foo
creates directory C:\foo with NTFS default
On 12/19/2008 4:38 PM, Angelo Graziosi wrote:
...and, last but not least, yes we need a Cygwin Emacs maintainer:
There *is* an official emacs maintainer, Steffen Sledz, but there's no
indication that he monitors this list for emacs questions/problems. The
last message I saw from him was to
If I do the following
xx
pid=$!
I get the cygwin pid.
Is there a way of getting the real windows pid?
--
Steve
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Steve Rainbird wrote:
If I do the following
xx
pid=$!
I get the cygwin pid.
Is there a way of getting the real windows pid?
Not directly, no. But 'ps -W' will show you the Windows PID as well.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc.
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely there is a FAQ on this ? haven;t found it though
Gary R. Van Sickle wrote:
Another one who believes what their calendar tells them?
Another one who doubts the calendar and can't do math...
Then riddle me this Andrew: If this were in fact the 21st century (AKA
The Future),
But you see that's the thing. It's not AKA The Future - it's now.
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely there is a FAQ on this ? haven;t found
Larry Hall (Cygwin) wrote:
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely there is a
fred wrote:
Larry Hall (Cygwin) wrote:
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a cygwin1.dll.
I thought surely
On Sat, Dec 20, 2008 at 12:16:52AM -0500, Larry Hall (Cygwin) wrote:
fred wrote:
Larry Hall (Cygwin) wrote:
FAQ: http://cygwin.com/faq/
?
My WAG is that you're building in the source directory which, as the FAQ
says, is a no-no.
ok thanks, but what your saying is that
Larry Hall (Cygwin) wrote:
fred wrote:
Larry Hall (Cygwin) wrote:
fred wrote:
I assume $make install
ok? but something gone wrong,
so manually what is supposed to get copied where ?
dir \i686-pc-cygwin\winsup\cygwin
has a cygwin0.dll,
I thought there is supposed to be a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cygport has been updated to 0.4.3 for Cygwin 1.5, and 0.9.4 for 1.7,
with similar changes to both:
* Requires libtool-2.2 throughout.
* cygpatch() tries with and without --binary.
* lndirs() uses lndir(1) unconditionally.
* Override pushd and popd
Hi community,
As my (probably) last action before the New Year break (I'll be offline
most of the time until January the 7th), I just uploaded a new Cygwin
1.7 test release, 1.7.0-36.
As announced in my first message about the 1.7 test, just download
http://cygwin.com/setup-1.7.exe and use that
On Dec 19 14:14, Corinna Vinschen wrote:
[...] As usual, please report bugs and problems to the mailing
list cygwin AT
Erm... the mailing list cygwin AT cygwin DOT com.
I also forgot to repeat the pointer to the new online documentation:
77 matches
Mail list logo
