bash script error

Hi, I am trying to run a script in cygwin,and keep getting this error.Both of these files exist (bash.exe) and user has 777 permissions. $ bin/run.sh : /bin/bash: /usr/local/x-daemon.sh: No such file or directory Any help appreciated. Brian -- Problem reports: http://cygwin.com/probl

Re: Please support CP932. (I have problem using subversion with SJIS)

Pardon me. I forgot to attach my patch. 2010/1/23 Nayuta Taga : > Please support CP932.  Because CP932 is not equal to SJIS, I have > problem using subversion when LANG=ja_JP.SJIS .  With the attached > patch and LANG=ja_JP.CP932, I can use subversion as expected. Index: newlib/libc/locale/locale

Please support CP932. (I have problem using subversion with SJIS)

Hi all, Please support CP932. Because CP932 is not equal to SJIS, I have problem using subversion when LANG=ja_JP.SJIS . With the attached patch and LANG=ja_JP.CP932, I can use subversion as expected. The problem is as follows: I have the following line in my ~/.subversion/config: glob

Re: missing setup command line arguments in the FAQ.

On Fri, Jan 22, 2010 at 03:07:10PM -0800, Brolin Empey wrote: >[deleted] Please. There was little in this message that was on-topic for the cygwin mailing list. Please use the cygwin-talk mailing list if you really want to pursue this further. -- Problem reports: http://cygwin.com/problem

Re: Why require ps -W and kill -f

On 1/22/2010 4:15 PM, Don Beusee wrote: I am a unix user that has moved to windows. I want unix commands on windows that function like their unix counterparts. That is supposed to be one of cygwin's missions, is it not? Sorry, but you're not exactly on the side of the angels when you argue t

Problem with Installation: No option to select DOS lines endings, defaults to UNIX.

I am having a problem with an installation of Cygwin. When I run setup.exe, I do not get an option for choosing line endings. So, I want to select DOS ine endings but that option is never available during setup, so it ends up being UNIX line endings. How do I force that option during installation?

X11 + remote desktop + clipboard = hang

Hi all, I noticed today that trying to cut and paste between an xterm and a remote desktop session causes the remote desktop to hang with a CPU pegged. I have vague memories of this sort of thing happening before (but with a VNC client causing the problem instead of rdtsc.exe). The fix then w

Re: Design issue with new MS-DOS style path warning?

Tried "bash", "-x", "bash build.sh", "bash -x build.sh", forward slashes in Windows environment variables, to no avail. But thank you for your time and patience, Dave! -e On Fri, Jan 22, 2010 at 7:25 PM, Dave Korn wrote: > On 22/01/2010 17:55, Eric Vautier wrote: >> Yes, it's a slightly complicat

Re: Design issue with new MS-DOS style path warning?

Just to clear things up, none of the paths are hard-coded. They are all obtained from environment variables or paths relative to project root. Only in the output from ant do they "look" absolute (the build has to figure out an absolute path sooner or later...). Again, the build script works perfec

Re: Why require ps -W and kill -f

On 22/01/2010 21:28, Don Beusee wrote: > People don't care about implementation details. They care about what is > running on the system (the WHOLE system). You are speaking for yourself. Not "everyone in the world". Try not to forget that. cheers, DaveK -- Problem reports:

RE: Why require ps -W and kill -f

I am a unix user that has moved to windows. I want unix commands on windows that function like their unix counterparts. That is supposed to be one of cygwin's missions, is it not? Isn't that one of the main reasons people get cygwin? What's the point of providing these commands otherwise? Why

Re: missing setup command line arguments in the FAQ.

I found this message in my hosted Gmail (Google Apps) account’s Spam folder. I wonder why Gmail thought it was spam? Because it contained the URL of a(n) (Windows) executable file? Dave Korn wrote: G.W. Haywood wrote: BTW, if you run "setup.exe --help", it will (depending on OS version) ei

Re: Why require ps -W and kill -f

On Fri, Jan 22, 2010 at 01:28:05PM -0800, Don Beusee wrote: >People don't care about implementation details. They care about what >is running on the system (the WHOLE system). They want kill and ps to >show what's running on the system, not what cygwin "thinks" is running. >Since exec() creates a

Re: Why require ps -W and kill -f

Larry Hall (Cygwin) wrote: > adding a system-wide flag to the CYGWIN environment variable is a > 10 ton sledge hammer for the pin you're trying to drive home. Yep. Especially as adding this: alias ps='ps -W' to ~/.bashrc will DTRT. -- Chuck -- Problem reports: http://cygwin.com/probl

RE: Why require ps -W and kill -f

--- Ven 22/1/10, Don Beusee ha scritto: > People don't care about > implementation details.  They care about what is > running on the system (the WHOLE system).  They want > kill and ps to show what's running on the system, not what > cygwin "thinks" is running.  then you are in the wrong place

Re: Why require ps -W and kill -f

On 01/22/2010 04:28 PM, Don Beusee wrote: People don't care about implementation details. They care about what is running on the system (the WHOLE system). They want kill and ps to show what's running on the system, not what cygwin "thinks" is running. Since exec() creates a new process on win

Re: Design issue with new MS-DOS style path warning?

On 1/22/2010 10:23 AM, Eric Vautier wrote: AndroidApp BUILD FAILED C:\dev\prj\app4\AndroidApp\build.xml:343: Warning: Could not find file C:\cygdrive\c\dev\prj\app4\Common\target\Common.jar to copy. My first thought when I see things like this isn't "oh, bad id

Re: 1.7: Problem with Novell volumes

On Jan 22 07:53, Sean Stidman wrote: > Hello, > >I recently upgraded to Cygwin 1.7. Since the upgrade, I started >having issues with accessing Novell volumes. Should be fixed in CVS. Try the latest developer snapshot at http://cygwin.com/snapshots/ Corinna -- Corinna Vinschen

R: Missing xdvi

--- Ven 22/1/10, Xianwen Chen ha scritto: > Hello friends, > > I've installed all tetex-* packages, howver, I can't find > xdvi. Should I compile it from source myself? > > Thank you in advance for any hint! > > Wen /usr/X11R6/bin/xdvi /usr/X11R6/bin/ is likely not anymore in the PATH Marco

[ANNOUNCEMENT] Updated: subversion-1.6.9-1

A new subversion package is available for the new upstream 1.6.9 release. (Versions 1.6.7 and 1.6.8 were never publicly released.) CYGWIN NEWS: There was one test failure. * All tests hang using the serf HTTP library. This package still includes support for serf, but if you encoun

Re: Missing xdvi

On 2010-01-22, Xianwen Chen wrote: > Hello friends, > > I've installed all tetex-* packages, howver, I can't find xdvi. > Should I compile it from source myself? > > Thank you in advance for any hint! Searching the Cygwin Package List (http://cygwin.com/packages/) for "xdvi" results in a number

Re: Missing xdvi

On 01/22/2010 04:22 PM, Xianwen Chen wrote: Hello friends, I've installed all tetex-* packages, howver, I can't find xdvi. Should I compile it from source myself? Thank you in advance for any hint! Cygwin X questions are best asked on the Cygwin X list. However:

RE: Why require ps -W and kill -f

People don't care about implementation details. They care about what is running on the system (the WHOLE system). They want kill and ps to show what's running on the system, not what cygwin "thinks" is running. Since exec() creates a new process on windows, that's more relevant for these tool

[1.7] Very odd reverse proxy problem . [nginx -> win32 zope]

The things: * I have a nginx handmade compiled under the hood * I have an official zope+plone installation on native windows * I have a django based application inside the cygwin * I have a tomcat+cas installation on native windows All of that seem to be configured correctly. What i want to do is

Missing xdvi

Hello friends, I've installed all tetex-* packages, howver, I can't find xdvi. Should I compile it from source myself? Thank you in advance for any hint! Wen -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows server 2008

On 22/01/2010 19:10, Cooper, Karl (US SSA) wrote: >> jenniferlee@ wrote: >>> administra...@nc042046 ~ $ cmd.exe /c 'mkdir C:\WINDOWS\temp' -bash: >>> /cygdrive/c/Windows/system32/cmd.exe: Bad address >>> > I get the same result you do when I use "/c" (lower case c), but the > command is proc

Re: help with error?

On 22/01/2010 01:57, Afflictedd2 wrote: > Hi everyone, > > I am having the following errors when compiling with cygwin. Didn't like the answer you got first time, when you were compiling it on your mac, eh? http://cboard.cprogramming.com/cplusplus-programming/123331-help-error.html When you

RE: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows server 2008

> Hi - I found that this error occurs on a 32 bit windows system, so > its not 64 bit related as I initially thought. The problem is only > occurring in Cygwin 1.7.1, not 1.5.24 so I will use the older version > of cygwin until there is a fix for this. > > Thanks > > jennifer...@nc.rr.com

Bash process substitution

Is process substitution expected to work in 1.7.1? Here's what I tried: kilr...@minime ~ $ uname -a CYGWIN_NT-5.1 MINIME 1.7.1(0.218/5/3) 2009-12-07 11:48 i686 Cygwin kilr...@minime ~ $ echo LOG:bananas | tee file.txt LOG:bananas kilr...@minime ~ $ cat file.txt LOG:bananas kilr...@minime ~ $ e

Re: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows server 2008

Hi - I found that this error occurs on a 32 bit windows system, so its not 64 bit related as I initially thought. The problem is only occurring in Cygwin 1.7.1, not 1.5.24 so I will use the older version of cygwin until there is a fix for this. Thanks jennifer...@nc.rr.com wrote: > Hi -

Re: 1.7.1 "Bad Address" when running cmd.exe on 64 bit windows server 2008

Hi - I found that this error occurs on a 32 bit windows system, so its not 64 bit related as I initially thought. The problem is only occurring in Cygwin 1.7.1, not 1.5.24 so I will use the older version of cygwin until there is a fix for this. Thanks jennifer...@nc.rr.com wrote: > Hi -

Re: Design issue with new MS-DOS style path warning?

On 22/01/2010 17:55, Eric Vautier wrote: >> So, you are lumbered with some massive mish-mash of complex build scripts, >> ANT, java, mixture of cygwin and native executables and god knows what else, >> and somewhere down in the middle of it something's invoking what it probably >> expects to be a

Re: Design issue with new MS-DOS style path warning?

>  So, you are lumbered with some massive mish-mash of complex build scripts, > ANT, java, mixture of cygwin and native executables and god knows what else, > and somewhere down in the middle of it something's invoking what it probably > expects to be a win32 program and getting the cygwin version,

Re: 1.7.1 gcc doesn't produce an output file

I ran cygcheck and saw that there was a stray Cygwin DLL file in my path. It was installed as part of Mentor Graphics Expedition. After removing the Expedition directory from my $PATH, the problem was resolved. Thanks, Tony -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: units: update, FHS compliance

On 01/22/2010 10:40 AM, Christopher Faylor wrote: On Fri, Jan 22, 2010 at 10:19:10AM +0100, Corinna Vinschen wrote: On Jan 21 12:40, Yaakov S wrote: On 21/01/2010 05:11, Corinna Vinschen wrote: Interesting. Especially the part about cmake. Did you try to convince Bill that WIN32 is not a goo

Re: Design issue with new MS-DOS style path warning?

On 22/01/2010 17:23, Eric Vautier wrote: > FYI, the "faulty but perfectly logical" path in one of the two > failures (I'll try to trace the other one as well) was arrived at > from: > > > 0. Invocation from sh build.sh (mid-script): > > ant clean get-common debug > > 1. Output of build s

Re: Design issue with new MS-DOS style path warning?

On Fri, Jan 22, 2010 at 6:01 PM, Dave Korn wrote: > On 22/01/2010 16:23, Eric Vautier wrote: > >> Let me confirm that the script has not changed at all, and used to >> work fine under the previous version. You'll agree that arriving at a >> C:/cygdrive/c/... path is a little odd, regardless of set

Re: 1.7.1 gcc doesn't produce an output file

On 22/01/2010 17:05, Tony Nelson wrote: > I CAN, however, compile the same program if I copy it over to /usr/bin. Where was it in the first place? Please run "cygcheck /usr/lib/gcc/i686-pc-cygwin/3.4.4/cc1.exe" from within both there and the original directory. And tell us what your $PATH is

1.7.1 gcc doesn't produce an output file

I've been using Cygwin and gcc for years with no problems. Recently I had to rebuild my Windows machine, and I installed the previous version of Cygwin (1.5.?). After a few days, I noticed 1.7 was out so I upgraded. Yesterday I tried using gcc for the first time. I'm now having a problem where

Re: futimes?

According to Charles Wilson on 1/22/2010 9:48 AM: > I noticed this change when reviewing libarchive development: > > "Windows resets atime at file close, so we can't use futimes() on > Cygwin." > http://code.google.com/p/libarchive/source/detail?r=1832 > > Is that the expected behavior? I thought

futimes?

I noticed this change when reviewing libarchive development: "Windows resets atime at file close, so we can't use futimes() on Cygwin." http://code.google.com/p/libarchive/source/detail?r=1832 Is that the expected behavior? I thought cygwin-(1.7?) took special care to go back and "fix up" this pr

Re: Best way to backup 1.5 to go to 1.7

If you have both 1.5 & 1.7, they can sorta co-exist. Leave your 1.5 system alone. Now crate & download 1.7 into a new node. (e.g./cygwinII). Just make sure everything is separate, include your update nodes and create a new "start" icon for 1.7 only. You might want to enforce separate execu

Re: Design issue with new MS-DOS style path warning?

On 22/01/2010 16:23, Eric Vautier wrote: > Let me confirm that the script has not changed at all, and used to > work fine under the previous version. You'll agree that arriving at a > C:/cygdrive/c/... path is a little odd, regardless of setup. Nope, it's actually entirely sensible! Because "

Re: Problem with svn and users over multiple machines

On 01/22/2010 04:21 AM, Gary . wrote: I don't know if this is a Cygwin related problem or if I am just being stupid. Probably the latter, but maybe in that case some kind soul will take pity on me. I added a new user "svn" and a new group "subversion-user", basically following http://www.cygwin.

Re: Design issue with new MS-DOS style path warning?

On Fri, Jan 22, 2010 at 4:45 PM, Christopher Faylor wrote: > On Fri, Jan 22, 2010 at 02:17:56PM +0100, Eric Vautier wrote: > If you are getting warnings then Cygwin is working as designed.  It is > telling you that you're doing something that is not guaranteed to work. > If you want to turn this o

Re: ls command crashed

On 01/22/2010 01:43 AM, Huang Bambo wrote: [ba...@bambo-pc /cygdrive/c/Sandbox/Bambo/DefaultBox] $ ls 6 [main] -bash 1104 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0xC10A, errno 11 $ cygcheck.exe -s We ask that you *attach* rather than a

R: Insall libsdl1.2 and libsdl1.2-dev packages

--- Ven 22/1/10, ghada zaibi ha scritto: > Hi, > I installed cygwin 1.5, but when when I used it to  > install another programm, I've got this error: > $ ./bootstrap > configure.ac:562: warning: macro `AM_PATH_SDL' not found in > library > which means that I need to install these packages to my >

1.7: Problem with Novell volumes

Hello, I recently upgraded to Cygwin 1.7. Since the upgrade, I started having issues with accessing Novell volumes. These issues are possibly similar to those seen by Avi Shwartz in his other threads. I'm too dumb to figure out how I can reply to those other threads so my apologies for cr

Re: Design issue with new MS-DOS style path warning?

On Fri, Jan 22, 2010 at 02:17:56PM +0100, Eric Vautier wrote: >It may be good advice not to do it. > >However, there's the case of environment variables, or parameter files >containing Windows-style paths used in build.xml, for example. It >appears that those variables are not converted sometimes,

Re: units: update, FHS compliance

On Fri, Jan 22, 2010 at 10:19:10AM +0100, Corinna Vinschen wrote: >On Jan 21 12:40, Yaakov S wrote: >>On 21/01/2010 05:11, Corinna Vinschen wrote: >>>Interesting. Especially the part about cmake. Did you try to convince >>>Bill that WIN32 is not a good idea for the Cygwin distro package? >> >>Yes

Insall libsdl1.2 and libsdl1.2-dev packages

Hi, I installed cygwin 1.5, but when when I used it to install another programm, I've got this error: $ ./bootstrap configure.ac:562: warning: macro `AM_PATH_SDL' not found in library which means that I need to install these packages to my system: libsdl1.2 and libsdl1.2-dev , my problem is that

Re: Problems starting sshd as a service on cygwin 1.7.1

Yes I looked for the logs - the /var/logs/sshd.log file is 0 length. Is there another log somewhere ? I'll explore if this is something the Symantec Client Firewall is causing. imaging away / flick -- Problem reports: http://cygwin.com/problems.html FAQ: ht

Re: Cygwin and gtk+ compiling problems still

On 1/22/2010 5:28 AM, Richard Dickinson wrote: > Hi > I am still not able to compile gtk+ or gtkmm programs in cygwin on my Vista > machine & I would > appreciate some advice on how to do this. I have already posted recently > about this and I had a > reply but as yet no further help to my follow

RE: Design issue with new MS-DOS style path warning?

Batson, Chuck sent the following at Wednesday, January 20, 2010 8:11 PM >I am aware it is possible to disable the "MS-DOS style path detected" >warning with the 'nodosfilewarning' option. > >But this message raises the question of, "What is the Cygwin ideal?" >That is, how to avoid the warning in a

RE: help with error?

I got the code from the web so I'm not sure what the author might have truly meant, a fix was to change it to 0, but I'm not sure if the program works as it is meant. Nellis, Kenneth-2 wrote: > >> From: Afflictedd2 >> Sent: Thursday, January 21, 2010 20:57 >> To: cygwin@cygwin.com >> Subject:

Re: Why require ps -W and kill -f

Don Beusee wrote: ps -e on Unix displays “every process running on the system”. This command doesn't do that under cygwin. Why should it be necessary to supply -W to see all processes running on the system? This makes it incompatible with Linux/Unix, and such scripts that rely on -e doing this

RE: help with error?

> From: Afflictedd2 > Sent: Thursday, January 21, 2010 20:57 > To: cygwin@cygwin.com > Subject: help with error? > > > Hi everyone, > > I am having the following errors when compiling with cygwin. > It complains on this line of code: > > while ( context->holder != '' ) { > > /usr/bin/g++ -

Re: Design issue with new MS-DOS style path warning?

It may be good advice not to do it. However, there's the case of environment variables, or parameter files containing Windows-style paths used in build.xml, for example. It appears that those variables are not converted sometimes, resulting in failures. One of my build files refers to such a prop

RE: Differentiate workgroup system from domain member under Cygwin

> Corinna Vinschen wrote: >> On Jan 22 10:34, Christoph Herdeg wrote: >> >>> So question is more if there is any place on a windows system, a >>> file or a directory or an entry in a file that exists only if that >>> machine is a domain member? >>> >> >> There are certainly multiple methods to

Re: Differentiate workgroup system from domain member under Cygwin

Corinna Vinschen wrote: On Jan 22 10:34, Christoph Herdeg wrote: So question is more if there is any place on a windows system, a file or a directory or an entry in a file that exists only if that machine is a domain member? There are certainly multiple methods to fetch this informatio

Cygwin and gtk+ compiling problems still

Hi I am still not able to compile gtk+ or gtkmm programs in cygwin on my Vista machine & I would appreciate some advice on how to do this. I have already posted recently about this and I had a reply but as yet no further help to my follow up (http://cygwin.com/ml/cygwin/2010-01/msg00850.html). I

Re: Differentiate workgroup system from domain member under Cygwin

>>On Jan 22 10:34, Christoph Herdeg wrote: >> So question is more if there is any place on a windows system, a file or a >> directory or an entry in a file that exists only if that machine is a >> domain member? > >There are certainly multiple methods to fetch this information. One of >them is,

Re: Differentiate workgroup system from domain member under Cygwin

On Jan 22 10:34, Christoph Herdeg wrote: > So question is more if there is any place on a windows system, a file or a > directory or an entry in a file that exists only if that machine is a > domain member? There are certainly multiple methods to fetch this information. One of them is, for instan

Re: Differentiate workgroup system from domain member under Cygwin

>>On Jan 22 09:31, Christoph Herdeg wrote: >> Dear Colleagues, >> >> I need being able to differentiate a workgroup system from a domain member >> in a shellscript under Cygwin - does anybody have an approach for me? >Look for the mkpasswd uppercase options -C, -L, -D, -S. They allow >to gene

Re: 1.7.1-1 - forward slash UNC names to use 'noacl'

On Jan 21 11:25, na na wrote: > > Listing the contents of a directory on our file server (a Samba share) by t= > he following command: > > =A0=A0 $ ls -l > > or explicitly > > =A0=A0 $ ls -l ./ > > the output is > > =A0=A0 --+ 1 600 2009-09-09 11:12 README.txt > =A0=A0

Problem with svn and users over multiple machines

I don't know if this is a Cygwin related problem or if I am just being stupid. Probably the latter, but maybe in that case some kind soul will take pity on me. I added a new user "svn" and a new group "subversion-user", basically following http://www.cygwin.com/ml/cygwin/2005-07/msg00933.html with

Re: Differentiate workgroup system from domain member under Cygwin

On Jan 22 09:31, Christoph Herdeg wrote: > Dear Colleagues, > > I need being able to differentiate a workgroup system from a domain member > in a shellscript under Cygwin - does anybody have an approach for me? Look for the mkpasswd uppercase options -C, -L, -D, -S. They allow to generate userna

Re: units: update, FHS compliance

On Jan 21 12:40, Yaakov S wrote: > On 21/01/2010 05:11, Corinna Vinschen wrote: > >Interesting. Especially the part about cmake. Did you try to convince > >Bill that WIN32 is not a good idea for the Cygwin distro package? > > Yes, among other things: > > http://www.cmake.org/Bug/view.php?id=101

Re: flex package requires m4

On Jan 21 16:49, Jeff Jones wrote: > Christopher Faylor cygwin.com> writes: > > > > > On Sun, Aug 23, 2009 at 06:36:12PM -0700, Karl M wrote: > > >My point was that flex needs a dependency on m4 for setup so that m4 is > > >installed automatically. Unless, of course, there is some reason not >

Differentiate workgroup system from domain member under Cygwin

Dear Colleagues, I need being able to differentiate a workgroup system from a domain member in a shellscript under Cygwin - does anybody have an approach for me? Mit freundlichen Grüßen / with

Re: Best way to backup 1.5 to go to 1.7

2010/1/21 Brian Keener: > I want to upgrade to 1.7 but would like to get a backup of the full 1.5 > install before hand.  I know in the past just doing copies some files > didn't or couldn't get copied.  Also in the unix world seems as though > I recall tar and cpio have difference in terms of what