public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ronald Fischer" <ynnor@mm.st>
To: "Ryan Johnson" <ryan.johnson@cs.utoronto.ca>, cygwin@cygwin.com
Subject: SOLVED (was: Re: fixing fork failures (was: Re: Best way to repair cygwin?))
Date: Fri, 26 Aug 2011 14:03:00 -0000	[thread overview]
Message-ID: <1314367396.12096.140258134029425@webmail.messagingengine.com> (raw)
In-Reply-To: <4E57A03D.9050207@cs.utoronto.ca>

> > This is typically the result of one of two things:
> >
> >   1. <http://cygwin.com/acronyms/#BLODA>
> >
> >   2. DLL collisions - Install the 'rebase' package, read its README in
> >      /usr/share/doc/Cygwin, and follow the instructions there to run
> >      'rebaseall'.

Thanks a lot!

In my case it turned out to be a BLODA....

I will however install rebase too, in case I need it one day.



Ronald
-- 
Ronald Fischer <ronaldf@eml.cc>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)


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

  reply	other threads:[~2011-08-26 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 13:22 Best way to repair cygwin? Ronald Fischer
2011-08-26 13:31 ` fixing fork failures (was: Re: Best way to repair cygwin?) Ryan Johnson
2011-08-26 14:03   ` Ronald Fischer [this message]
2011-08-26 16:21 ` Best way to repair cygwin? LMH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1314367396.12096.140258134029425@webmail.messagingengine.com \
    --to=ynnor@mm.st \
    --cc=cygwin@cygwin.com \
    --cc=ryan.johnson@cs.utoronto.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).