next up previous contents
Next: Known builds Up: Using rq2proxy Previous: Support

Building and installing rq2proxy

rq2proxy uses GNU autoconf, so you should just be able to do

$ ./configure
$ make
$ make docs
$ make install

For more details about how to install the program, see the INSTALL file in the distribution directory and the output of ./configure -help.

The make docs stage simply rebuilds the documentation: it shouldn't be necessary, so you can omit it if you don't have LATEX, dvips and latex2html.

If that doesn't work, try doing:

$ ./configure
$ make lexclean
$ make
$ make docs
$ make install
To kill off the stale bison and flex output files.

You may need to use GNU make to build the system on some platforms (eg. OSF/1), since the native make doesn't understand how to regenerate the dependency files.

You can remove build files by doing make clean, and attempt to return the distribution to a pristine state by doing make distclean.

If configure can't find yacc or lex, don't despair--pre-built copies of y.tab.c and lex.yy.c are provided. This does, however, mean that you won't be able to change the parser and scanner and recompile. Free replacements for yacc and lex are available as bison and flex, respectively (these are the programs rq2proxy was developed with), available from the GNU project. Likewise, if libfl is not available (eg. because flex is not installed on your machine), you will have to remove lex.yy.c and have your copy of lex rebuild it.

Note that this program probably will not work on 64-bit systems such as the DEC Alpha, where sizeof(unsigned long) == sizeof(long) == sizeof(int) == 4. In the next version...

If you want to mess about with the internals of the program, take a look at config.h.in--it contains a few defines you can tweak to use different routing policies. Note that tweaking most of these will result in variously nasty effects--see §7.



 
next up previous contents
Next: Known builds Up: Using rq2proxy Previous: Support
Richard Watts
1998-12-22