On Wed, Apr 17, 2002 at 01:40:39PM -0400, Andy Dougherty wrote: > On Wed, 17 Apr 2002, Andy Dougherty wrote: > > If I had to guess, I'd guess this was the problem. This is probably not > > as heavily-tested a Configuration as the plain 'long' version, and most of > > that has probably been on little-endian systems, while I'll guess that Mac > > OS X is big-endian. > > > Hmm. You could try again with just 'long'. I'll also try with 'long > > long' on SPARC, which often uncovers such issues > > Nope, bad guess on my part. Parrot 0.0.5+ (checked out this morning) > did just fine with 'long long' opcode_t and INTVAL on SPARC Solaris 8.
Trying CVS parrot as of 1400 EDT (why not?), it still didn't work. Interestingly, typing "long" both times that Configure suggests "long long" doesn't work, either. (I get what appears to be the same problem: scads of compiler errors/warnings, and fail basically all of the first few tests but test one. I'm running late for something called "work" that might, ahm, be important for me to go to one of these days.) Now, I get a *lot* of errors/warnings. For example ---BEGIN--- core_ops_cg.c:811: illegal expression, found `&&' core_ops_cg.c:812: illegal expression, found `&&' core_ops_cg.c:816: illegal statement, missing `identifier' after `goto' core_ops_cg.c:816: syntax error, missing `;' after `*' core.ops:65: illegal statement, missing `identifier' after `goto' core.ops:65: syntax error, missing `;' after `*' core.ops:95: illegal statement, missing `identifier' after `goto' core.ops:95: syntax error, missing `;' after `*' core.ops:113: illegal statement, missing `identifier' after `goto' core.ops:113: syntax error, missing `;' after `*' ----END---- (Copied from the border between those two errors.) I get pages and pages of each of those errors, in addition to others. Is *this* related to long long, too? -- David "Cogent" Hand <http://davidhand.com/> <mailto:[EMAIL PROTECTED]> <icq:4321282>
