public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: George Barrick <gbarrick@walsh.edu> To: "'cygwin-xfree@cygwin.com'" <cygwin-xfree@cygwin.com> Subject: Re: most recent xfig-3.2.5b-2 broken. Date: Mon, 27 Feb 2012 12:47:00 -0000 [thread overview] Message-ID: <4B30AD0BED19E842AAE88DC3973649314F6327B7B1@mail3.walsh.edu> (raw) In-Reply-To: <4F497F79.6090500@gmail.com> Subj: most recent xfig-3.2.5b-2 broken. 2012.02.27.12:45:48 UT Hi Marco (and cygwin-x folks), I will try the experiment that I think you are suggesting. If the .so is part of an older .dll, then a reinstallation of the packages should clear up the problem. I have not yet done that however because the same difficulty is emerging with the octave-3.6 that was released over the weekend. The message that I get is: gbarrick@TS207 ~/jpegs/figs $ octave /usr/bin/octave-3.6.1.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory The cygcheck for octave indicates no particular problem: gbarrick@TS207 ~/jpegs/figs $ cygcheck octave Found: D:\cygwin\bin\octave Found: D:\cygwin\bin\octave -> D:\cygwin\bin\octave-3.6.1.exe D:\cygwin\bin\octave-3.6.1.exe D:\cygwin\bin\cygoctinterp-1.dll D:\cygwin\bin\cygoctave-1.dll D:\cygwin\bin\cygcruft-1.dll 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\cyggfortran-3.dll D:\cygwin\bin\cygstdc++-6.dll D:\cygwin\lib\lapack\cygblas-0.dll D:\cygwin\lib\lapack\cyglapack-0.dll D:\cygwin\bin\cygreadline7.dll D:\cygwin\bin\cygncursesw-10.dll C:\WINDOWS\system32\USER32.dll C:\WINDOWS\system32\GDI32.dll D:\cygwin\bin\cygfftw3-3.dll D:\cygwin\bin\cygfftw3f-3.dll D:\cygwin\bin\cygpcre-0.dll D:\cygwin\bin\cygqrupdate-0.dll D:\cygwin\bin\cygGL-1.dll D:\cygwin\bin\cygglapi-0.dll D:\cygwin\bin\cygX11-xcb-1.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\cygxcb-glx-0.dll D:\cygwin\bin\cygGLU-1.dll D:\cygwin\bin\cygz.dll D:\cygwin\bin\cygfontconfig-1.dll D:\cygwin\bin\cygexpat-1.dll D:\cygwin\bin\cygfreetype-6.dll D:\cygwin\bin\cygbz2-1.dll D:\cygwin\bin\cygiconv-2.dll D:\cygwin\bin\cyghdf5-7.dll I also examined the file /var/log/setup.log.full, but saw only messages that looked like successful installations of the many hundreds of files in the octave packages, plus a few messages from "io_stream:mklink" that seem to indicate successful creation of links. Is there anything that I might do to narrow down the .so or .dll that is causing the problem? It seems quite odd, because this is a new installation of cygwin (about three weeks old), and I do not think that it has had time to get mucked up with old .dll's and such. George g_barrick_at_walsh_dot_edu -- 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 12:47 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 [this message] 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=4B30AD0BED19E842AAE88DC3973649314F6327B7B1@mail3.walsh.edu \ --to=gbarrick@walsh.edu \ --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).