On Apr 7 22:20, Christopher Faylor wrote:
> On Thu, Apr 07, 2005 at 05:10:14PM -0700, Hans Horn wrote:
> >Nevermind! Sorry, folks - I really didn't mean to upset anybody! Bye then!
>
> No, no. Please. We are looking for a new bash maintainer. We haven't
> heard from the maintainer in a while a
Brian Dessent wrote:
> Furthermore, threads in the past have
> expressed the fact that 2.05b has been very stable and both Ronald and
> others have agreed that any major changes in bash would have to be
> done very carefully so as not to cause instability.
Uhm. No it's not..
Bash 2.05b is so unst
On Apr 8 12:19, David Dindorp wrote:
> To be fair, this is probably more a Cygwin DLL problem than a bash
> problem, or perhaps a "bash hasn't kept up with changes in Cygwin
> because the maintainer haven't had the time" problem. It's running
> quite stable under 1.5.10, it sucks with 1.5.12 and
David Dindorp wrote:
> Uhm. No it's not..
> Bash 2.05b is so unstable under Cygwin that it classifies as a
> volatile chemical. At least if you put it under a lot of pressure -
> a normal users everyday use it may cope fine with, which is probably
> how it's used by most people in here anyway.
>
Brian Dessent wrote:
> David Dindorp wrote:
>> Uhm. No it's not..
>> Bash 2.05b is so unstable under Cygwin that it classifies as a
>> volatile chemical. At least if you put it under a lot of pressure -
>> a normal users everyday use it may cope fine with, which is probably
>> how it's used by mo
Corinna Vinschen wrote:
> On Apr 8 12:19, David Dindorp wrote:
>> To be fair, this is probably more a Cygwin DLL problem than a bash
>> problem, or perhaps a "bash hasn't kept up with changes in Cygwin
>> because the maintainer haven't had the time" problem. It's running
>> quite stable under 1.5
$ uname -a
CYGWIN_NT-5.1 PHB 1.5.14(0.126/4/2) 2005-04-01 13:40 i686 unknown
unknown Cygwin
$ ln -s /bin /tmp
$ cygpath -w /tmp/bin
C:\cygwin\bin
$ cygpath -w /tmp/bin/ls.exe
C:\cygwin\tmp\bin\ls.exe
-
Worked fine in 1.5.13.
– Michael
--
Unsubscribe info:
Michael Schaap wrote on Friday, April 08, 2005 4:03 PM:
> $ uname -a
> CYGWIN_NT-5.1 PHB 1.5.14(0.126/4/2) 2005-04-01 13:40 i686 unknown
> unknown Cygwin
>
> $ ln -s /bin /tmp
>
> $ cygpath -w /tmp/bin
> C:\cygwin\bin
>
> $ cygpath -w /tmp/bin/ls.exe
> C:\cygwin\tmp\bin\ls.exe
Already reporte
On Fri, Apr 08, 2005 at 03:06:02PM +0200, David Dindorp wrote:
>Corinna Vinschen wrote:
>> On Apr 8 12:19, David Dindorp wrote:
>>> To be fair, this is probably more a Cygwin DLL problem than a bash
>>> problem, or perhaps a "bash hasn't kept up with changes in Cygwin
>>> because the maintainer ha
Original Message
>From: David Dindorp
>Sent: 08 April 2005 14:06
>
> If you can tell me how to proceed from here, I'd be happy to throw in
> a bunch of manhours to try and find out what's wrong.
http://cygwin.com/acronyms#PPAST
I'm surprised, myself, I find bash very reliable.
On 8-Apr-2005 16:24, Jörg Schaible wrote:
Michael Schaap wrote on Friday, April 08, 2005 4:03 PM:
$ uname -a
CYGWIN_NT-5.1 PHB 1.5.14(0.126/4/2) 2005-04-01 13:40 i686 unknown
unknown Cygwin
$ ln -s /bin /tmp
$ cygpath -w /tmp/bin
C:\cygwin\bin
$ cygpath -w /tmp/bin/ls.exe
C:\cygwin\tmp\bin\ls.
On Apr 4 18:05, Vincent Dedun wrote:
grepping cygserver debug output, show that, with 2 child process
sharing mutex, wakeup is called first, then 2 msleep are called. So
when msleep is called, wakeup has already been called, and msleep has
to sleep forever.
What you see is intermixed debug output
>> If you can tell me how to proceed from here, I'd be happy to throw in
>> a bunch of manhours to try and find out what's wrong.
>
> If you are happy to throw a bunch of manhours to try and find out
what's
> wrong, then the solution is obvious -- learn cygwin that well.
Manhours. Not entire lif
>> If you can tell me how to proceed from here, I'd be happy to throw in
>> a bunch of manhours to try and find out what's wrong.
>
> http://cygwin.com/acronyms#PPAST
Obviously, if I were able to produce a simple testcase, I would have.
Duh ;-).
--
Unsubscribe info: http://cygwin.com/ml/#
Original Message
>From: David Dindorp
>Sent: 08 April 2005 16:14
>>> If you can tell me how to proceed from here, I'd be happy to throw in
>>> a bunch of manhours to try and find out what's wrong.
>>
>> http://cygwin.com/acronyms#PPAST
>
> Obviously, if I were able to produce a simple
> There is one potential problem in that we may need to adapt Pierre's
> patch to prevent problems with pid reuse to 3.0 if it is released.
Besides that, looking at ftp://ftp.gnu.org/pub/gnu/bash/bash-3.0-
patches/, I see 16 patches. I hope all of those will be applied to a
Cygwin bash 3.0 packa
Hi !
I am trying to get away my mounts in the gegistry on HKEY_LOCAL_MACHINE
etc. as I was told the version of cygwin I am running should not have
them. From cygwin.bat I type umount -S
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\Program
Options\ with no result. Also I
Elin Aronsen wrote:
> I am trying to get away my mounts in the gegistry on HKEY_LOCAL_MACHINE
> etc. as I was told the version of cygwin I am running should not have
> them. From cygwin.bat I type umount -S
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\Program
> Options\ with no
At 01:17 PM 4/8/2005, you wrote:
> Hi !
>
>I am trying to get away my mounts in the gegistry on HKEY_LOCAL_MACHINE
>etc. as I was told the version of cygwin I am running should not have
>them. From cygwin.bat I type umount -S
>HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\Pro
RE:
I just upgraded to cygwin 1.5.14 from 1.5.12, and python
(version 2.4 in both cases) stopped being able to import
thru symlinks.
Test case: in a directory containing a symlink to foo.py,
python
import foo
complains "no module named foo.py"; if I copy the file to
Hi !
OK, if I do not have to change the mounts, I will just leave them.
Do you think it is necessary to do anything with the warning of a bad
signal mask at 19005 or can it not result in problems when running
cygwin ? When uninstalling cygwin are you supposed to use umount before
deletin
[snip]
> (3) Thinking that the realpath bug might be a key
> to the python import-thru-symlinks problem,
> I ran a simple test on recent cygwin/python
> combinations, finding:
>
> Cygwin version Python version realpath Import
> 1.5.xx: 2.yy:
RE:
> (3) Thinking that the realpath bug might be a key
> to the python import-thru-symlinks problem,
> I ran a simple test on recent cygwin/python
> combinations, finding:
>
> Cygwin version Python version realpath Import
> 1
I have cygwin installed on four win2000 machines I use. On three of them
running "setup.exe" on my usual mirror site results in "Nothing to
install/update". The fourth machine happily updated several files, including
the base cygwin, to the latest release. Choosing another mirror site get
either "n
At 04:17 PM 4/8/2005, you wrote:
>I have cygwin installed on four win2000 machines I use. On three of them
>running "setup.exe" on my usual mirror site results in "Nothing to
>install/update". The fourth machine happily updated several files, including
>the base cygwin, to the latest release. Choos
/usr/include/sys/features.h defines _POSIX_TIMERS, presumably to
indicate that POSIX timers are supported. There seems to be something
missing, though.
Under the influence of _POSIX_TIMERS, /usr/include/time.h defines
function prototypes for clock_gettime() and clock_getres() (and a few
others). c
On Fri, Apr 08, 2005 at 10:32:19PM +0200, Keith Moore wrote:
>/usr/include/sys/features.h defines _POSIX_TIMERS, presumably to
>indicate that POSIX timers are supported. There seems to be something
>missing, though.
>
>Under the influence of _POSIX_TIMERS, /usr/include/time.h defines
>function prot
Christopher Faylor cygwin.com> writes:
>
> The latest cygwin snapshot at:
>
> http://cygwin.com/snapshots/
>
> should fix the startup problems that some people were seeing. I'd
> appreciate feedback on that fact so that we can get a new release
> out quickly.
>
> Please try the snapshot.
>
>
"Kirschner, Paul E UTRC" wrote:
> I have cygwin installed on four win2000 machines I use. On three of them
> running "setup.exe" on my usual mirror site results in "Nothing to
> install/update". The fourth machine happily updated several files, including
> the base cygwin, to the latest release. C
On Apr 8 17:10, [EMAIL PROTECTED] wrote:
> it works for me too for the testcase i provided last time.
>
> But there is still some issues when you run several semaphore-using
> program at the same time.
[Insert swear-word here]
> to reproduce it :
> -compil last testcase with this modification
At 04:57 AM 4/7/2005, you wrote:
>I downloaded ALL files, apache and latex to /My_Temp_Dir and installed them.
>/cygwin/ has about 801 MB.
>
>When using the cygwin command box, I get no response:
>bash-2.05$ pcrgrep -V
>bash: pcrgrep: command not found
>
>The /var/log/setup.log.full tells me:
>2005
At 03:42 AM 4/7/2005, you wrote:
>Sorry, I've searched the lists quite a bit as well as the documenation and
>other online sources that I could find. I couldn't find anything that was both
>similar to my problem and had a solution that I could understand. I've been
>trying to add domain users to
At 07:34 PM 3/31/2005, you wrote:
>
>Hello,
>
>I have cygwin installed on a windows 2003 enterprise edition domain
>controller.
>
>The version of cygwin is:
>
>$ uname -a
>CYGWIN_NT-5.2 server 1.5.13(0.122/4/2) 2005-03-01 11:01 i686 unknown
>unknown Cygwin
>
>I ran the ssh-host-config -y script
On Fri, 8 Apr 2005, Larry Hall wrote:
> At 04:57 AM 4/7/2005, you wrote:
> >I downloaded ALL files, apache and latex to /My_Temp_Dir and installed them.
> >/cygwin/ has about 801 MB.
> >
> >When using the cygwin command box, I get no response:
> >bash-2.05$ pcrgrep -V
> >bash: pcrgrep: command not
Hello,
Using cygwin, I'm building the code from the book, Beginning Linux
Programming. I ran across a bug that chewed up a considerable amount of my
time. As a newbie, perhaps I'm doing something wrong. On the chance that
this is a bug, I hope I can save others from grief.
Chapter 4 of the book i
Hi there, not sure whether this is a cygwin or vim issue. I have a file that
contains "hello" (note it's really a upside down ,,). When I cat the file, it
displays correctly like when I use notepad. But when I'm in vim editing the
file, it shows up as ~Shello~T.
Very likely it's not a cygwin is
Larry wrote:
> The problem I found is that the Makefile contains the statement
> 'TMP=tmpnam'. The build fails after the program builds a file $(TMP).
> Apparently, the local tmpnam.exe file that gets built gets called when make
> attempts to build the remaining files. (Is there a way to disable t
On Fri, 8 Apr 2005, ERIC HO wrote:
> Hi there, not sure whether this is a cygwin or vim issue. I have a file
> that contains "hello" (note it's really a upside down ,,). When I cat
> the file, it displays correctly like when I use notepad. But when I'm in
> vim editing the file, it shows up as ~Sh
Brian,
Did you create two identical .c files, one named program.c and the
other named tmpnam.c? I get the same error you report when I haven't
created the tmpnam.c file.
I appreciate your additional helpful comments. I wish I was more
experienced to know how to look further into debugging this.
What is the correct mailing list command-address format? In particular,
I can't seem to get the syntax right for message index so I can use it
correctly in various contexts.
Here is the message of interest:
http://cygwin.com/ml/cygwin/2005-04/msg00265.html
And here are the formats that I have t
Nothing I can change the cygdrive prefix. I recall
being able to do it before.
# show current mount table:
/> mount
C:\cygwin\bin on /usr/bin type system (binmode)
C:\cygwin\lib on /usr/lib type system (binmode)
C:\cygwin on / type system (binmode)
c: on /cygdrive/c type user (binmode,noumount)
y
Larry wrote:
> Did you create two identical .c files, one named program.c and the
> other named tmpnam.c? I get the same error you report when I haven't
> created the tmpnam.c file.
>
> I appreciate your additional helpful comments. I wish I was more
> experienced to know how to look further into
On Fri, 8 Apr 2005, John Sellers wrote:
> What is the correct mailing list command-address format? In particular,
> I can't seem to get the syntax right for message index so I can use it
> correctly in various contexts.
>
> Here is the message of interest:
>
> http://cygwin.com/ml/cygwin/2005-04/
ChrisW wrote:
> Nothing I can change the cygdrive prefix. I recall
> being able to do it before.
You're getting confused because you can set the cygdrive prefix both
system-wide and per-user, and the latter takes precedent.
> c: on /cygdrive/c type user (binmode,noumount)
> y: on /cygdrive/y ty
Brian wrote:
> Anyway, assuming you're at the cygwin bash prompt, try the following
> $ make -v
> GNU Make 3.80
> Copyright (C) 2002 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR
That fixed my problem. Thanks so much.
--- Brian Dessent <[EMAIL PROTECTED]> wrote:
> ChrisW wrote:
>
> > Nothing I can change the cygdrive prefix. I
> recall
> > being able to do it before.
>
> You're getting confused because you can set the
> cygdrive prefix both
> system-wide and per-user
Hi Igor, thank you for the suggestion. But I failed to find the proper setting
for the tenc and fenc.
I ended up setting up a vim mapping to change it as follows:
map #8 :g/~S/s//"/g^M:g/~T/s//"/g^M:g/~Q/s//\'/g^M:g/~R/s//\'/g^M
The characters are 147, 148, 145, 146 in decimal.
Not an elegant so
Larry wrote:
> I get the exact same results when I run those commands.
>
> Perhaps I had an error in my Makefile. Can you please try the following
> Makefile that still generates the same error for me?
Okay, I realized that I'd named one of the source files "tmpname.c" and
not "tmpnam.c" in whic
Under what conditions does setup not enable the Next button?
It appears to have successfully finished the checksum and provide a list
of packages, but never "enables" the Next button.
I'm trying to install locally via UNC path which is a share in case that
makes a difference.
--
Ken Shaffer
Thank you very much for your help with this, Brian.
I understand and agree with your analysis.
Larry
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
50 matches
Mail list logo
