| Date: | Sat, 16 Jan 2010 13:41:38 -0600 |
|---|---|
| From: | Dan Gibson <degibson@xxxxxxxx> |
| Subject: | Re: [Gems-users] problem compiling ruby part 3 |
|
1. 'make clean' should be sufficient to resolve most compile-time transients. There IS benefit to removing Simics's module cache (a file called modules.cache), though I don't know where that file lives in Simics 3.x 2. I haven't seen the conflicts with stdint.h and unistd.h before. It might be redhat-specific... anyway, if you get the definitions correct (e.g., uint64 is a uint64, etc.) it should be OK. 3. I had a look at my own attrlex.c: yy_fatal_error is defined at the bottom of the file. Unfortunately, I have no idea why it does not appear in YOUR attrlex.c. Again, I suspect its absence is somehow specific to your host configuration. At any rate, there are a couple of work-arounds that are possible. I think the easiest would be for you to just manually add a definition for yy_fatal_error. Bear in mind that if you make clean, attrlex.c will go away, so keep a safe copy of your modified attrlex.c. Here's my definition of attrlex's yy_fatal_error -- hopefully it works for you, too. 1659 #ifdef YY_USE_PROTOS 1660 static void yy_fatal_error( yyconst char msg[] ) 1661 #else 1662 static void yy_fatal_error( msg ) 1663 char msg[]; 1664 #endif 1665 { 1666 (void) fprintf( stderr, "%s\n", msg ); 1667 exit( YY_EXIT_FAILURE ); 1668 } Good luck. Regards, Dan
On Sat, Jan 16, 2010 at 12:05 PM, Mladen Nikitovic <mladen@xxxxxx> wrote:
-- http://www.cs.wisc.edu/~gibson [esc]:wq! |
| [← Prev in Thread] | Current Thread | [Next in Thread→] |
|---|---|---|
| ||
| Previous by Date: | [Gems-users] problem compiling ruby part 3, Mladen Nikitovic |
|---|---|
| Next by Date: | Re: [Gems-users] problem compiling ruby part 3, Mladen Nikitovic |
| Previous by Thread: | [Gems-users] problem compiling ruby part 3, Mladen Nikitovic |
| Next by Thread: | Re: [Gems-users] problem compiling ruby part 3, Mladen Nikitovic |
| Indexes: | [Date] [Thread] |