On Mon, Jul 06, 2009 at 07:03:11AM -0600, Eric Blake wrote:
>But on cygwin 1.7, when you attempt to create multiple writers to a single
>fifo, the second writer creates an fd just fine but then fails on any
>attempt to write to that fd:
I see the problem but I don't know how to fix it yet. It may
On Fri, Jul 3, 2009 at 6:31 PM, Dave Korn wrote:
> Yep; click on "Keep" first thing of all, that makes setup keep all your
> current choices, then manually choose the new version of the particular file
> you want. Should get a warning if there's any unsatisfied dependencies,
> otherwise everythin
Paul Bibbings wrote:
> The following code [ ... ] appears to be closely related to (if not
> duplicating)
> GCC Bugzilla Bug 35640
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35640).
Yep, sure looks like it to me. I don't think I'll have time to look at this
before 4.3.3-1, but I'll try an
The following code compiles successfully using gcc-4.3.2 (Cygwin,
gcc 4.3.2 20080827 (beta) 2) running under Windows Vista (Ver 6.0
Build 6002 Service Pack 2).
// inaccessible_test.cpp
class X { };
class Y : protected X { };
class Z : private X {
public:
void f(Y *);
};
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 10:55:40AM -0700, Jerry DeLisle wrote:
Christopher Faylor wrote:
--- snip ---
I will try the manual process you suggested after I figure out how to get the
snapshot and when it is available.
Bare in mind that I am using the broken environment t
On Mon, Jul 06, 2009 at 10:55:40AM -0700, Jerry DeLisle wrote:
>Christopher Faylor wrote:
>--- snip ---
>>> I will try the manual process you suggested after I figure out how to get
>>> the
>>> snapshot and when it is available.
>>
>
>Bare in mind that I am using the broken environment to do thi
Christopher Faylor wrote:
--- snip ---
I will try the manual process you suggested after I figure out how to get the
snapshot and when it is available.
Bare in mind that I am using the broken environment to do this. I managed to
extract the snapshot and replace the cygwin1.dll while not run
Oops, my bad. I forgot about xargs. No wonder I couldn't get it to work.
Glad I asked anyway. I learned a some useful stuff, especially "grep -r".
thanks!
km4hr wrote:
>
> Do pipes work in cygwin in the usual way?
>
> Why doesn't the following command works on HP Unix? Why not cygwin?
>
> f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
km4hr writes:
> Do pipes work in cygwin in the usual way?
>
> Why doesn't the following command works on HP Unix? Why not cygwin?
>
> find .|grep "hello"
>
> I get no output from this command even though I'm sure the word "hello" is
> in some files.
km4hr wrote on Monday, July 06, 2009 12:13 PM:
> Do pipes work in cygwin in the usual way?
>
> Why doesn't the following command works on HP Unix? Why not cygwin?
>
> find .|grep "hello"
>
> I get no output from this command even though I'm sure the word
"hello" is
> in some files.
>
> What I w
On Mon, Jul 06, 2009 at 10:13:12AM -0700, km4hr wrote:
>
>Do pipes work in cygwin in the usual way?
>
>Why doesn't the following command works on HP Unix? Why not cygwin?
>
>find .|grep "hello"
>
>I get no output from this command even though I'm sure the word "hello" is
>in some files.
>
>What I w
On Mon, Jul 6, 2009 at 1:13 PM, km4hr wrote:
>
> Do pipes work in cygwin in the usual way?
Pipes on Cygwin work in the usual way. You seem to misunderstand how
find and grep work.
> Why doesn't the following command works on HP Unix? Why not cygwin?
> I get no output from this command even thou
On Mon, Jul 06, 2009 at 10:00:22AM -0700, Jerry DeLisle wrote:
>Maybe this warrants a cygwin1.dll release.
It would be premature to make a release without verifying that it fixes the
problem.
>I will try the manual process you suggested after I figure out how to get the
>snapshot and when it is
Do pipes work in cygwin in the usual way?
Why doesn't the following command works on HP Unix? Why not cygwin?
find .|grep "hello"
I get no output from this command even though I'm sure the word "hello" is
in some files.
What I want this command to do is find all files in all sub-directories an
Jerry DeLisle wrote:
> I will try the manual process you suggested after I figure out how to
> get the snapshot and when it is available.
Look here: http://cygwin.com/snapshots/
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cy
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 12:32:16AM -0400, Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
Jerry DeLisle wrote:
I am making the switch to 1.7. I started with a clean windows (nt4)
environment and went through the usual run of setup
On Mon, Jul 06, 2009 at 06:19:55AM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Eric Blake on 7/6/2009 6:14 AM:
>> A new release 6.0.3-2 for readline and libreadline7 is now available for
>> use in cygwin 1.7, replacing 6.0.3-1. Cygwin 1.5 users are unaf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's been a lot of interest in this over the years, but I've found
no reports of success. The following involves a number of hacks, but
it works, which may be of use to some.
1) Download and install MIT Kerberos for Windows -- I used
kfw-3-2-2.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Karl M on 7/6/2009 9:18 AM:
>>
> On a Vista Business SP2 machine, I just updated and received the following
> when starting bash. Rolling back eliminated the symptoms.
You didn't get the desired upgrade:
> libreadline6 5.2.13-11
On Mon, Jul 06, 2009 at 12:32:16AM -0400, Christopher Faylor wrote:
>On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
>>Jerry DeLisle wrote:
>>> I am making the switch to 1.7. I started with a clean windows (nt4)
>>> environment and went through the usual run of setup-1.7 downloaded toda
> Date: Mon, 6 Jul 2009 06:19:55 -0600
> From: Eric Blake
> Subject: Re: [ANNOUNCEMENT] [1.7] Updated: readline-6.0.3-2,
> libreadline7-6.0.3-2
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Eric Blake on 7/6/2009 6:14 AM:
>> A new release 6.0.3-2 for readline and libreadlin
On Mon, Jul 06, 2009 at 12:42:20PM +0200, Kaul, Martin wrote:
>Hi,
>
>currently I try to compile cygwin-1.7.0-50.
>
>The make fails with the following error:
>
>
>Making in mingwex...
>make[4]: Entering directory
>`/home/mkaul/toolchain/cygwin-1.7.0-50/i686-pc-cygwin/winsup/mingw/
Hello,
we're deploying an unattended installation of Cygwin to some of our
testmachines. On goal is to have SSH access to those machines, so we put a
customizing script to "/etc\profile.d" which then runs at 1st start
involving the command "ssh-host-config -y -c "tty ntsec" -w
"$RANDOM_PASS"".
E
When I built libgfortran from the current gcc-4.5 snapshot, with cygwin
1.7 updated as of yesterday, headers were required from the libstdc++
#include but the path wasn't active. Is this to be expected?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/6/2009 7:03 AM:
> But on cygwin 1.7, when you attempt to create multiple writers to a single
> fifo, the second writer creates an fd just fine but then fails on any
> attempt to write to that fd:
>
> $ mkfifo fifo
> $ (exe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My earlier request for bi-directional named pipes is not portable (POSIX
does not require it), so I don't care if we delay it until later. But
here is a case that (usually) works in 1.5 but now (always) fails in 1.7,
and which obeys POSIX as far as I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/6/2009 6:14 AM:
> A new release 6.0.3-2 for readline and libreadline7 is now available for
> use in cygwin 1.7, replacing 6.0.3-1. Cygwin 1.5 users are unaffected by
> this change.
>
> Please check the mailing lists - if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new release 6.0.3-2 for readline and libreadline7 is now available for
use in cygwin 1.7, replacing 6.0.3-1. Cygwin 1.5 users are unaffected by
this change.
NEWS:
=
This is a packaging update, using the new binutils to hopefully alleviate
some
Hi,
currently I try to compile cygwin-1.7.0-50.
The make fails with the following error:
Making in mingwex...
make[4]: Entering directory
`/home/mkaul/toolchain/cygwin-1.7.0-50/i686-pc-cygwin/winsup/mingw/mingw
ex'
make[4]: Nothing to be done for `all'.
make[4]: Leaving direct
On Jul 5 11:06, Ian Kelling wrote:
> In the ssh package there is a bug in /usr/bin/ssh-host-config where if
> you select a valid password spaces or punctuation that bash knows of, it
> will fail and you could possibly shoot yourself in the foot due to
> evaling your password. I don't know who i
On Jul 5 13:57, Dave Korn wrote:
> Pedro Izecksohn wrote:
> > Will it be implemented in Cygwin someday?
>
> If you think she can see into the future, shouldn't you be asking something
> more interesting than whether cygwin will ever support rlimit, like what next
> week's lottery numbers will
31 matches
Mail list logo
