3 This program's build procedure is fairly standard. Try:
9 Options to the configure script are up to you. For details, run:
13 Please report build problems at:
15 http://sourceforge.net/bugs/?func=addbug&group_id=4664
17 (yes, even non-Linux problems).
20 ***** TIPS AND PROBLEMS:
22 - Try to use flex as the lexical analyzer. The lex scanner is now
23 separated from the flex version to allow the flex scanner to be
24 optimized. It's also a lot harder to diagnose and debug problems
25 without having full access to the particular platform and its version of
26 lex being used. flex is available everywhere --- AT&T lex is not.
28 - On Solaris, the native lex fails to catch our redefinition of YYLMAX
29 early enough, which leads to possible buffer overflows.
31 - On Linux systems (and possibly others) configure may fail if lex is
32 a synomyn for flex. To fix, do the following:
35 ./configure --with-flex
38 - On HP-UX several problems exist when using configure. Try the following
41 CFLAGS='-Ae -DYYCHAR_ARRAY' CURSES_LIBS=-lHcurses ./configure
43 - On Tru64, formerly known as Digital Unix, formerly known as DEC OSF/1,
44 the system-supplied libcurses causes cscope to terminate itself
45 immediately as it comes back to foreground after being suspended by
46 the user (Ctrl-Z). Using GNU Ncurses instead of OSF1 curses works
47 around the problem. According to the lynx and ncurses people, this
48 is a design problem of curses vs. signal handling, at the heart of it.
50 - Solaris 2.8 on Intel hardware may not work using the vendor's curses
51 implementation. Using the free NCurses should help.
53 - Some ancient Unix filesytems supported only 14 characters in
54 filenames. cscope no longer cares for that by default. If you want
55 to run it on such a system, #define the macro SHORT_NAMES_ONLY manually
56 (there's a definition in global.h you can uncomment).
58 Browse to http://cscope.sourceforge.net for more current information,
59 like reported bugs whose solutions haven't been put into this source