Re: Fortran Compiler Error CMBFAST
Yes I forgot to mention that the include file that the compiler could not find was in the working directory. Adding a -I./ to the flags has seemed to solve this. On 6/26/06, Williams, Gerald S (Jerry) <[EMAIL PROTECTED]> wrote: Brad Krane wrote: > I'm trying to compile the scientific package CMBFAST-4.5.1 in the > cygwin environment using g77. I get the following error... > > f77 -O2 -c -o jlgen.o jlgen.F > jlgen.F: In program `jlgen': > jlgen.F:14: > include 'cmbfast.inc' > ^ > Unable to open INCLUDE file `cmbfast.inc' at (^) Tim Prince wrote: > Normally, you would specify the path to search for include files with > -I, if it is not in the current working directory. I looked at the library, and the referenced include file *is* in the same directory. The library even includes a configure script, so this isn't simple pilot error--it looks like there is a bug in the compiler. For now, you can work around the problem by adding -I. to the command lines, or more likely to the end of FFLAGS in the Makefile (after running ./configure). I don't use FORTRAN enough to say whether the behavior we are seeing is correct, though from the evidence I've seen I'd say it isn't. gsw -- Brad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Fortran Compiler Error CMBFAST
I'm trying to compile the scientific package CMBFAST-4.5.1 in the cygwin environment using g77. I get the following error and I have no idea how to fix this having never used Fortran before. This should work without any problem as many other people have compiled this and never run up on a similar problem. I think that it is a compiler specific issue or an environment one. f77 -O2 -c -o jlgen.o jlgen.F jlgen.F: In program `jlgen': jlgen.F:14: include 'cmbfast.inc' ^ Unable to open INCLUDE file `cmbfast.inc' at (^) jlgen.F:18: integer l(lmax),i,j,lmo ^ Invalid declaration of or reference to symbol `lmax' at (^) [initially seen at (^)] jlgen.F:18: integer l(lmax),i,j,lmo 1 jlgen.F:21: (continued): common /lvalues1/ l,l0,lmo 2 Invalid declaration of or reference to symbol `l' at (2) [initially seen at (1)] Thanks, -- Brad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Increasing Available Memory for Cygwin Run Programs in XP Cygwin1.dll v1.5.19-cr-0x5ef
Sorry I forgot to mention my Cygwin version in my previous post. -- Brad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Increasing Available Memory for Cygwin Run Programs in XP
Look at "--large-address-aware" option in ld.info. Danny I have just tried this option by compiling with the line below: gcc -DMEMLOC -Wl,--large-address-aware memloc.c -o memloc and this has unfortunatly lead to no effect. -- Brad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Increasing Available Memory for Cygwin Run Programs in XP
I am trying to run a numerical simulation that requires a large amount of RAM in the cygwin environment running on a Pentium 4 with Windows XP and 3GB RAM. I have so far learned that Windows XP (and other Windows versions) allot only 2GB RAM for user program space. I have verified this with a small program I developed that allocates the maximum available memory to 4 bytes. In Windows when I run this program I am able to allocate a total of 1.94GB of memory, however, when I run the same code in Cygwin I am only able to allocate 1.12GB of memory. I am not the only person to have come across a similar problem in the past. I have been searching through the archives and so far have found 3 notable references from topics that can be found here: http://sourceware.org/ml/cygwin/2005-04/msg01309.html http://sources.redhat.com/ml/cygwin/2003-02/msg00234.html http://sourceware.org/ml/cygwin/2004-06/msg01248.html In the first topic it is said that using the -mno-cygwin flag in the compiler options will allow programs to gain access to more memory by having them by pass the cygwin1.dll. This however produces the undesirable side effect of an error compiling, as the program references sys/resource.h and I can only assume that this would require the use of cygwin1.dll. I don't suppose there is much of a way around this? The second idea I found was to set the registry item "/HKEY_CURRENT_USER/Software/Cygnus\ Solutions/Cygwin/heap_chunk_in_mb x" where 'x' is the amount in MB(obviously). I set this value to a safe amount of 195MB or 1.90GB. Unfortunately this does nothing and I am left with the exact same amount of memory. Finally there was the idea to run XP with the /3gb option set in the boot.ini to increase the user program space from 2GB to 3GB. The problem is that after a reboot I am still only able to allocate 1.94GB of RAM with a Windows XP binary and 1.12GB through Cygwin. Could this be a side-effect of having only 3GM or physical memory or would the page file accommodate this(as I think)? I've noticed that the messages are at least one year old. Has anything significant that would affect these "fixes" have changed since then? Does anyone have any fresh ideas or work around aside from a new OS? ;) On a further note I have noticed that in the Advanced Properties of the Cygwin shortcut that is set to run in a separate memory space by default and I am unable to change this even when making a shortcut directly to bash.exe itself. Could this be affecting the available memory and if so is there anyway to modify this property? Thank you for your time and effort. -- Brad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
