RE: Incorrect module file format in Fortran netCDF package

2013-10-03 Thread Mark Hadfield
There's a second issue. In the output of "/usr/bin/nf-config --all" (below) a -no-undefined option is printed. This is not a valid option for gfortran. With these two issues fixed I can compile and link Fortran 90 programs that use the netCDF Fortran interface. -

Incorrect module file format in Fortran netCDF package

2013-10-03 Thread Mark Hadfield
The Cygwin package x86/libnetcdf-fortran-devel-4.2-2 includes two Fortran module files usr/include/NETCDF.mod usr/include/TYPESIZES.mod both dated 20 June 2012. According to the first line in each file (they are text files) the Gfortran format module version is '4'. The current Cygwin gcc-fort

Re: fixing BLODA-caused fork failures

2013-10-03 Thread Christopher Faylor
On Thu, Oct 03, 2013 at 04:55:19PM -0400, Adam Kellas wrote: >My company uses Cygwin and we experience fairly frequent fork >failures, believed to be BLODA-related. I say "believed to be" because >in this corporate environment, like many, we cannot uninstall the >virus scanner even long enough to s

Re: fixing BLODA-caused fork failures

2013-10-03 Thread Larry Hall (Cygwin)
On 10/3/2013 5:50 PM, Ryan Johnson wrote: On 03/10/2013 4:55 PM, Adam Kellas wrote: My company uses Cygwin and we experience fairly frequent fork failures, believed to be BLODA-related. I say "believed to be" because in this corporate environment, like many, we cannot uninstall the virus scanner

Re: fixing BLODA-caused fork failures

2013-10-03 Thread Ryan Johnson
On 03/10/2013 4:55 PM, Adam Kellas wrote: My company uses Cygwin and we experience fairly frequent fork failures, believed to be BLODA-related. I say "believed to be" because in this corporate environment, like many, we cannot uninstall the virus scanner even long enough to see what happens witho

fixing BLODA-caused fork failures

2013-10-03 Thread Adam Kellas
My company uses Cygwin and we experience fairly frequent fork failures, believed to be BLODA-related. I say "believed to be" because in this corporate environment, like many, we cannot uninstall the virus scanner even long enough to see what happens without it. The presumed culprit in our case is M

Re: VIM Vundle not working under Cygwin64

2013-10-03 Thread Gary Johnson
On 2013-10-03, Paul King wrote: > Hello > > I have tried to get vim's vundle package to work under Cygwin64, and > it appears as though vim doesn't understand most of the package. > Vundle works under 32-bit Cygwin, but something in the way the 64-bit > version was compiled looks in the wrong plac

Re: fonts for X11 and TexLive

2013-10-03 Thread Larry Hall (Cygwin)
On 10/3/2013 12:24 PM, wynfi...@gmail.com wrote: Is there some X11 or other utiltiy that can display a list of available fonts to 1.) X11 and if different fonta available and 2.) TexLive's Context macro processor? Why not ask this on the much more appropriate cygwin-xfree list? -- Larry ___

fonts for X11 and TexLive

2013-10-03 Thread wynfield
Is there some X11 or other utiltiy that can display a list of available fonts to 1.) X11 and if different fonta available and 2.) TexLive's Context macro processor? Thanks -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Ghostscript 9.10 with Cygwin 1.7.25 on the directory mounted as text

2013-10-03 Thread Smith
Hi. Almost data which are used with Ghostscript are text file, but Ghostscript is capable to handle binary files, for instance, image files like JPEG and/or PNG. In the case of Cygwin, if these files are read from the directory mounted as text, binary representation of these files are not prese

VIM Vundle not working under Cygwin64

2013-10-03 Thread Paul King
Hello I have tried to get vim's vundle package to work under Cygwin64, and it appears as though vim doesn't understand most of the package. Vundle works under 32-bit Cygwin, but something in the way the 64-bit version was compiled looks in the wrong place for vimrc. The 64-bit version (sorry I fo