This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problems installing on vista, no /bin in path


I've been seeing the same problem with both bash behaving in this
manner (presummably because of the simple non-existence of
/etc/profile) and cases where bash segfaults immediately on startup.
Both problems, while not confirmed to have the same root cause, have
the same errors in postinstall as seen below.

None the the identified BLODA options seem to apply in my case as 
these are relatively new/clean installs.  The prime suspect would have
been Windows Defender but on my boxes (Windows 2008 Server) it does
not seem to be installed (nothing under "Programs and Features" or
under "Programs" in the StartMenu).  Let me know if there's something
else going on here and Windows Defender might still be on my system.

I tried to find out why the postinstalls failed but my current situation
is that bash is in the "segfault mode" and thus the scripts fundamentally
cannot run.  I'll look for other ways of identifying why bash is segfaulting
but any recommendations would be welcome.  Otherwise I'll keep plugging
away and let you know if I find anything new.

-- Eric

----- Original Message ----
From: Brian Dessent <>
To: Steinar Bang <>
Sent: Monday, May 26, 2008 5:26:24 AM
Subject: Re: Problems installing on vista, no /bin in path

Steinar Bang wrote:

> 2008/05/23 13:26:24 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/
> 2008/05/23 13:26:33 abnormal exit: exit code=35584
> 2008/05/23 13:26:33 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/
> 2008/05/23 13:26:38 abnormal exit: exit code=35584
> 2008/05/23 13:26:38 running: C:\cygwin\bin\bash.exe -c /etc/postinstall/
> 2008/05/23 13:26:43 abnormal exit: exit code=35584
> ...

You need to find out why these fail.  Probably BLODA.

> What I did was
>  1. start cmd.exe
>  2. type c:\cygwin\bin\bash at the cmd prompt
>  3. I get a
>       bash-32$
>     prompt, and no cygwin utilities found (ie. the same behaviour as
>     when starting the cygwin shortcut)

That is not a valid test, because just running bash with no options does
not start a login session, and therefore the /etc/profile will not be
sourced, and it is there that /usr/bin is added to PATH.  So it's
expected behavior that if you do the above, no commands (except for bash
builtins) will work because they are not in the PATH.  If you look at
the cygwin.bat file, you'll see that bash needs to be started with the
--login (or -l) option for a proper environment.

But that aside, it won't work anyway even if you start a login shell,
since /etc/profile is only installed from /etc/defaults/etc/profile by
the postinstall script of the 'base-files'
package.  Since your postinstall scripts are failing, you need to find
out what's wrong there before anything will work.  You won't have a
working system until postinstall scripts are run correctly.


Unsubscribe info:
Problem reports:


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]