Cygwin hang related to "FIFO" (?) during "File::BOM" test in CPAN

I've been trying to install the perl CPAN module "File::BOM" for several days, now, and keep running into a hang under Cygwin (I can install it successfully under linux). I've tried updating cygwin software as well as, seemingly, unrelated CPAN modules, but it's still reliably hanging during the

Re: strange cygstart bug with current Cygwin versions

On Mon, Feb 06, 2006 at 11:40:22PM +0100, Michael Schaap wrote: > What we basically need to do, is copy the Cygwin environment to the > Windows environment, taking care of path conversion for all the > appropriate variables. Maybe start with: http://www.cygwin.com/ml/cygwin-patches/2005-q4/msg000

Re: problems with exit codes on 64-bit Windows XP Pro x64

Samuel Thibault <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Kevin Layer, le Mon 06 Feb 2006 14:37:00 -0800, a écrit : >> Content-Description: bug.c >> > /* demonstrate a bug in capturing the exit code from shell */ >> > main (int argc, char *argv[]) >> > { >> > int docommand(char *), res; >> >

Re: problems with exit codes on 64-bit Windows XP Pro x64

Hi, Kevin Layer, le Mon 06 Feb 2006 14:37:00 -0800, a écrit : Content-Description: bug.c > /* demonstrate a bug in capturing the exit code from shell */ > main (int argc, char *argv[]) > { > int docommand(char *), res; > > if (argc > 1) { > res = docommand(argv[1]); > prin

Re: problems with exit codes on 64-bit Windows XP Pro x64

[Interestingly, the text of my message was stripped out... here it is] I'm running the latest cygwin (1.5.19, see cygcheck below). My application is a native Windows app (64 and 32-bit). It includes no cygwin libraries and is not compiled with cygwin's gcc. When I execute cygwin programs from m

Re: strange cygstart bug with current Cygwin versions

On 6-Feb-2006 22:29, David Picton wrote: > On 2/3/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: > >> Sounds like an instance of >> ... Does it work if >> you "cygstart cmd" and then start word from that cmd shell? If you get >> the same sympto

problems with exit codes on 64-bit Windows XP Pro x64

/* demonstrate a bug in capturing the exit code from shell */ #include #include #include #include #include #include #define _POSIX_ #include #include #include main (int argc, char *argv[]) { exit(1); } /* demonstrate a bug in capturing the exit code from shell */ #include #include

[ANNOUNCEMENT] New Package: jikes-1.22 -- Fast Java compiler adhering to language and VM specifications

PACKAGE DESCRIPTION === Home page: http://www.sourceforge.net/project/jikes License : IBM Public License (OSI approved) IBM's Java compiler (now Open Source) that translates Java source files as defined in The Java Language Specification (Addison-Wesley, 1996) into the bytecoded

[ANNOUNCEMENT] New package: httptunnel-3.3 -- Tunnel data stream in HTTP requests

PACKAGE DESCRIPTION === Home page: http://www.nocrew.org/software/httptunnel.html License : GPL Creates a bidirectional virtual data stream tunnelled in HTTP requests. The requests can be sent via a HTTP proxy if so desired. This can be useful for users behind restrictive firewa

Re: Best Practice for file ownership and permissions?

> I frequently encounter problems due to file ownership and permissions > for the "system" files in /usr, /bin, /sbin/ /etc, and so forth. For > example, when I type > su Administrator > cygwin responds > /usr/bin/su: /bin/bash: Permission denied Not quite the answer to your original

RE: Bash Window Geometry

Corinna wrote: > On Feb 6 17:34, Bubba Jones wrote: >> On Mon, 6 Feb 2006 12:13:43 -0500 (EST) Igor Peshansky > <[EMAIL PROTECTED]> wrote: >>> On Mon, 6 Feb 2006, Bubba Jones wrote: >>> Is it possible to tell the bash prompt where I want it positioned on my desktop? Using X Windows I sp

Best Practice for file ownership and permissions?

I frequently encounter problems due to file ownership and permissions for the "system" files in /usr, /bin, /sbin/ /etc, and so forth. For example, when I type su Administrator cygwin responds /usr/bin/su: /bin/bash: Permission denied I know enough to have done mkpasswd -l

Re: strange cygstart bug with current Cygwin versions

On 2/3/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: > On Fri, 3 Feb 2006, David Picton wrote: > > > I have encountered a strange bug when starting Microsoft Word when it is > > started by the cygstart command, e.g. "cygstart Index.doc", with the > > current version of the Cygwin dll. > > > > The s

Re: Latest update trashed my cygwin install

Thanks for the reply. Reinstalling package 'base-files' seems to have restored normal operation. I found the install logs and can rerun the failed postinstall scripts. One question: Can the installer be fed a list of packages to install, or otherwise configured with a different default set of

Re: Latest update trashed my cygwin install

> I updated and when it was running postinstall I got a large number of > "Entry point not found in cygwin1.dll" popups. Now bash comes up > in /usr/bin instead of my home directory and is badly hosed. > /etc/profile is gone, and all the cygwin directories are missing > from $PATH. The bulk of yo

Re: Issue, most possibly with new Readline

On 2/6/06, Zach Gelnett <[EMAIL PROTECTED]> wrote: > On 2/6/06, Eric Blake <[EMAIL PROTECTED]> wrote: > > > After installing the latest readline updates (that fixed the earlier > > > prompt issue) I'm finding an issue with the vi command line interface. > > > > > > Basically, when I hit [ESC] then

Latest update trashed my cygwin install

I updated and when it was running postinstall I got a large number of "Entry point not found in cygwin1.dll" popups. Now bash comes up in /usr/bin instead of my home directory and is badly hosed. /etc/profile is gone, and all the cygwin directories are missing from $PATH. What I'd like to do is

Re: rxvt readme?

On Feb 6 10:10, beau wrote: > Hi all, > > I'm trying to get rxvt set up on a new install; can't seem to find the > rxvt readme. I thought it should be in /usr/doc/Cygwin; nothing but > tetex readmes there. All clues greatly appreciated. /usr/share/doc? Corinna -- Corinna Vinschen

Re: rxvt readme?

Sorry for the noise. Sending the note triggerred a better google search string, which in turn led to an archived post from Igor with a little grep magic that did the trick. cygcheck -l rxvt | grep README Cheers, On 2/6/06, beau <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm trying to get rxvt set

rxvt readme?

Hi all, I'm trying to get rxvt set up on a new install; can't seem to find the rxvt readme. I thought it should be in /usr/doc/Cygwin; nothing but tetex readmes there. All clues greatly appreciated. -- Robert Thomas ("beau") Hayes Link (c)2006ISR http://www.semanticrestructuring.com/ Discussion

Re: Bash Window Geometry

Reid Thompson wrote: rxvt takes -geometry as a parameter -- it also provides a much better interface than CMD.EXE forgot to mention that rxvt will run natively or with X. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.h

Re: Bash Window Geometry

On Feb 6 17:34, Bubba Jones wrote: > On Mon, 6 Feb 2006 12:13:43 -0500 (EST) Igor Peshansky <[EMAIL PROTECTED]> > wrote: > > On Mon, 6 Feb 2006, Bubba Jones wrote: > > > > > Is it possible to tell the bash prompt where I want it positioned on my > > > desktop? Using X Windows I specify size and

Re: Bash Window Geometry

rxvt takes -geometry as a parameter -- it also provides a much better interface than CMD.EXE -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http:

Re: Bash Window Geometry

On Mon, 6 Feb 2006, Bubba Jones wrote: > On Mon, 6 Feb 2006 12:13:43 -0500 (EST) Igor Peshansky <[EMAIL PROTECTED]> > wrote: While you're at it, . Thanks. > > On Mon, 6 Feb 2006, Bubba Jones wrote: > > > > > Is it possible to tell the bash prompt wher

Re: Bash Window Geometry

On Mon, 6 Feb 2006 12:13:43 -0500 (EST) Igor Peshansky <[EMAIL PROTECTED]> wrote: > On Mon, 6 Feb 2006, Bubba Jones wrote: > > > Is it possible to tell the bash prompt where I want it positioned on my > > desktop? Using X Windows I specify size and location with "--geometry". > > Is there a

Re: Porting from SUN Solaris to Cygwin

Lerohl, John K wrote: > We're porting several hundred SLOCs from a SUN Solaris environment to > Windows XP PCs. The initial port was done with MKS Toolkit on lab > machines. We're looking at using Cygwin for cost reasons. We have a > hundred or so users with desktops outside the lab. > > We'

Re: Bash Window Geometry

On Mon, 6 Feb 2006, Bubba Jones wrote: > Is it possible to tell the bash prompt where I want it positioned on my > desktop? Using X Windows I specify size and location with "--geometry". > Is there anything comparable under MS Windows? First off, . Thanks.

Porting from SUN Solaris to Cygwin

We're porting several hundred SLOCs from a SUN Solaris environment to Windows XP PCs. The initial port was done with MKS Toolkit on lab machines. We're looking at using Cygwin for cost reasons. We have a hundred or so users with desktops outside the lab. We're getting an odd error when we try

Re: default PATH

> Try opening a cmd.com window in c:\cygwin\bin (or whatever it is > named), then running 'bash --login -xv' to see every command executed > by bash during startup. Maybe that will help you pinpoint the > culprit. This really helps understand why it takes so long to open a bash shell, the login

Re: Issue, most possibly with new Readline

On 2/6/06, Eric Blake <[EMAIL PROTECTED]> wrote: > > After installing the latest readline updates (that fixed the earlier > > prompt issue) I'm finding an issue with the vi command line interface. > > > > Basically, when I hit [ESC] then fwd slash (/) to search through the > > history, it throws my

Bash Window Geometry

Is it possible to tell the bash prompt where I want it positioned on my desktop? Using X Windows I specify size and location with "--geometry". Is there anything comparable under MS Windows? _Get your FREE Budweiser E-mail accoun

Re: default PATH

> I upgrade to 1.5.19-4 and my default PATH has changed: > > PATH is "inherited" from my WinXP environment as usual but it is not > prepend with "/bin" like before the upgrade, and is now appended with > ".". > I cannot find where this happen (my .bashrc is unchanged). Try opening a cmd.com windo

Re: Issue, most possibly with new Readline

> After installing the latest readline updates (that fixed the earlier > prompt issue) I'm finding an issue with the vi command line interface. > > Basically, when I hit [ESC] then fwd slash (/) to search through the > history, it throws my cursor back to get beginning of the line (on top > of the

default PATH

I upgrade to 1.5.19-4 and my default PATH has changed: PATH is "inherited" from my WinXP environment as usual but it is not prepend with "/bin" like before the upgrade, and is now appended with ".". I cannot find where this happen (my .bashrc is unchanged). Also, when I start cygwin (shell in rxv

Re: Prompt issue within cygwin

>Chet Ramey, the upstream readline maintainer, FINALLY admitted that his >routines have display bugs when readline is compiled with multi-byte >support, and when a single-line prompt contains invisible characters. The >problem stems from the fact that there is no reliable way to determine >which c

List posting (Was Re: fwilson00hotmail.com)

On Mon, 6 Feb 2006, Fred Wilson wrote: > Apologies for the intrusion. > > I have signed up for teh cygwin mailing list and am currently getting > list emails. > > However, none of the message I authr and send to the list at > cygwincygwin.com are making it to the list. (I neither see them in my >

Re: 1.5.19+: symlink bug

On Feb 3 22:59, Corinna Vinschen wrote: > On Feb 3 16:29, Eric Blake wrote: > > > > behavior is the same, and it is cygwin doing it. It appears that when > > > > both TESTLINK.lnk and TESTLINK.exe.lnk exist, lstat("TESTLINK") > > > > is picking up the contents of TESTLINK.exe.lnk rather than the

Re: Cygwin fork implementation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Sudhahar on 2/6/2006 5:33 AM: > Hi, >In Cygwin fork code the statement > > int res = setjmp (grouped.ch.jmp); > if (res) > res = fork_child (grouped.ch.parent, grouped.first_dll, > grouped.load_dlls); > else > res = fork_

Re: gdb hangs

Vitaly Provodin wrote: > I am trying to debug Win32 dll. > Actually, I exercised setting breakpoint in dynamically loaded libraries and > used the pending breakpoints feature of gdb. It properly works on Linux but > on Windows I get the promising start message "Starting program:…" and > gdb succes

Re: Prompt issue within cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 1/24/2006 7:12 AM: > > Shoot - the bug is still not fixed upstream; I reproduced it with > bash-3.1-1, readline-5.1-1, and rxvt-2.7.10-6. One of these days, I hope > to be able to sit down and figure out where readline is

Cygwin fork implementation

Hi, In Cygwin fork code the statement int res = setjmp (grouped.ch.jmp); if (res) res = fork_child (grouped.ch.parent, grouped.first_dll, grouped.load_dlls); else res = fork_parent (grouped.ch.parent, grouped.first_dll, grouped.load_dlls, esp, grouped.ch); avoids the fork being cal

gdb hangs

I am trying to debug Win32 dll. Actually, I exercised setting breakpoint in dynamically loaded libraries and used the pending breakpoints feature of gdb. It properly works on Linux but on Windows I get the promising start message "Starting program:…" and gdb successfully hangs. Here is a log of gd

Re: Cygwin 1.5.19 breaks my app

I have got to a similar problem with Cygwin having same symptoms. I have found that there was a reported problem with a strings in libstdc++.la, if your application is using dlls. It is really awfull bug to identify... See this links for details: http://sourceware.org/ml/cygwin/2006-01/msg01352.ht

Re: how to avoid error dialog during app crash when non-interactive

Hans Horn wrote: > I have an app build with gcc -mno-cygwin, that constantly bombards me with > error dialogs as shown in the attachment. > The app is meant to run non-interactively. > Is there a way to compile the app differently so error notifications get > simply printed out rather than being p