Erros de script postgg Cygwin (código de saída 254)

Question

Estou tentando instalar o cygwin, mas estou recebendo o seguinte erro de script de pós-instalação:

Package: _/base-files
    base-files-mketc.sh exit code 254
    base-files-profile.sh exit code 254

Não consigo encontrar informações úteis sobre isso por meio do Google. Eu encontrei algumas outras discussões de erro pós-instalação que recomendam excluir o Cygwin e limpar o registro, reinicializar e reinstalar, o que eu tentei sem sorte.

Alguém encontrou isto e, em caso afirmativo, como pode ser resolvido?

EDIT: Aqui está o log de instalação

    

Answer 1

Dois passos:

• desativar antivírus
• desativar o firewall

Se isso ajudar, ative o firewall e adicione todas as pastas do cygwin à lista de permissões do firewall.

Se não, leia este

How do I fix fork() failures?

Unfortunately, Windows does not use the fork/exec model of process creation found in UNIX-like OSes, so it is difficult for Cygwin to implement a reliable and correct fork(), which can lead to error messages such as:

• unable to remap somedll to same address as parent
• couldn't allocate heap
• died waiting for dll loading
• child -1 - died waiting for longjmp before initialization
• STATUS_ACCESS_VIOLATION
• resource temporarily unavailable

Potential solutions for the above errors:

• Restart whatever process is trying (and failing) to use fork(). Sometimes Windows sets up a process environment that is even more hostile to fork() than usual.
• Ensure that you have eliminated (not just disabled) all software on the BLODA.

• Switch from 32-bit Cygwin to 64-bit Cygwin, if your OS and CPU support that. With the bigger address space fork() is less likely to fail.

• Try setting the environment variable CYGWIN to "detect_bloda", which enables some extra debugging, which may indicate what other software is causing the problem.

  See this mail for more information.

• Force a full rebase: Run rebase-trigger fullrebase, exit all Cygwin programs and run Cygwin setup.

  By default, Cygwin's setup program automatically performs an incremental rebase of newly installed files. Forcing a full rebase causes the rebase map to be cleared before doing the rebase.

  See /usr/share/doc/rebase/README and /usr/share/doc/Cygwin/_autorebase.README for more details.

  Please note that installing new packages or updating existing ones undoes the effects of rebase and often causes fork() failures to reappear.

  See the process creation section of the User's Guide for the technical reasons it is so difficult to make fork() work reliably.

    

Answer 2

Já tentou usar outros espelhos?

O problema pode estar relacionado ao espelho. O código de erro pode estar relacionado à terminação ssh.

Fonte: Fóruns do PythonAnywhere