15 thoughts on “>Cygwin / Emacs / Problems

  1. >I am experiencing the same problem but the page you linked to with the solution is down. Can you describe what the solution is?

  2. >Courtesy of the Internet Wayback Machine, here's that page: http://web.archive.org/web/20080414075615/http://pseudocode.cc/

    And here's the posted solution therein:

    Fixing emacs M-x shell or M-x compile for cygwin on Vista
    Filed under: Cygwin, Emacs, Technology — Frederick @ 4:07 pm

    If you try executing a command in emacs and receive an error similar to the following:

    > apply: Doing vfork: no error

    > apply: Doing vfork: resource temporarily unavailable [2 times]

    > “linked dll data write copy failed”

    Here is a workaround:

    1. Exit all cygwin based programs.

    2. Run c:\cygwin\bin\ash (may need to run as administrator)

    3. In ash, run /bin/rebaseall

    4. Run cygwin’s setup.exe

    5. Reinstall Libs/libncurses7

    Emacs should be capable of forking properly now.

  3. >Worked for me as well on Windows 7 64 bit. Ran into the problem, found this post immediately, and was past the issue in 5 minutes. Thanks!

  4. Worked for me too. Windows 7, 32 bit.

    Except that I reinstalled ALL modules found with the search string “libncurses”. Just to be sure (because some other webpage declared the method outdated).

    I didn’t try reinstalling only libncurses7.

  5. worked for me windows 7 extreme rtm eer1 32bit dell 14r laptop. it’s better, but the problem is still there.

    And ‘run’ means start menu->run not run from other cygwin shell

  6. Well, I tried this but deviated slightly: Since libncurses*7* was not already installed, I didn’t install. Instead, I just reinstalled the curses libraries that were installed.

    THIS DID NOT WORK.
    Libncurses7 is apparently magic here.

    Anyway, life is good now. Thanks for the help.

  7. Under Windows Vista x64, I had to make certain to hunt down and kill every Cygwin process, rebase all, and then reinstall every libncurses-related library. This worked for me.

    Thank you for the help.

  8. Followed the steps which worked like a charm for me on Windows Server 2008 R2 Enterprise 64-bit on March 14, 2012 except that I searched for ‘curses’ and reinstalled everything that was already installed containing the sub-string ‘curses’.

    Thank you very much for the help.

  9. It worked for me July 2013, I didn’t install ncurses7 but but just the ones that were installed (8 and 9 maybe?) and it worked fine.

  10. I managed to get this to work on windows 8.1
    However I did it once where it didn’t work. Then I rebooted and tried the approach again, this time using the dash (instead of ash) terminal, and it worked 🙂

    Both times I ran the terminal as administrator.
    /Jan

Leave a Reply

Your email address will not be published. Required fields are marked *