FW: Compiling 7.2 on Solaris 10
David Lehmann
Hello,
After untarring the vim7.2 package and running configure, I get the following error on Solaris 10. Can anyone help? Thanks.
% make
CC="gcc -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/openwin/include -I/usr/sfw/include -I/usr/sfw/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/openwin/include " srcdir=. sh ./osdef.sh
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/openwin/include -I/usr/sfw/include -I/usr/sfw/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -I/usr/openwin/include -o objects/buffer.o buffer.c
In file included from buffer.c:28:
vim.h:41: error: syntax error before ':' token
make: *** [objects/buffer.o] Error 1
--
David
Tony Mechelynck
vim.h line 41 is the last line but one of the following:
> /* ============ the header file puzzle (ca. 50-100 pieces) ========= */
>
> #ifdef HAVE_CONFIG_H /* GNU autoconf (or something else) was here */
> # include "auto/config.h"
> # define HAVE_PATHDEF
>
> /*
> * Check if configure correctly managed to find sizeof(int). If this failed,
> * it becomes zero. This is likely a problem of not being able to run the
> * test program. Other items from configure may also be wrong then!
> */
> # if (SIZEOF_INT == 0)
> Error: configure did not run properly. Check auto/config.log.
> # endif
So I recommend that you:
1) check my HowTo page,
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
2) make sure that you have all required "development packages" for any
libraries that your Vim will use
3) set your configure arguments as the values of _environment variables_
as shown in the above-mentioned HowTo
4) run "make reconfig" (or, maybe better, "make reconfig 2>&1 |tee
reconfig.log") in the top-level directory (the vim72 directory
containing src/ runtime/ etc.).
This way, even if make runs configure again (it may happens, especially
if there are patches for the makefile dependencies, in which case make
will rebuild its makefiles then restart) your configure settings won't
get lost.
If it goes wrong again, check the output of the configure phase, which
comes before what you quoted.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
64. The remote to the T.V. is missing...and you don't even care.