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: Sun, 26 Feb 2012 00:40:00 -0000	[thread overview]
Message-ID: <4F497F79.6090500@gmail.com> (raw)
In-Reply-To: <4B30AD0BED19E842AAE88DC3973649314F600A1537@mail3.walsh.edu>

On 2/25/2012 9:06 PM, George Barrick wrote:
>
> Subj: most recent xfig-3.2.5b-2 broken.
>
>                                2012.02.25.19:18:18 UT
>
> Hey cygwin-x folks,
>
>        I just installed the xorg-server-1.11.4-5, and I
> thought that some aspect of its configuration may have
> broken the xfig program on my box.  This however was
> untrue.  When I reverted to xorg-server-1.11.4-1, the
> xfig crashed on startup as before, and I concluded
> that it must be a difficulty only with xfig.
>
>        I am running on a Dell Optiplex 380 with an Intel
> Core2 E7500 2.93 GHz CPU, 4.0 GBt DRAM and an 150 GBt
> Western Digital HD.  The OS is WinXp Pro. 32-bit, and
> is fully up-to-date.  My CygWin installation is 1.7.10-1,
> the xorg-server is 1.11.4-5, and everything in that
> sub-system is up-to-date.
>
>        The xfig is a minor part of the things I use,
> but I do like to have it around.  It fails to start,
> issuing the messages:
>
>> gbarrick@TS207 ~/figs/sqaccel
>> $ xfig sqposn.fig&
>> [1] 2904
>>
>> gbarrick@TS207 ~/figs/sqaccel
>> $ /usr/bin/xfig.exe: error while loading shared libraries:
>> ?: cannot open shared object file:
>>   No such file or directory
>
> I ran the cygcheck on the xfig package, but it claims
> that none of the required resources or libraries are
> missing.
>
>> $ cygcheck xfig
>> Found: D:\cygwin\bin\xfig.exe
>> Found: D:\cygwin\bin\xfig.exe
>> D:\cygwin\bin\xfig.exe
>>    D:\cygwin\bin\cyggcc_s-1.dll
>>      D:\cygwin\bin\cygwin1.dll
>>        C:\WINDOWS\system32\KERNEL32.dll
>>          C:\WINDOWS\system32\ntdll.dll
>>    D:\cygwin\bin\cygX11-6.dll
>>      D:\cygwin\bin\cygxcb-1.dll
>>        D:\cygwin\bin\cygXau-6.dll
>>        D:\cygwin\bin\cygXdmcp-6.dll
>>    D:\cygwin\bin\cygXaw3d-7.dll
>>      D:\cygwin\bin\cygXext-6.dll
>>      D:\cygwin\bin\cygXmu-6.dll
>>        D:\cygwin\bin\cygXt-6.dll
>>          D:\cygwin\bin\cygICE-6.dll
>>          D:\cygwin\bin\cygSM-6.dll
>>            D:\cygwin\bin\cyguuid-1.dll
>>    D:\cygwin\bin\cygXi-6.dll
>>    D:\cygwin\bin\cygXpm-4.dll
>>    D:\cygwin\bin\cygjpeg-7.dll
>>    D:\cygwin\bin\cygpng12.dll
>>      D:\cygwin\bin\cygz.dll
>
> I had reason to suspect that it was the
> xorg-server because new versions had recently
> been installed.  When I reverted to the previous
> xorg-server-1.11.4-1, everything was not O.K.
> The xfig still has the problem.
>
> George Barrick                 g_barrick_at_walsh_dot_edu
>

just installed xfig on latest  xorg-srver 1.11.4-5
and it works.

You have likely an old version of one of the several
dll's.

Dependency Walker can help to find the wrong dll
http://www.dependencywalker.com/

or you can use strace

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


  reply	other threads:[~2012-02-26  0:40 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 [this message]
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
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=4F497F79.6090500@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: 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).