[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cygwin
Subject:    Re: Installation problems - post install scripts all give "abnormal exit: exit code=128"
From:       "Larry Hall (Cygwin)" <reply-to-list-only-lh () cygwin ! com>
Date:       2010-04-30 3:37:04
Message-ID: 4BDA5060.6040707 () cygwin ! com
[Download RAW message or body]

On 4/29/2010 11:22 PM, Crow, Frank wrote:
> Hi,
> 
> I recently installed the latest version of the full Cygwin.   I noticed that many \
> things were not working, so I looked at the /var/log/setup.log file.   In that log \
> file, I discovered that all of the package post install scripts failed during \
> installation.    All, except two, give the "abnormal exit: exit code=128" error, \
> such as: 
> 
> 2010/04/25 22:58:53 running: C:\cygwin\bin\bash.exe --norc --noprofile \
> /etc/postinstall/000-cygwin-post-install.sh 2010/04/25 22:59:26 abnormal exit: exit \
> code=128 2010/04/25 22:59:26 running: C:\cygwin\bin\bash.exe --norc --noprofile \
> /etc/postinstall/passwd-grp.sh 2010/04/25 22:59:53 abnormal exit: exit code=128
> 2010/04/25 22:59:53 running: C:\cygwin\bin\bash.exe --norc --noprofile \
> /etc/postinstall/coreutils.sh 2010/04/25 23:00:19 abnormal exit: exit code=128
> 2010/04/25 23:00:19 running: C:\cygwin\bin\bash.exe --norc --noprofile \
> /etc/postinstall/terminfo.sh 2010/04/25 23:00:47 abnormal exit: exit code=128
> 2010/04/25 23:00:47 running: C:\cygwin\bin\bash.exe --norc --noprofile \
> /etc/postinstall/bash.sh 2010/04/25 23:01:14 abnormal exit: exit code=128
> 
> I did some internet searches and have found a couple other people reporting this \
> problem.    Unfortunately, in every case, there has never been a resolution or fix \
> posted in reply. 
> I tried a bit of hacking: I went into the /etc/postinstall directory and ran
> all of the post install scripts manually.   While this did have some amount
> of success, it still did not result in a fully functional Cygwin
> installation.   As the scripts ran, many errors were reported.   Too many to
> list here.   But at least now I have the Cygwin and Cygwin-X start menus,
> which I did not have before.
> 
> 
> So my questions are:
> 
> 1. Does anyone know what "exit code=128" or "exit code=129" mean?   Or where
> to find out what those errors mean?
> 2. Does anyone know why all of the post install scripts fail in this manner
> for some installations such as mine?   Or how to better troubleshoot or fix
> the problem(s)?
> 
> Any information is highly appreciated.

Generally, this kind of failure stems from a few common problems:

   1. The existence of another (often old) cygwin1.dll.  Find it.  Remove it.
   2. http://cygwin.com/acronyms/#BLODA.  Remove BLODA.
   3. Possibly fork failures.  Install the rebase package and run
      rebaseall after reading the README in /usr/share/doc/Cygwin.

Also, make sure you're using the latest 'setup.exe' as found at cygwin.com.
Beware of proxies along your path that could be caching an old version.
You want version 2.697.

> Problem reports:       http://cygwin.com/problems.html

If it's none of the above, please provide cygcheck output as requested by
the link above.

-- 
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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic