From: Markus Hoenicka <markus.hoenicka@mhoenicka.de>
To: cygwin@cygwin.com
Subject: Re: troubles with forking program (not the usual probs though...)
Date: Wed, 16 Nov 2011 07:59:00 -0000 [thread overview]
Message-ID: <20111116085916.Horde.oe3MALuWis5Ow21UoD8BO5A@webmail.df.eu> (raw)
In-Reply-To: <20111115193830.Horde.LGKYH0lCcOxOwrGmoiHw0iA@webmail.df.eu>
Markus Hoenicka <markus.hoenicka@mhoenicka.de> was heard to complain:
> Hi all,
>
> I've managed to screw up a forking program (refdbd, from
> http://refdb.sourceforge.net) in an attempt to install R which I
> need at work. This does not look like the widely reported fork
> failures as I do not get any diagnostic output - things just don't
> work as expected anymore. setup ran uneventfully, except that it
> failed to upgrade libatk the first time as it was probably in use,
> so I ran setup a second time after closing all programs. I've
> appended the log of both runs just in case.
>
[...]
After a few hours of sleep I Looked at the update log again. Only
binutils (containing the linker) and mysql-related packages (refdbd
was set up to use the MySQL client library) were likely to affect
refdbd. Downgrading binutils didn't help. Downgrading the
MySQL-related packages was not possible as there are no previous
versions available in setup. However, switching to a different
database engine (sqlite3) made refdbd return to normal. Therefore I
suspect that refdbd was screwed up by upgrading the MySQL client
library. I'll follow up on this on the Cygwin Ports list.
regards,
Markus
--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38
--
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 parent reply other threads:[~2011-11-16 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 18:39 Markus Hoenicka
2011-11-16 7:59 ` Markus Hoenicka [this message]
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=20111116085916.Horde.oe3MALuWis5Ow21UoD8BO5A@webmail.df.eu \
--to=markus.hoenicka@mhoenicka.de \
--cc=cygwin@cygwin.com \
/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).