RE: gcc4 and -mno-cygwin
Jerry DeLisle wrote: > You could try this: > > http://www.equation.com/servlet/equation.cmd?call=fortran Am I going blind, or is there no source available from there? Phil -- This email has been scanned by Ascribe Ltd using Microsoft Antigen for Exchange. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
setup for 1.7 fails with Japanese characters in download directory name
Hi all, First post, decided to file bug after installing testing Cygwin 1.7 on my Japanese WinXP on a Dell Core2Duo 64-bit x86-64 machine. The net installer failed to write to the download directory, by default the one in "My Documents" but written in Japanese characters. When I created a parallel directory "Downloads" I could run the net installer fine. Best regards, Gernot Hassenpflug -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
forget how to setup the 3-button emulating
Hi, I reinstalled my whole system, now when I launch up a X program and find my middle mouse button emulation does not work any more (by press in the same time both the left and right buttons). Who can remind me how to do it? Thanks. -- Life is the only flaw in an otherwise perfect nonexistence -- Schopenhauer narke public key at http://subkeys.pgp.net:11371 (narkewo...@gmail.com) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
mkpasswd, mkgroup: __progname points to rubbish
Hi, In last cygwin beta: $ uname -a CYGWIN_NT-5.2 VFPT-ITSECVMT 1.7.0(0.212/5/3) 2009-09-11 01:25 i686 Cygwin If I do (obviously found by mistake): $ mkpasswd -n 0 mkpasswd: unknown option -- n Try '̨ a --help' for more information. Note the rubish after "Try". Or, if I do: $ mkgroup -S-- <ª a: Only one character allowed as domain\user separator character. Rubbish. But when I do: $ mkgroup -n 0 mkgroup: unknown option -- n Try 'mkgroup --help' for more information. ...OK! The difference is in the 'default' clause of the select statement in the getopt output handling in main(). In mkgroup.c, argv[0] is used; in mkpasswd.c, it's __progname. Several other places with error conditions are using __progname, and the problem is identical. another example: $ mkpasswd -p idiot/path ̨ a: 'idiot/path' is not a fully qualified path. So, I currently don't know WHY __progname it's apparently non-initialized. If it is obvious for you, I'll stop right here. If you'd like that I dig more deeper, please say so! -- ___ Julio Costa -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: snapshot 20091002 and xterm crash
[Ping Yaakov] On Oct 2 09:04, Marco Atzeri wrote: > Hi, > > xterm abort when run in snapshot 20091002 > reverting to 20090924 solve the issue. > > Run as: > DISPLAY=127.0.0.1:0.0 xterm -ls /usr/bin/bash.exe I can reproduce that. I found the problem and it's really puzzeling. In the snapshot 2009-10-02, the default charset for the "C" locale is set to UTF-8 for the application. In 2009-09-24, it was only using UTF-8 for filenames and other system objects by default. When starting xterm with no locale environment variable set, it fails to start. If you're quick enough, you can read a message along the lines of "Cannot allocate pty: No such file ..." However, starting xterm works if you set, for instance, the environment variable $LANG to "C.UTF-8". This works: DISPLAY=127.0.0.1:0.0 LANG=C.UTF-8 xterm However, even though newlib handles "UTF8" same as "UTF-8", it's apparently not the same for xterm. This fails: DISPLAY=127.0.0.1:0.0 LANG=C.UTF8 xterm Yaakov, do you have a debug version of xterm handy? Would you mind trying to figure out why xterm is so sensitive in terms of the UTF-8 charset usage? What's especially weird is the fact that no native characters are used anywhere, only the ASCII range. Why xterm should fail, and why it's supposedly unable to open a pty with a "no such file or directory" message beats me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: snapshot 20091002 and xterm crash
2009/10/2 Corinna Vinschen: > > [Ping Yaakov] > > > On Oct 2 09:04, Marco Atzeri wrote: >> Hi, >> >> xterm abort when run in snapshot 20091002 >> reverting to 20090924 solve the issue. >> >> Run as: >> DISPLAY=127.0.0.1:0.0 xterm -ls /usr/bin/bash.exe > > I can reproduce that. I found the problem and it's really puzzeling. > > In the snapshot 2009-10-02, the default charset for the "C" locale is > set to UTF-8 for the application. In 2009-09-24, it was only using > UTF-8 for filenames and other system objects by default. > > When starting xterm with no locale environment variable set, it fails > to start. If you're quick enough, you can read a message along the > lines of "Cannot allocate pty: No such file ..." That could be a luit problem: http://www.mail-archive.com/cygwin-xf...@cygwin.com/msg19129.html > However, starting xterm works if you set, for instance, the environment > variable $LANG to "C.UTF-8". This works: > > DISPLAY=127.0.0.1:0.0 LANG=C.UTF-8 xterm > > However, even though newlib handles "UTF8" same as "UTF-8", it's > apparently not the same for xterm. Random guess: xterm recognises "UTF-8" in $LANG and concludes that no translation is needed. It doesn't recognise "UTF8" (without the hyphen), nor does it know that plain "C" now implies "UTF-8", hence it invokes "luit" to do the translation, which fails for the reason above. No idea why the luit problem didn't show up more prominently before though ... Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mkpasswd, mkgroup: __progname points to rubbish
On Oct 2 11:38, Julio Costa wrote: > Hi, > > In last cygwin beta: > > $ uname -a > CYGWIN_NT-5.2 VFPT-ITSECVMT 1.7.0(0.212/5/3) 2009-09-11 01:25 i686 Cygwin > > If I do (obviously found by mistake): > > $ mkpasswd -n 0 > mkpasswd: unknown option -- n > Try '̨ a --help' for more information. > > Note the rubish after "Try". I can reproduce this with mkpasswd from the latest test release. I can not reproduce it with the latest from CVS. So, whatever it was, it seems to be fixed in CVS. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: snapshot 20091002 and xterm crash
On Oct 2 12:12, Andy Koppe wrote: > 2009/10/2 Corinna Vinschen: > > > > [Ping Yaakov] > > > > > > On Oct 2 09:04, Marco Atzeri wrote: > >> Hi, > >> > >> xterm abort when run in snapshot 20091002 > >> reverting to 20090924 solve the issue. > >> > >> Run as: > >> DISPLAY=127.0.0.1:0.0 xterm -ls /usr/bin/bash.exe > > > > I can reproduce that. I found the problem and it's really puzzeling. > > > > In the snapshot 2009-10-02, the default charset for the "C" locale is > > set to UTF-8 for the application. In 2009-09-24, it was only using > > UTF-8 for filenames and other system objects by default. > > > > When starting xterm with no locale environment variable set, it fails > > to start. If you're quick enough, you can read a message along the > > lines of "Cannot allocate pty: No such file ..." > > That could be a luit problem: > > http://www.mail-archive.com/cygwin-xf...@cygwin.com/msg19129.html Uh, I see. Thanks for the pointer. > > However, starting xterm works if you set, for instance, the environment > > variable $LANG to "C.UTF-8". This works: > > > > DISPLAY=127.0.0.1:0.0 LANG=C.UTF-8 xterm > > > > However, even though newlib handles "UTF8" same as "UTF-8", it's > > apparently not the same for xterm. > > Random guess: xterm recognises "UTF-8" in $LANG and concludes that no > translation is needed. It doesn't recognise "UTF8" (without the > hyphen), nor does it know that plain "C" now implies "UTF-8", hence it > invokes "luit" to do the translation, which fails for the reason > above. > > No idea why the luit problem didn't show up more prominently before though ... Indeed. So it's not xterm, it's luit. That explains the weird strace output which shows that, for some reason, xterm tries to open /dev/ptyxx, which isn't available on Cygwin. I guess I can drop the ashen look from my face again. Not being able to use UTF-8 by default would have rendered a good amount of work of the last couple of days useless. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Assistance sought grepping log files
--- On Thu, 10/1/09, Ken Jackson wrote: > Try: > > strings -el logfile | grep ... Thanks - that works for me (as long as I remember that -el flag... -- Tcl - It's the real thing. http://wiki.tcl.tk/ http://www.purl.org/NET/lvirden/ http://www.xanga.com/lvirden/ Anything in this posting represents only my personal opinion. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: snapshot 20091002 and xterm crash
When starting xterm with no locale environment variable set, it fails to start. If you're quick enough, you can read a message along the lines of "Cannot allocate pty: No such file ..." Just a hint for debugging start problems with xterm: it has an option -hold in which case it doesn't terminate if the application terminates. Don't know, though, if this helps if there is an error during its own initialisation. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: forget how to setup the 3-button emulating
On 02/10/2009 11:29, Steven Woody wrote: I reinstalled my whole system, now when I launch up a X program and find my middle mouse button emulation does not work any more (by press in the same time both the left and right buttons). Who can remind me how to do it? Thanks. If only there was a manual [1] or some kind of online documentation (see 'man XWin'), so we didn't have to remember all these things :-) Please send X related questions should go to the cygwin-xfree list [2] [1] http://x.cygwin.com/docs/ug/configure-cygwin-x-options.html [2] http://cygwin.com/lists.html -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: forget how to setup the 3-button emulating
On Fri, Oct 2, 2009 at 8:39 PM, Jon TURNEY wrote: > On 02/10/2009 11:29, Steven Woody wrote: >> >> I reinstalled my whole system, now when I launch up a X program and >> find my middle mouse button emulation does not work any more (by press >> in the same time both the left and right buttons). Who can remind me >> how to do it? Thanks. > > If only there was a manual [1] or some kind of online documentation (see > 'man XWin'), so we didn't have to remember all these things :-) > > Please send X related questions should go to the cygwin-xfree list [2] > > [1] http://x.cygwin.com/docs/ug/configure-cygwin-x-options.html > [2] http://cygwin.com/lists.html > Okay, thanks for the info. -- Life is the only flaw in an otherwise perfect nonexistence -- Schopenhauer narke public key at http://subkeys.pgp.net:11371 (narkewo...@gmail.com) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
nttcp does not work
Hi: I am trying to use an utility called nttcp from the network series, in order to measure network throughput. Sadly, it always fails: $ nttcp server8 nttcp-l: connect: No such file or directory, errno=2 nttcp-l: Could not connecto to remote host : No such file or directory, errno=2 $ server8 resolves fine with ping and or nslookup, and nttcp -i is being run on server8 which is a linux box to receive the connection. Also, if ran from a linux machine to server8, it works just fine. Any hints? Thanks, -- Eduardo J. Ortega U. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: top - uknown terminal type
Works fine after running /etc/postinstall/terminfo0.sh. thanks Chuck/Christopher, jim > -Original Message- > From: Charles Wilson [mailto:cyg...@cwilson.fastmail.fm] > Sent: Thursday, October 01, 2009 6:54 PM > To: cygwin@cygwin.com > Subject: Re: top - uknown terminal type > > Egerton, Jim wrote: > > top gives me 'cygwin': unknown terminal type with a fresh > 1.7 install on server 2008. Any ideas what I am missing? > > Well, top uses: > > libncurses8 5.5-10 OK > which needs the "old-style" terminfo database in > > terminfo05.5_20061104-10 OK > which you have. I'd try to re-run >/etc/postinstall/terminfo0.sh.done > and try again. > > -- > Chuck > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mkpasswd, mkgroup: __progname points to rubbish
On Fri, Oct 02, 2009 at 01:19:55PM +0200, Corinna Vinschen wrote: >On Oct 2 11:38, Julio Costa wrote: >> In last cygwin beta: >> >> $ uname -a >> CYGWIN_NT-5.2 VFPT-ITSECVMT 1.7.0(0.212/5/3) 2009-09-11 01:25 i686 Cygwin >> >> If I do (obviously found by mistake): >> >> $ mkpasswd -n 0 >> mkpasswd: unknown option -- n >> Try '?? a --help' for more information. >> >> Note the rubish after "Try". > >I can reproduce this with mkpasswd from the latest test release. I can >not reproduce it with the latest from CVS. So, whatever it was, it >seems to be fixed in CVS. I can reproduce this and have checked in an obvious fix. It looks like I need to spend some time updating my binutils and gcc this weekend. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
cygwin bash and DOS cmd extremely sluggish.
For some reason my Cygwin bash is very sluggish. Whenever I type it takes awhile for it to respond. There is no load on the system and when I type in Word or another program it seems fine. I reinstalled Cygwin but this didn't seem to fix the problem. I then noticed that the DOS cmd window is also very sluggish. Any ideas why this is happening? My only clue is that this seemed to start happening after I switched the drive letters of my external hard drive from G:, H:, I: to E:, F:, G: respectively. I am running on a ThinkPad T60p w/ Symantec Anti-Virus, Sonic DLA, Google Desktop, etc. Any help would be appreciated, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mkpasswd, mkgroup: __progname points to rubbish
On Oct 2 09:50, Christopher Faylor wrote: > On Fri, Oct 02, 2009 at 01:19:55PM +0200, Corinna Vinschen wrote: > >On Oct 2 11:38, Julio Costa wrote: > >> In last cygwin beta: > >> > >> $ uname -a > >> CYGWIN_NT-5.2 VFPT-ITSECVMT 1.7.0(0.212/5/3) 2009-09-11 01:25 i686 Cygwin > >> > >> If I do (obviously found by mistake): > >> > >> $ mkpasswd -n 0 > >> mkpasswd: unknown option -- n > >> Try '?? a --help' for more information. > >> > >> Note the rubish after "Try". > > > >I can reproduce this with mkpasswd from the latest test release. I can > >not reproduce it with the latest from CVS. So, whatever it was, it > >seems to be fixed in CVS. > > I can reproduce this and have checked in an obvious fix. Strange enough, attributing the symbols as dllimport was not required before. OpenSSH, for instance, uses some of the exported data symbols as well without dllimport attribute and it works fine for a couple of years. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reinstallation problems
Because of problems mentioned previously I uninstalled cygwin following all the instructions at http://cygwin.com/faq/faq-nochunks.html#faq.setup.uninstall-all. However when I installed again and started up the bash shell I did not get my usual prompt, i.e. the typical Cygwin prompt. Instead I got this prompt: bash-3.2$ Also I was started in /usr/bin. No /home directory was created. No skeleton files were created. I thought Cygwin automatically does this the first time you start up. How come it didn't do it? What steps do I manually have to do? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] new: unison2.32; updated: unison2.27; removed: unison2.13, unison2.17, unison2.31
There are several updates to the Unison packages for Cygwin: * unison2.32 is a new package, now available in the archive. Upstream considers this version to be the current stable release of Unison. * unison2.27 has been updated. This is an upstream release with several bug fixes. Unison 2.27 is still in use in e.g. Debian stable and testing, so it will continue to be supported in Cygwin for some time. * unison2.13, unison2.17, and unison2.31 have all been removed from the Cygwin archive. The first two were obsoleted a few months ago, and no one has told me that they're still using them. The last was a short-lived beta release that's now considered obsolete. Unison is a file synchronizer for Unix and Windows. It allows two replicas of a collection of files and directories to be stored on different hosts (or on different disks on the same host), modified separately, and then brought up to date by propagating the changes in each replica to the other. == About Unison in Cygwin == Unison is packaged for Cygwin as several independent packages, each providing a version of Unison that is incompatible with the others. You have to run compatible versions of Unison on the client and server, or Unison will issue an error message and quit. Two versions of Unison are compatible if and only if the first two numbers in their version strings are the same. For example, all versions 2.32.* are mutually compatible, and incompatible with versions 2.27.*. By installing one or more of these packages side by side, you can use whichever one you need to synchronize with a particular host. Please read /usr/share/doc/unison*/README.Cygwin for more details. The unison* packages install a convenience symlink from /usr/bin/unison to one of the versioned unison executables, e.g. unison-2.27.exe. alternatives(8) is used to manage the symlink. If the symlink is being managed in "auto" mode, then it will automatically track the highest numbered version of unison that you have installed. You can override this by either changing the symlink manually with ln(1), or, preferably, by using alternatives(8): alternatives --display unison shows you the installed versions of unison, their priorities, which executable the symlink points to, and whether the symlink is being managed in "auto" or "manual" mode. alternatives --config unison presents a menu from which you can choose which version you want to use as the default. This puts the symlink in manual mode. alternatives --auto unison puts the symlink in automatic mode, where it will always point to the highest numbered version of unison that's installed on your host. alternatives --set unison /usr/bin/unison-$V.exe forces the symlink to point to unison-$V.exe, and puts it in manual mode. Please see alternatives(8) for more details. Andrew E. Schulman *** To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin bash and DOS cmd extremely sluggish.
* Frank Kim (Fri, 2 Oct 2009 07:11:00 -0700) > > For some reason my Cygwin bash is very sluggish. Whenever I type it > takes awhile for it to respond. There is no load on the system and > when I type in Word or another program it seems fine. > > I reinstalled Cygwin but this didn't seem to fix the problem. > > I then noticed that the DOS cmd window is also very sluggish. > > Any ideas why this is happening? My only clue is that this seemed to > start happening after I switched the drive letters of my external hard > drive from G:, H:, I: to E:, F:, G: respectively. > > I am running on a ThinkPad T60p w/ Symantec Anti-Virus, Sonic DLA, > Google Desktop, etc. http://cygwin.com/faq/faq.using.html#faq.using.bloda -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin bash and DOS cmd extremely sluggish.
Thanks for the pointer. However it seems strange that I'm having this problem now since I didn't have it before when I first installed Cygwin and I was using it for awhile. I only noticed the problem when I switched drive letters though I'm not sure if that's the reason. -- Thanks, Frank On Fri, Oct 2, 2009 at 9:01 AM, Thorsten Kampe wrote: > * Frank Kim (Fri, 2 Oct 2009 07:11:00 -0700) >> >> For some reason my Cygwin bash is very sluggish. Whenever I type it >> takes awhile for it to respond. There is no load on the system and >> when I type in Word or another program it seems fine. >> >> I reinstalled Cygwin but this didn't seem to fix the problem. >> >> I then noticed that the DOS cmd window is also very sluggish. >> >> Any ideas why this is happening? My only clue is that this seemed to >> start happening after I switched the drive letters of my external hard >> drive from G:, H:, I: to E:, F:, G: respectively. >> >> I am running on a ThinkPad T60p w/ Symantec Anti-Virus, Sonic DLA, >> Google Desktop, etc. > > http://cygwin.com/faq/faq.using.html#faq.using.bloda > > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ZIP64 support?
paul wrote: > What is the status of ZIP64 support in Info-ZIP? Will this be in 6.0? > > I received a ZIP64 file and had to use WinRAR to extract. Please direct questions regarding cygwin packages to the cygwin list, thx. Info-ZIP zip-3.0 (available for both cygwin-1.5 and cygwin-1.7) supports creating ZIP64 archives, AFAIK. Info-ZIP unzip-6.0 (available only for cygwin-1.7) supports unpacking (and listing) ZIP64 archives. For cygwin-1.5, only unzip-5.52 is available, which doesn't support ZIP64. You'll have to compile unzip-6.0 on that platform yourself (and I don't know how difficult that will be; there are a number of patches needed for clean builds on cygwin-1.7, so I assume building on cygwin-1.5 will require similar accommodation). I do not plan to release unzip-6.0 for cygwin-1.5. -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: reinstallation problems
On 10/02/2009 10:14 AM, Frank Kim wrote: Because of problems mentioned previously I uninstalled cygwin following all the instructions at http://cygwin.com/faq/faq-nochunks.html#faq.setup.uninstall-all. However when I installed again and started up the bash shell I did not get my usual prompt, i.e. the typical Cygwin prompt. Instead I got this prompt: bash-3.2$ Also I was started in /usr/bin. No /home directory was created. No skeleton files were created. I thought Cygwin automatically does this the first time you start up. How come it didn't do it? What steps do I manually have to do? (Fingers to temples, eyes closed) Quite please! I need absolute silence while I read your mind and determine your configuration. '/etc/passwd' is wrong, for one thing. Check 'setup.log.full' in '/var/log' or the directory you ran 'setup.exe' from (your mind is cloudy - I can't see this clearly). Your post-install scripts didn't run successfully. You can try to re-run them by hand but they will likely complain again until you determine the source of the problem, unless it was just a question of timing. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: setup for 1.7 fails with Japanese characters in download
My base os is Japanese OEM Windows XP. I've only used the standard c:\cygwin-packages directory, so have not had any problems. But, to confirm Gernot's report, I created a C:\japanese_dirname日本語名 directory and tried to download a package into it. It fails. setup reports the following type of message: No such file or directory: C:\japanese_dirname日本語名/http%3./release-2/..bzip_filename Although I think comments regarding "setup" may need to be sent to some setup mailing list?? Regards, Wynfield Gernot Hassenpflug wrote: > . > First post, decided to file bug after installing testing Cygwin 1.7 on > my Japanese WinXP on a Dell Core2Duo 64-bit x86-64 machine. > > The net installer failed to write to the download directory, by > default the one in "My Documents" but written in Japanese characters. > When I created a parallel directory "Downloads" I could run the net > installer fine. > > Best regards, > Gernot Hassenpflug -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygwin bash and DOS cmd extremely sluggish.
Frank Kim wrote: I then noticed that the DOS cmd window is also very sluggish. How could Cygwin be to blame for the DOS cmd window being sluggish? Cheers, Nicholas Sherlock -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
