This is what I get on a fresh, default install of cygwin:
$ mpif77
---
The Open MPI wrapper compiler was unable to find the specific compiler
ifort.exe in your PATH.
Note that this compiler was either specified at configure time or in
one of several possible environment variables.
---
On 12/13/2011 12:18 PM, Brian Craft wrote:
On Tue, Dec 13, 2011 at 11:16 AM, Csaba Raduly wrote:
On Tue, Dec 13, 2011 at 7:45 PM, Brian Craft wrote:
And why don't I see cyg*.dll files, for example, in /usr/lib?
They are all hiding under /usr/bin :)
Ah! I see. So the install is working fi
On Tue, Dec 13, 2011 at 11:16 AM, Csaba Raduly wrote:
> On Tue, Dec 13, 2011 at 7:45 PM, Brian Craft wrote:
>
>> And why don't I see cyg*.dll files, for example, in /usr/lib?
>
> They are all hiding under /usr/bin :)
>
Ah! I see. So the install is working fine, I was just adding the wrong
direct
On Tue, Dec 13, 2011 at 7:45 PM, Brian Craft wrote:
> And why don't I see cyg*.dll files, for example, in /usr/lib?
They are all hiding under /usr/bin :)
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real number
On Sat, Dec 10, 2011 at 11:34 PM, Christopher Faylor wrote:
> The hanging problem should be fixed in recent snapshots.
I can confirm this in the 12/12 and 12/13 snapshots - thanks!
Cygwin-X is working fine again without any hangs.
--
Jim Reisert AD1C, , http://www.ad1c.us
--
Problem reports:
On Tue, Dec 13, 2011 at 10:24 AM, Ryan Johnson wrote:
> On 13/12/2011 1:16 PM, Brian Craft wrote:
>>
>> I'm building a few libraries which are dependencies of a program I'm
>> building. Most of them build via autotools. Doing "make install"
>> installs files *.a, *.la, *.dll.a. Linking the executab
On 13/12/2011 1:16 PM, Brian Craft wrote:
I'm building a few libraries which are dependencies of a program I'm
building. Most of them build via autotools. Doing "make install"
installs files *.a, *.la, *.dll.a. Linking the executable succeeds
without error, however when running it, the loader com
I'm building a few libraries which are dependencies of a program I'm
building. Most of them build via autotools. Doing "make install"
installs files *.a, *.la, *.dll.a. Linking the executable succeeds
without error, however when running it, the loader complains that it
can't find cyg*.dll files. E.
> Andrew,
> Sorry to bother you again but could I get another gold star for the gold
> star gatekeeper? His unflagging responsiveness is appreciated. It may
> be recursive but I think it's well deserved.
Hm... I resist awarding awards to myself... but your wish is my command.
http://cygwin.co
Andrew,
Sorry to bother you again but could I get another gold star for the gold
star gatekeeper? His unflagging responsiveness is appreciated. It may
be recursive but I think it's well deserved.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.
On Dec 12 23:07, Enrico Forestieri wrote:
> Corinna Vinschen writes:
> >
> > Would it be ok if it works the old way (WIN_A uses the Cygwin codeset)
> > for applications built under 1.7.9 and earlier, and the new way (WIN_A
> > uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and
>
On Dec 13 16:24, Jari Aalto wrote:
>
> ** To CC Emacs BTS, use 10257(at)debbugs.gnu.org
>
> My full original bug report was sent initially to Emacs, because the editor
> started considering remotes file as read-only and requiring confirmation
> after every save. See:
>
> http://debbugs.gnu.o
On 12/13/2011 8:41 AM, Stitchz wrote:
Is it possible to have a mpif90 command (mpi fortran 90 compiler) working
under cygwin? I've tried to download several packages (open mpi, mpich2,
...) but the configure scripts always fail.
OpenMPI list indicated recently that cygwin support is a work in
p
> On Mon, Dec 12, 2011 at 04:57:10PM -0500, Ken Brown wrote:
> >The attached patches address some of the documentation problems mentioned in
> >
> > http://cygwin.com/ml/cygwin/2011-12/msg00277.html .
> >
> >I think the other problems have already been fixed in CVS.
>
> Patch applied along with
** To CC Emacs BTS, use 10257(at)debbugs.gnu.org
My full original bug report was sent initially to Emacs, because the editor
started considering remotes file as read-only and requiring confirmation
after every save. See:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10257
It appears that Cyg
Is it possible to have a mpif90 command (mpi fortran 90 compiler) working
under cygwin? I've tried to download several packages (open mpi, mpich2,
...) but the configure scripts always fail.
Since a fresh install of cygwin includes the mpif77 command (even though it
just points to a missing ifort
On Dec 12 14:43, Charles Wilson wrote:
> On 12/9/2011 3:35 PM, Corinna Vinschen wrote:
> > I have a well-known problem. I just don't have all filesystems
> > available for testing. What I need are testers for a certain, very
> > simple functionality on any filesystem you can get hold of.
>
> I'v
On Dec 12 10:45, Ken Brown wrote:
> On 12/12/2011 1:31 AM, Mike Brown wrote:
> >On Sun, Dec 11, 2011 at 11:48:01PM -0600, Mike Brown wrote:
> >Suggestions for document improvement:
> >
> >FAQ addition to show how to modify the cygwin.bat file, or a copied file for
> >modification, in order to be ab
On 12/13/2011 5:36 AM, Christopher Faylor wrote:
On Mon, Jul 25, 2011 at 07:27:23PM +0200, Marco Atzeri wrote:
On 25/07/2011 19.05, Christopher Faylor wrote:
"sleeping and waiting for signal" would mean that "bash is not waiting
for input". If bash isn't waiting for input that would explain
19 matches
Mail list logo
