Sigh.
On Fri, Mar 19, 2010 at 02:07:33AM -0400, Christopher Faylor wrote:
>Can we please shut this discussion down? The person who had the initial
>problem is satisfied and I've made it clear that no one at
>sourceware.org/cygwin.com is interested in pursuing additional web site
>measures. While
Can we please shut this discussion down? The person who had the initial
problem is satisfied and I've made it clear that no one at
sourceware.org/cygwin.com is interested in pursuing additional web site
measures. While that could change at some point in the past, it is not
going to do so because
On 2010/03/18 8:38 AM, Warren Young wrote:
> Your proposed solutions don't really work.
I disagree. Granted, they are not 100% effective, but since when is
perfection the standard by which all solutions are judged?
> They're crutches which may
> help in some cases, but they don't absolutely and f
On 03/18/2010 05:06 PM, Jason Pyeron wrote:
It seams that svn needs to be able to write the DAC, and if it cannot then svn
up cannot work. This seems to be not the case in the past (or was there some
magic voodoo on my old system?)
Any suggestions on where to start?
Granting Full on the share a
On 2010/03/17 10:28 PM, Dave Korn wrote:
> On 18/03/2010 00:58, Steven Monai wrote:
>
>> As an alternative to setting up SSL on cygwin.com, what about the idea
>> of crypto-signing (e.g. with gnupg) every release of setup.exe, and then
>> posting the signature alongside the binary? I know I would
> Hi,
>
> I recently upgraded a computer running XP Embedded to Cygwin 1.7.1.
> When I ssh from another computer, and run a graphical program (such as
> the calculator included in Win XP), it doesn't display correctly.
>
> If I run the program from a local ssh shell, it does display
correctly.
The mingw-libgcrypt package provides a version of the libgcrypt
library and tools built using the standard windows runtime library
and NOT cygwin. It is (or will be) used by setup.exe and is provided
specifically for that purpose. No other uses are supported. However,
for testing purposes it does p
Libgcrypt is a general purpose cryptographic library based on
the code from GnuPG. It provides functions for all cryptographic
building blocks: symmetric ciphers, hash algorithms, MACs, public
key algorithms, large integer functions, random numbers and a lot
of supporting functions.
[[ compiled u
I upgraded to Cygwin 1.7.1 on a (64-bit) Windows Server 2003 and immediately
ran into trouble. It seems that Perl can no longer shutdown pipes related to
Cygwin executables. Here is some example code:
#!/usr/bin/perl
use strict;
# my $fname = 'Y:\path\to\ratherbigfile.gz';
my $fname = '/cygdrive
On 3/18/2010 7:03 PM, Douglas Seay wrote:
I’ve had some problems, and it looks like it boils down to handling .
(dot) characters. I created a little script to create some files with
dots in various places. This script works fine in my $HOME directory
(C:\cygwin\home\SEAYD). The name is wrong when
I’ve had some problems, and it looks like it boils down to handling .
(dot) characters. I created a little script to create some files with
dots in various places. This script works fine in my $HOME directory
(C:\cygwin\home\SEAYD). The name is wrong when the last character of
the filename i
For those people testing cygwin snapshots, a new release of coreutils,
8.4-2, has been uploaded. 7.0-2 remains current, because the 8.4-2
release depends on features available only in recent snapshots (that is,
don't upgraded if you are still using the current cygwin 1.7.1).
NEWS:
=
This is a
It seams that svn needs to be able to write the DAC, and if it cannot then svn
up cannot work. This seems to be not the case in the past (or was there some
magic voodoo on my old system?)
Any suggestions on where to start?
Granting Full on the share and the directory mitigated this issue. I am un
Yaakov (Cygwin/X) writes:
> This is how I build MySQL:
>
> http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/db/mysql/
>
Thanks for the hint. I still couldn't convince 5.1.45 to build, but
after some fiddling with libtool incompatibilities I was able to
coerce 5.1.39 in
On 03/18/2010 03:16 PM, Charles Wilson wrote:
> Eric Blake wrote:
>> On 03/11/2010 10:18 AM, Eric Blake wrote:
>>> For those people testing cygwin snapshots, a new release of coreutils,
>>> 8.4-1, has been uploaded. 7.0-2 remains current, because the 8.4-1
>>> release depends on features available
Eric Blake wrote:
> On 03/11/2010 10:18 AM, Eric Blake wrote:
>> For those people testing cygwin snapshots, a new release of coreutils,
>> 8.4-1, has been uploaded. 7.0-2 remains current, because the 8.4-1
>> release depends on features available only in recent snapshots (that is,
>> don't upgrade
On Mar 18 14:23, Eric Blake wrote:
> On 03/11/2010 10:18 AM, Eric Blake wrote:
> > For those people testing cygwin snapshots, a new release of coreutils,
> > 8.4-1, has been uploaded. 7.0-2 remains current, because the 8.4-1
> > release depends on features available only in recent snapshots (that
On 03/11/2010 10:18 AM, Eric Blake wrote:
> For those people testing cygwin snapshots, a new release of coreutils,
> 8.4-1, has been uploaded. 7.0-2 remains current, because the 8.4-1
> release depends on features available only in recent snapshots (that is,
> don't upgraded if you are still using
On Thu, Mar 18, 2010 at 03:55:48PM +0100, Schmidt, Oliver wrote:
>Hi Corinna,
>
>> Would you mind to give the latest developer snapshot from
>> http://www.cygwin.com/snapshots/ a try? It tries very carefully to
>> eliminate concurrency problems in the initialization phase.
>
>I see. With the same
On 3/18/2010 11:43 AM, Markus Hoenicka wrote:
> Rance Hall was heard to say:
>
>> this is the old cygwin 1.5 setup still active but unsupported. It may
>> contain the perl version you want.
>>
>> No promised, I don't have 1.5 installed anymore, and dont have the
>> time to look in the archive fo
On 3/11/2010 2:45 AM, Eugen Zalinescu wrote:
My problem is that I cannot start cygwin (with Cygwin.bat). Actually
any cygwin application finishes as soon as I invoke it (or in about
1sec), with no output, as in
D:\cygwin\bin> bash
D:\cygwin\bin>
However, sometimes (I cannot reproduce the b
On 18/03/2010 17:04, Larry Hall (Cygwin) wrote:
> On 3/18/2010 11:51 AM, Cygwin wrote:
>>> 4 [main] perl 3156 D:\Local\Cygwin\bin\perl.exe: *** fatal error -
>>> cygheap base mismatch detected - 0x6120C6E0/0xD4C6E0.
>>> There is not another cygwin DLL on my system, and rebooting does in
>>> fact
On 3/18/2010 11:51 AM, Cygwin wrote:
"Cygwin" <> wrote in message
news:hne7t6$8l...@dough.gmane.org...
About once a month I get something like this:
4 [main] perl 3156 D:\Local\Cygwin\bin\perl.exe: *** fatal error -
cygheap
base mismatch detected - 0x6120C6E0/0xD4C6E0.
This problem is probably
Rance Hall was heard to say:
this is the old cygwin 1.5 setup still active but unsupported. It may
contain the perl version you want.
No promised, I don't have 1.5 installed anymore, and dont have the
time to look in the archive for you, but thats where I'd start.
I still have a 1.5 install
2010.03.18.16:13:51 UT
Hi Gregg and CygWin folks,
I found the PGP/GPG key, and confirmed
the validity of the setup.exe.
As for the blocking, my college hires
Cymphonix to do this for them, and then the
college Information Svces. guys stay com-
pletely away fro
2010.03.18.16:13:51 UT
Hi Gregg and CygWin folks,
I found the PGP/GPG key, and confirmed the validity of the setup.exe.
As for the blocking, my college hires Cymphonix to do this for them, and
then the college Information Svces. guys stay com- pletely away fr
On Thu, Mar 18, 2010 at 10:55 AM, jvsrvcs wrote:
>
> I inherited some code at work that is dependent on a number of .pm that will
> only run with perl 5.8. I can not upgrade the pm's so must use perl 5.8.
>
> I have cygwin installed but it will only let me install perl 5.10.1. I want
> to roll b
I inherited some code at work that is dependent on a number of .pm that will
only run with perl 5.8. I can not upgrade the pm's so must use perl 5.8.
I have cygwin installed but it will only let me install perl 5.10.1. I want
to roll back to perl 5.8. I tried ActiveState perl but it will not
r
Has no one else seen anything like this?
"Cygwin" wrote in message
news:hne7t6$8l...@dough.gmane.org...
About once a month I get something like this:
4 [main] perl 3156 D:\Local\Cygwin\bin\perl.exe: *** fatal error - cygheap
base mismatch detected - 0x6120C6E0/0xD4C6E0.
This problem is proba
On 3/17/2010 9:05 PM, Steven Monai wrote:
On 2010/03/17 6:54 PM, Christopher Faylor wrote:
Oh. Are we still talking about this? I drifted off.
Somebody please wake me when all of this tempest in a bikeshed is over.
I don't understand the reason for the dismissive attitude.
Your proposed s
Hi Corinna,
> Would you mind to give the latest developer snapshot from
> http://www.cygwin.com/snapshots/ a try? It tries very carefully to
> eliminate concurrency problems in the initialization phase.
I see. With the same scenario as in my original posting I trigger an
assertion added by Chris
On 3/18/2010 5:33 AM, Deon Brits wrote:
Good Day,
It is the first time I use Cygwin so hope that I am using the correct
contact details...
I have to support a product called Tivoli Application dependency
discovery manager that uses Cygwin ssh that is on the remote sites to do
a SSH connection.
Oliver,
On Mar 16 13:06, Corinna Vinschen wrote:
> On Mar 16 10:53, Schmidt, Oliver wrote:
> > >No one is doubting that problems exist. That's why we're working
> > >on them.
> >
> > Sorry for again being unclear. The information above was soley meant to
> > complement the cygcheck output - whic
33 matches
Mail list logo
