> Don't know Rich. Could we have some basics here just in case it > matters: > 1) How much real memory on the machine ( RAM ). 3 gigs > > 2) How much free disk space on the hard drive 254 gigs > > 3) Does a check with Disk Utility on the hard drive show it is ok? > Are permissions ok? Yes, and it fails on two different Macs > > 4) Which OS X on this G5 Powermac? OS 10.5.2 One Mac is dual 2 ghz PowerMac G5 Other Mac is Intel Mac Mini dual core 1.6 ghz > > 5) How many lines of code in MacWise? ( approximately ) About 40,000 Robert had me set some special options in the FBtoC compiler and email the log to him. Rich On Mar 8, 2008, at 7:24 PM, Brian Stevens wrote: > > On Mar 8, 2008, at 9:27 AM, Rich Love wrote: > >> The compile attempt on my Mac Mini went for 54 minutes and then >> failed with the virtual memory exhausted error. >> Here is the FBtoC log. >> I could not find anything revealing in the console log. >> >> FBtoC: translating project MacWise.π to MacWise.c >> FBtoC: translation time: 12.94 s >> FBtoC: copying files >> FBtoC: copying resources >> ¿¿ Warning: 'plst' 0 ignored in file MacWise.RSRC >> FBtoC: found Info.plist >> FBtoC: copy time: 0.34 s >> FBtoC: compiling MacWise.c to MacWise.app >> FBtoC: compiling runtime >> FBtoC: compiling user code >> virtual memory exhausted: Cannot allocate memory >> virtual memory exhausted: Cannot allocate memory >> lipo: can't figure out the architecture type of: /var/folders/tC/ >> tCRopMvyHGKuYZkxDDg2S++++TI/-Tmp-//ccZw6MIN.out >> Compilation failed >> >> >> >> On Mar 8, 2008, at 9:21 AM, Rich Love wrote: >> >>> A few things I have discovered so far. >>> >>> 1. Getting rid of all the variable warnings helped me discover a >>> hard (red) error. >>> The error said that virtual memory was used up. >>> This was after letting it run all night. I don't know how long it >>> ran before running out of memory. >>> I have 52 gigs of virtual memory assigned by the system so that >>> was a lot of memory to use up. >>> This was on my dual G5 PowerMac. > Don't know Rich. Could we have some basics here just in case it > matters: > 1) How much real memory on the machine ( RAM ). > 2) How much free disk space on the hard drive > 3) Does a check with Disk Utility on the hard drive show it is ok? > Are permissions ok? > 4) Which OS X on this G5 Powermac? > 5) How many lines of code in MacWise? ( approximately ) > > What I do know is any compile over just a few minutes even with > optimization has a problem. If it lasts longer than a few minutes it > probably is stuck ( possible loop ) and will just keep grinding > until out of resources. > > > >>> >>> 2. When compiled with an Intel Mac Mini, I got a red error -192 >>> for ResType 'DLOG' in file MacWise.RSRC >>> I was no longer using any DLOG resources so I removed them and >>> that fixed the error. >>> The interesting thing is that when compiled on my G5 Mac, I never >>> got that error. > FBtoC is built from the same soruce code for Intel and PowerPC > macs, so the check for resources is the same. Any differences in > this case must be with the machine and the files. > > >>> 3. I have restarted the compile on my Intel Mac Mini with >>> Optimization on. It has been running for 20 minutes. > > > This is way too long Rich. If it runs for more than 5 minutes on the > compile, you can safety force quit knowing it is a goner. > > What we need is some debugging information ( maybe a parm to feed > gcc ) to get a clue what is going wrong. Maybe RP knows of such a > parm because I don't. RP knows gcc and its parms better than the > rest of us. > > > Brian S. > > -- > To unsubscribe, send ANY message to: futurebasic-unsubscribe@... >