Re: [ANNOUNCEMENT] [1.7] Updated: file-5.00-1

Corinna Vinschen wrote: > I've updated the Cygwin 1.7 version of file to 5.00-1. Odd behavior: after I did a rebaseall, I was consistently seeing coredumps using this version of file. Reverting to the older version of file fixed it, as did re-installing the new version. I haven't rebased again,

Re: fstream - problem with reading/writing to file

On 2009-02-19 20:33Z, Tim McDaniel wrote: > On Thu, 19 Feb 2009, Pavel Kudrna wrote: >> I have found problem with read and write to file using fstream. The >> following example opens existing file for read+write, separately >> writes "Hello" and " world!" and in between it tries to read one >> cha

RE: Cannot convert string "-*-lucida-medium-r-*-*-*-*-*-*-*-*-iso8859-1"

FAQ 3.5: "The lucida font family is provided by the package font-bh-dpi75 (or font-bh-dpi100). The monospaced version, lucida typewriter is provided by the package font-bh-lucidatypewriter-dpi75 (or font-bh-lucidatypewriter-dpi100). " HTH, Mike > -Original Message- >

Re: Cannot convert string "-*-lucida-medium-r-*-*-*-*-*-*-*-*-iso8859-1"

Thanks for your reply. I see two folders /usr/share/fonts/75dpi, /usr/share/fonts/100dpi on my PC. But I do not know if they are the two needed font packages or not, and how to use them to fix my issue. Please give some details. Thanks. --- On Thu, 2/19/09, Yaakov (Cygwin/X) wrote: > From: Y

Re: fstream - problem with reading/writing to file

On Thu, 19 Feb 2009, Pavel Kudrna wrote: I have found problem with read and write to file using fstream. The following example opens existing file for read+write, separately writes "Hello" and " world!" and in between it tries to read one character from the file. The problem is that without call

Re: Cannot convert string "-*-lucida-medium-r-*-*-*-*-*-*-*-*-iso8859-1"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jeff Y wrote: > I can not launch Oracle Installer from AIX by warning: > > Warning: Cannot convert string "-*-lucida-medium-r-*-*-*-*-*-*-*-*-iso8859-1" > to type FontStruct > Exception in thread "main" > > Is there a fix for this? > > I check

fstream - problem with reading/writing to file

Hi, I have found problem with read and write to file using fstream. The following example opens existing file for read+write, separately writes "Hello" and " world!" and in between it tries to read one character from the file. The problem is that without call to seekg() or tellg() the read fai

Cannot convert string "-*-lucida-medium-r-*-*-*-*-*-*-*-*-iso8859-1"

I can not launch Oracle Installer from AIX by warning:   Warning: Cannot convert string "-*-lucida-medium-r-*-*-*-*-*-*-*-*-iso8859-1" to type FontStruct Exception in thread "main"   Is there a fix for this?   I check Cygwin FAQ. How can I know if packages font-bh-dpi75 and font-bh-lucidatypewrit

Re: Can't compile Screen: Undefined reference to __imp__ospeed

On 2/19/09, Andrew Schulman wrote: > > Note that for Emacs to recognize screen-256color, you need to add the > > following into "term/screen-256color.el" in the load path (for Emacs 22): > > > > (defun terminal-init-screen () > > "Terminal initialization function for screen." > > ;; Use th

Re: Can't compile Screen: Undefined reference to __imp__ospeed

> Note that for Emacs to recognize screen-256color, you need to add the > following into "term/screen-256color.el" in the load path (for Emacs 22): > > (defun terminal-init-screen () > "Terminal initialization function for screen." > ;; Use the xterm color initialization code. > (load "term/

Re: Can't compile Screen: Undefined reference to __imp__ospeed

Andrew Schulman-3 wrote: > >> screen-256color: GNU Screen compiled with the --enable-colors256 flag; >> without >> this flag, terminals launched from within Screen can only show 16 colors. >> Depending on your terminal, you may need to launch Screen as >> 'TERM=screen-256color screen' in order

Re: SSH/SCREEN/REATTACH bug

On Feb 19 09:15, Andrew Schulman wrote: > > Andrew, can you give us a bit more detail than just this micro snippet > > of information? > > > > What about providing details about the failing test done in screen's > > configure... > > > > What about extracting the code from configure and test it st

Lftp hang while executing batch file

Hi folks, I found that the Version 3.7.6-3 have the problem executing batchfiles. After upgrading from 3.7.6-1 my script does not longer work. I started lftp -f batchfile where in the batchfile the connection to the server And some action is done. It looks like that lftp hang while it tries to co

Re: [1.7] "broken" pipe implementation?

On Thu, Feb 19, 2009 at 09:16:50AM -0500, Andrew Schulman wrote: >I'm compiling screen for 1.7. The configure script has a test for a "usable" >pipe implementation, which passes, and another one for a "working" pipe >implementation, which fails. The test for a working pipe implementation is >zer

Re: Installation problem - "unix" root doesn't work

Hi Dave, Your last mail gave a hint to me. The fact that bash.exe exists in one place and doesn't exist in another place made me think about cygwin1.dll Actually, I looked for it on my disk and I found a tool which included in it an old version of cygwin1.dll. Apparently, the installation of this

[1.7] "broken" pipe implementation?

I'm compiling screen for 1.7. The configure script has a test for a "usable" pipe implementation, which passes, and another one for a "working" pipe implementation, which fails. The test for a working pipe implementation is zero exit code from the following program (simplified for clarity): ---

Re: SSH/SCREEN/REATTACH bug

> Andrew, can you give us a bit more detail than just this micro snippet > of information? > > What about providing details about the failing test done in screen's > configure... > > What about extracting the code from configure and test it standalone... > > What about maybe using strace and/or

RE: Installation problem - "unix" root doesn't work

Michel Wozniak wrote on Thursday, February 19, 2009 5:36 AM: > CygCheck -s -v -r gives me : "Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a st

Re: Installation problem - "unix" root doesn't work

Oh, and another thing occurred to me: Michel Wozniak wrote: > So, I cleaned all the entries you asked from the user and system PATH > env, and I relaunched an installation. > > The result is the same. Another question we should try and answer: > If you launch it manually, you get : > C:\

Re: Installation problem - "unix" root doesn't work

Michel Wozniak wrote: > The result is the same. > In the setup.log, all the postinstalls give : >2009/02/19 13:03:06 running: C:\cygwin\bin\bash.exe -c > /etc/postinstall/passwd-grp.sh >2009/02/19 13:03:06 abnormal exit: exit code=127 > > If you launch it manually, you get : > C:\cygfil

Re: Installation problem - "unix" root doesn't work

Hi Dave, Thanks for the answer. First, I tried to erase the former erroneous installation of Cygwin. I cleaned the registry. So, I cleaned all the entries you asked from the user and system PATH env, and I relaunched an installation. The result is the same. In the setup.log, all the postinstalls

Re: Installation problem - "unix" root doesn't work

Michel Wozniak wrote: > Path: > C:\SYNC\OUTILS\php > C:\SYNC\OUTILS\Unix like > Not Found: awk > Not Found: bash > Not Found: cat > Found: C:\SYNC\OUTILS\Unix like\cp.exe > Not Found: cpp (good!) > Not Found: crontab > Found: C:\SYNC\OUTILS\Unix like\find.exe > Not Found: gcc > Not Fou

Re: SSH/SCREEN/REATTACH bug

On Feb 18 09:26, Andrew Schulman wrote: > > sorry to inform you, using "Cygwin 1.7" yields the same result. > > OK, too bad. > > > Can't wait to see the recompile using pipes! > > I recompiled it yesterday in 1.7, and the configure script still found a > "broken" fifo implementation, but in a ge

Installation problem - "unix" root doesn't work

Hi, I couldn't find the answer to this question neither on the FAQ, nor on the lists... I make a standard clean install of CygWin (last setup.exe on the web site) on my Win2K computer (beforehand, I clean old cygwin folder, I clean the reg entries, and I clean all the links). I tried the install

Re: sshd w/o admin?

On Feb 19 10:50, Aaron Davies wrote: > I tried moving all my keys aside (outside of ~/.ssh). Now "ssh > localhost" on the local box takes my password, prints the banner, then > quits with "Connection to localhost closed." > > % ssh localhost > adav...@localhost's password: > Last login: Thu Feb 19