Re: Problem with automake

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Public Mailing Lists on 5/27/2007 8:30 PM: > /usr/bin/m4:configure.in:1363: cannot create temporary file for > diversion: Permission denied > /usr/bin/m4: cannot remove temporary directory /tmp/m4-KJkmd5: Directory > not empty > autom4te-2

Problem with automake

I'm trying to compile some older linux program with automake under Cygwin. (My Cygwin installation is on the latest version.) I'm getting the following error message: $ ./autogen.sh calling autoconf and autoheader... /home/test/project /usr/bin/m4:configure.in:1363: cannot create temporary file

rsync problems with snapshots

I want to flag that with the Cygwin snapshots (those of 1.7 version) there is this problem using rsync: - $ rsync -av --delete ftp.dante.de::CTAN/systems/win32/miktex /tmp receiving file list ... done rsync: read error: Socket opera

Re: pseudo pty terminal issue

On Sun, May 27, 2007 at 09:52:59AM -0700, RAM SUNEE wrote: >In the Cygwin environment, I was able to run a C language program that >successfully opened '/dev/ptmx'. But when tried the same using python, >I have the following error message. > >"OSError: [Error 2] No such File or directory: '/dev/pt

pseudo pty terminal issue

Hello, In the Cygwin environment, I was able to run a C language program that successfully opened '/dev/ptmx'. But when tried the same using python, I have the following error message. "OSError: [Error 2] No such File or directory: '/dev/ptmx'] Any ideas will be greatly appreciated. Thanks, Ram

Re: [patch] fix printf("%p") (lesstif / XPDF crash)

On Sun, May 27, 2007 at 08:15:23AM -0600, Eric Blake wrote: >According to Brian Dessent on 5/27/2007 7:01 AM: >> Currently sprintf("%p") does not work because the path taken for >> handling %p shares most of the code with %x but fails to populate the >> char ox[2] used to emit the prefix, resulting

Re: Problems with XPDF on Cygwin with recent snapshots (newlib ?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Brian Dessent on 5/27/2007 8:57 AM: > Brian Dessent wrote: > >> I can't possibly see how this would be due to the changes in newlib, but > > Sigh, I knew those sounded like famous last words when I typed them. > The actual error was unr

Re: Problems with XPDF on Cygwin with recent snapshots (newlib ?)

Brian Dessent wrote: > I can't possibly see how this would be due to the changes in newlib, but Sigh, I knew those sounded like famous last words when I typed them. The actual error was unrelated to this frame, it was occuring several frames up and was a cascading failure that originated with ne