Red Hat Bugzilla – Bug 8069
syntax error in vim.h (vim 5.5)
Last modified: 2008-05-01 11:37:53 EDT
-- sent to Bram@vim.org also --- vim-5.5/src/vim.h Thu Sep 9 09:13:43 1999 +++ house-vim-5.5/src/vim.h Thu Dec 30 09:54:11 1999 @@ -26,7 +26,7 @@ * test program. Other items from configure may also be wrong then! */ # if (SIZEOF_INT == 0) - Error: configure did not run properly. Check config.log. +#error Error: configure did not run properly. Check config.log. # endif #endif
Bram: I submitted the patch to redhat also. Maybe its best to have distros keep a seperate patch outside of the prestine source in the situation you describe. The error is caused by a bad system setup. I was just trying to reduce 560 lines of meaningless gcc warnings and errors to 1 coherent error. If some preprocessors cant handle it I can see your point. On linux #error makes more sense. Packages are an easy way to deal with this issue. Trent Jarvi trentjarvi@yahoo.com --- Bram Moolenaar <Bram@moolenaar.net> wrote: > > Trent - > > > --- vim-5.5/src/vim.h Thu Sep 9 09:13:43 1999 > > +++ house-vim-5.5/src/vim.h Thu Dec 30 09:54:11 1999 > > @@ -26,7 +26,7 @@ > > * test program. Other items from configure may also be wrong then! > > */ > > # if (SIZEOF_INT == 0) > > - Error: configure did not run properly. Check config.log. > > +#error Error: configure did not run properly. Check config.log. > > # endif > > #endif > > That's how it was before, but this caused trouble for some compilers. Did you > have trouble with how it is now? > > - Bram >
[I guess I should mention this all started with configure failing to write the test file for sizeof(int) on a near full fs.] --- Bram Moolenaar <Bram@moolenaar.net> wrote: > > > I submitted the patch to redhat also. Maybe its best to have > > distros keep a seperate patch outside of the prestine source > > in the situation you describe. > > It's alright if this is patched in a Linux distribution where gcc is always > used.
I don't think this needs to be fixed - sizeof(int) is not 0 on Linux, so first of all you aren't getting to this place unless something's very wrong. Also, both versions will generate an error, and point you to the same place.