public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com> To: cygwin-xfree@cygwin.com Subject: Re: most recent xfig-3.2.5b-2 broken. Date: Mon, 27 Feb 2012 16:37:00 -0000 [thread overview] Message-ID: <4F4BB128.6010205@gmail.com> (raw) In-Reply-To: <4B30AD0BED19E842AAE88DC3973649314F6327B7B4@mail3.walsh.edu> On 2/27/2012 5:20 PM, George Barrick wrote: > Subj: most recent xfig-3.5.2b-2 broken. > > 2012.02.27.16:18:08 UT > >> >> I see no reason to re-install cygwin. It is purely a Avast problem >> > > Hi Marco, > > I went and re-installed my antivirus so that its > files would be stored in a better directory. That has > fixed my problem, as the av still slips .dll's into the > execution stack when I run cygwin processes, but now > my system knows where everything can be found. > > I tested the new octave. At first it crashed > when I asked for plots, but then I did the: > > rebaseall -v Hi George if you see fork problem on the *.oct dll's of octave please try "rebaseall -s 'dll|so|oct'" > from the ash-shell, and everything works. Both the > latest xfig and the new octave-3.6.1 work as they > should. Thank you for your patience. > > George you are welcome Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2012-02-27 16:37 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-25 20:07 George Barrick 2012-02-26 0:40 ` marco atzeri 2012-02-27 12:47 ` George Barrick 2012-02-27 13:14 ` marco atzeri 2012-02-27 14:36 ` George Barrick 2012-02-27 14:47 ` marco atzeri 2012-02-27 15:01 ` George Barrick 2012-02-27 15:05 ` marco atzeri 2012-02-27 16:21 ` George Barrick 2012-02-27 16:37 ` marco atzeri [this message] 2012-02-27 19:34 ` Yaakov (Cygwin/X) 2012-02-25 20:22 George Barrick
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=4F4BB128.6010205@gmail.com \ --to=marco.atzeri@gmail.com \ --cc=cygwin-xfree@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: linkBe 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).