/[pcre]/code/trunk/NON-UNIX-USE
ViewVC logotype

Contents of /code/trunk/NON-UNIX-USE

Parent Directory Parent Directory | Revision Log Revision Log


Revision 691 - (hide annotations) (download)
Sun Sep 11 14:31:21 2011 UTC (3 years, 2 months ago) by ph10
File size: 21186 byte(s)
Final source and document tidies for 8.20-RC1.

1 nigel 41 Compiling PCRE on non-Unix systems
2     ----------------------------------
3    
4 ph10 131 This document contains the following sections:
5    
6     General
7 ph10 134 Generic instructions for the PCRE C library
8 ph10 131 The C++ wrapper functions
9     Building for virtual Pascal
10 ph10 198 Stack size in Windows environments
11 ph10 319 Linking programs in Windows environments
12 ph10 134 Comments about Win32 builds
13 ph10 316 Building PCRE on Windows with CMake
14 ph10 306 Use of relative paths with CMake on Windows
15 ph10 461 Testing with RunTest.bat
16 ph10 131 Building under Windows with BCC5.5
17 ph10 134 Building PCRE on OpenVMS
18 ph10 461 Building PCRE on Stratus OpenVOS
19 ph10 131
20    
21     GENERAL
22    
23 ph10 200 I (Philip Hazel) have no experience of Windows or VMS sytems and how their
24 ph10 101 libraries work. The items in the PCRE distribution and Makefile that relate to
25 ph10 122 anything other than Unix-like systems are untested by me.
26 nigel 63
27 ph10 406 There are some other comments and files (including some documentation in CHM
28 ph10 401 format) in the Contrib directory on the FTP site:
29 ph10 101
30 nigel 75 ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
31 nigel 41
32 ph10 144 If you want to compile PCRE for a non-Unix system (especially for a system that
33     does not support "configure" and "make" files), note that the basic PCRE
34     library consists entirely of code written in Standard C, and so should compile
35     successfully on any system that has a Standard C compiler and library. The C++
36     wrapper functions are a separate issue (see below).
37 nigel 73
38 ph10 316 The PCRE distribution includes a "configure" file for use by the Configure/Make
39     build system, as found in many Unix-like environments. There is also support
40 ph10 672 for CMake, which some users prefer, especially in Windows environments. There
41     are some instructions for CMake under Windows in the section entitled "Building
42     PCRE with CMake" below. CMake can also be used to build PCRE in Unix-like
43     systems.
44 nigel 75
45 ph10 144
46 ph10 131 GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
47 nigel 75
48 ph10 672 The following are generic instructions for building the PCRE C library "by
49     hand":
50 nigel 75
51 ph10 188 (1) Copy or rename the file config.h.generic as config.h, and edit the macro
52     settings that it contains to whatever is appropriate for your environment.
53     In particular, if you want to force a specific value for newline, you can
54 ph10 237 define the NEWLINE macro. When you compile any of the PCRE modules, you
55     must specify -DHAVE_CONFIG_H to your compiler so that config.h is included
56     in the sources.
57 ph10 197
58 ph10 188 An alternative approach is not to edit config.h, but to use -D on the
59 ph10 243 compiler command line to make any changes that you need to the
60 ph10 237 configuration options. In this case -DHAVE_CONFIG_H must not be set.
61 ph10 197
62 ph10 188 NOTE: There have been occasions when the way in which certain parameters
63     in config.h are used has changed between releases. (In the configure/make
64     world, this is handled automatically.) When upgrading to a new release,
65     you are strongly advised to review config.h.generic before re-using what
66     you had previously.
67 ph10 197
68 ph10 188 (2) Copy or rename the file pcre.h.generic as pcre.h.
69 ph10 197
70 ph10 188 (3) EITHER:
71     Copy or rename file pcre_chartables.c.dist as pcre_chartables.c.
72 ph10 197
73 ph10 188 OR:
74 ph10 243 Compile dftables.c as a stand-alone program (using -DHAVE_CONFIG_H if
75 ph10 237 you have set up config.h), and then run it with the single argument
76     "pcre_chartables.c". This generates a set of standard character tables
77     and writes them to that file. The tables are generated using the default
78     C locale for your system. If you want to use a locale that is specified
79     by LC_xxx environment variables, add the -L option to the dftables
80     command. You must use this method if you are building on a system that
81     uses EBCDIC code.
82 ph10 197
83 ph10 188 The tables in pcre_chartables.c are defaults. The caller of PCRE can
84     specify alternative tables at run time.
85 ph10 197
86 ph10 188 (4) Ensure that you have the following header files:
87 ph10 197
88 ph10 188 pcre_internal.h
89     ucp.h
90 ph10 197
91 ph10 188 (5) Also ensure that you have the following file, which is #included as source
92 ph10 287 when building a debugging version of PCRE, and is also used by pcretest.
93 ph10 197
94 ph10 188 pcre_printint.src
95 ph10 197
96 ph10 237 (6) Compile the following source files, setting -DHAVE_CONFIG_H as a compiler
97 ph10 243 option if you have set up config.h with your configuration, or else use
98 ph10 237 other -D settings to change the configuration as required.
99 ph10 197
100 ph10 188 pcre_chartables.c
101     pcre_compile.c
102     pcre_config.c
103     pcre_dfa_exec.c
104     pcre_exec.c
105     pcre_fullinfo.c
106     pcre_get.c
107     pcre_globals.c
108     pcre_info.c
109     pcre_maketables.c
110     pcre_newline.c
111     pcre_ord2utf8.c
112     pcre_refcount.c
113     pcre_study.c
114     pcre_tables.c
115     pcre_try_flipped.c
116 ph10 374 pcre_ucd.c
117 ph10 188 pcre_valid_utf8.c
118     pcre_version.c
119     pcre_xclass.c
120 ph10 197
121 ph10 200 Make sure that you include -I. in the compiler command (or equivalent for
122     an unusual compiler) so that all included PCRE header files are first
123     sought in the current directory. Otherwise you run the risk of picking up
124     a previously-installed file from somewhere else.
125 ph10 691
126 ph10 672 (7) If you have defined SUPPORT_JIT in config.h, you must also compile
127 ph10 691
128 ph10 672 pcre_jit_compile.c
129 ph10 691
130     This file #includes sources from the sljit subdirectory, where there
131 ph10 672 should be 16 files, all of whose names begin with "sljit".
132 ph10 200
133 ph10 672 (8) Now link all the compiled code into an object library in whichever form
134 ph10 188 your system keeps such libraries. This is the basic PCRE C library. If
135     your system has static and shared libraries, you may have to do this once
136     for each type.
137 ph10 197
138 ph10 672 (9) Similarly, if you want to build the POSIX wrapper functions, ensure that
139 ph10 489 you have the pcreposix.h file and then compile pcreposix.c (remembering
140     -DHAVE_CONFIG_H if necessary). Link the result (on its own) as the
141     pcreposix library.
142 nigel 41
143 ph10 672 (10) Compile the test program pcretest.c (again, don't forget -DHAVE_CONFIG_H).
144 ph10 489 This needs the functions in the PCRE library when linking. It also needs
145     the pcreposix wrapper functions unless you compile it with -DNOPOSIX. The
146     pcretest.c program also needs the pcre_printint.src source file, which it
147     #includes.
148 ph10 182
149 ph10 672 (11) Run pcretest on the testinput files in the testdata directory, and check
150     that the output matches the corresponding testoutput files. Some tests are
151 ph10 691 relevant only when certain build-time options are selected. For example,
152     test 4 is for UTF-8 support, and will not run if you have build PCRE
153     without it. See the comments at the start of each testinput file. If you
154     have a suitable Unix-like shell, the RunTest script will run the
155 ph10 672 appropriate tests for you.
156 ph10 691
157 ph10 672 Note that the supplied files are in Unix format, with just LF characters
158     as line terminators. You may need to edit them to change this if your
159     system uses a different convention. If you are using Windows, you probably
160     should use the wintestinput3 file instead of testinput3 (and the
161     corresponding output file). This is a locale test; wintestinput3 sets the
162     locale to "french" rather than "fr_FR", and there some minor output
163     differences.
164 ph10 691
165 ph10 672 (12) If you have built PCRE with SUPPORT_JIT, the JIT features will be tested
166     by the testdata files. However, you might also like to build and run
167     the JIT test program, pcre_jit_test.c.
168 nigel 75
169 ph10 672 (13) If you want to use the pcregrep command, compile and link pcregrep.c; it
170 ph10 188 uses only the basic PCRE library (it does not need the pcreposix library).
171 nigel 41
172 nigel 75
173 nigel 79 THE C++ WRAPPER FUNCTIONS
174    
175 ph10 111 The PCRE distribution also contains some C++ wrapper functions and tests,
176 nigel 79 contributed by Google Inc. On a system that can use "configure" and "make",
177     the functions are automatically built into a library called pcrecpp. It should
178     be straightforward to compile the .cc files manually on other systems. The
179     files called xxx_unittest.cc are test programs for each of the corresponding
180     xxx.cc files.
181    
182    
183 ph10 111 BUILDING FOR VIRTUAL PASCAL
184 nigel 75
185 ph10 128 A script for building PCRE using Borland's C++ compiler for use with VPASCAL
186     was contributed by Alexander Tokarev. Stefan Weber updated the script and added
187     additional files. The following files in the distribution are for building PCRE
188 ph10 135 for use with VP/Borland: makevp_c.txt, makevp_l.txt, makevp.bat, pcregexp.pas.
189 ph10 101
190 ph10 111
191 ph10 198 STACK SIZE IN WINDOWS ENVIRONMENTS
192    
193     The default processor stack size of 1Mb in some Windows environments is too
194     small for matching patterns that need much recursion. In particular, test 2 may
195     fail because of this. Normally, running out of stack causes a crash, but there
196     have been cases where the test program has just died silently. See your linker
197 ph10 200 documentation for how to increase stack size if you experience problems. The
198     Linux default of 8Mb is a reasonable choice for the stack, though even that can
199 ph10 261 be too small for some pattern/subject combinations.
200 ph10 198
201 ph10 260 PCRE has a compile configuration option to disable the use of stack for
202     recursion so that heap is used instead. However, pattern matching is
203     significantly slower when this is done. There is more about stack usage in the
204     "pcrestack" documentation.
205 ph10 198
206 ph10 111
207 ph10 317 LINKING PROGRAMS IN WINDOWS ENVIRONMENTS
208    
209 ph10 319 If you want to statically link a program against a PCRE library in the form of
210 ph10 535 a non-dll .a file, you must define PCRE_STATIC before including pcre.h or
211 ph10 526 pcrecpp.h, otherwise the pcre_malloc() and pcre_free() exported functions will
212     be declared __declspec(dllimport), with unwanted results.
213 ph10 317
214    
215 ph10 359 CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS
216    
217 ph10 371 It is possible to compile programs to use different calling conventions using
218     MSVC. Search the web for "calling conventions" for more information. To make it
219     easier to change the calling convention for the exported functions in the
220     PCRE library, the macro PCRE_CALL_CONVENTION is present in all the external
221     definitions. It can be set externally when compiling (e.g. in CFLAGS). If it is
222     not set, it defaults to empty; the default calling convention is then used
223 ph10 359 (which is what is wanted most of the time).
224    
225    
226 ph10 260 COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE WITH CMAKE" below)
227    
228 ph10 177 There are two ways of building PCRE using the "configure, make, make install"
229 ph10 144 paradigm on Windows systems: using MinGW or using Cygwin. These are not at all
230 ph10 145 the same thing; they are completely different from each other. There is also
231 ph10 319 support for building using CMake, which some users find a more straightforward
232     way of building PCRE under Windows. However, the tests are not run
233 ph10 316 automatically when CMake is used.
234 nigel 93
235 ph10 131 The MinGW home page (http://www.mingw.org/) says this:
236 nigel 93
237 ph10 131 MinGW: A collection of freely available and freely distributable Windows
238     specific header files and import libraries combined with GNU toolsets that
239     allow one to produce native Windows programs that do not rely on any
240     3rd-party C runtime DLLs.
241 nigel 93
242 ph10 131 The Cygwin home page (http://www.cygwin.com/) says this:
243 ph10 111
244 ph10 134 Cygwin is a Linux-like environment for Windows. It consists of two parts:
245    
246     . A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing
247 ph10 131 substantial Linux API functionality
248 ph10 134
249 ph10 131 . A collection of tools which provide Linux look and feel.
250 ph10 111
251 ph10 134 The Cygwin DLL currently works with all recent, commercially released x86 32
252 ph10 131 bit and 64 bit versions of Windows, with the exception of Windows CE.
253 ph10 111
254 ph10 131 On both MinGW and Cygwin, PCRE should build correctly using:
255 nigel 41
256 ph10 134 ./configure && make && make install
257 ph10 148
258 ph10 146 This should create two libraries called libpcre and libpcreposix, and, if you
259 ph10 182 have enabled building the C++ wrapper, a third one called libpcrecpp. These are
260 ph10 672 independent libraries: when you link with libpcreposix or libpcrecpp you must
261 ph10 182 also link with libpcre, which contains the basic functions. (Some earlier
262     releases of PCRE included the basic libpcre functions in libpcreposix. This no
263 ph10 181 longer happens.)
264 ph10 134
265 ph10 317 A user submitted a special-purpose patch that makes it easy to create
266 ph10 319 "pcre.dll" under mingw32 using the "msys" environment. It provides "pcre.dll"
267 ph10 317 as a special target. If you use this target, no other files are built, and in
268     particular, the pcretest and pcregrep programs are not built. An example of how
269     this might be used is:
270 nigel 41
271 ph10 317 ./configure --enable-utf --disable-cpp CFLAGS="-03 -s"; make pcre.dll
272    
273 ph10 131 Using Cygwin's compiler generates libraries and executables that depend on
274     cygwin1.dll. If a library that is generated this way is distributed,
275     cygwin1.dll has to be distributed as well. Since cygwin1.dll is under the GPL
276     licence, this forces not only PCRE to be under the GPL, but also the entire
277     application. A distributor who wants to keep their own code proprietary must
278     purchase an appropriate Cygwin licence.
279 nigel 63
280 ph10 131 MinGW has no such restrictions. The MinGW compiler generates a library or
281     executable that can run standalone on Windows without any third party dll or
282     licensing issues.
283 nigel 63
284 ph10 131 But there is more complication:
285 nigel 63
286 ph10 131 If a Cygwin user uses the -mno-cygwin Cygwin gcc flag, what that really does is
287     to tell Cygwin's gcc to use the MinGW gcc. Cygwin's gcc is only acting as a
288     front end to MinGW's gcc (if you install Cygwin's gcc, you get both Cygwin's
289     gcc and MinGW's gcc). So, a user can:
290 nigel 63
291 ph10 134 . Build native binaries by using MinGW or by getting Cygwin and using
292 ph10 131 -mno-cygwin.
293 nigel 63
294 ph10 134 . Build binaries that depend on cygwin1.dll by using Cygwin with the normal
295 ph10 131 compiler flags.
296 nigel 63
297 ph10 134 The test files that are supplied with PCRE are in Unix format, with LF
298     characters as line terminators. It may be necessary to change the line
299 ph10 489 terminators in order to get some of the tests to work.
300 nigel 63
301    
302 ph10 316 BUILDING PCRE ON WINDOWS WITH CMAKE
303 ph10 258
304 ph10 434 CMake is an alternative configuration facility that can be used instead of the
305     traditional Unix "configure". CMake creates project files (make files, solution
306     files, etc.) tailored to numerous development environments, including Visual
307     Studio, Borland, Msys, MinGW, NMake, and Unix. The following instructions
308 ph10 260 were contributed by a PCRE user.
309 ph10 258
310 ph10 434 1. Install the latest CMake version available from http://www.cmake.org/, and
311     ensure that cmake\bin is on your path.
312 ph10 319
313 ph10 316 2. Unzip (retaining folder structure) the PCRE source tree into a source
314     directory such as C:\pcre.
315 ph10 319
316 ph10 434 3. Create a new, empty build directory, for example C:\pcre\build\
317 ph10 319
318 ph10 434 4. Run cmake-gui from the Shell envirornment of your build tool, for example,
319     Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++.
320 ph10 319
321 ph10 316 5. Enter C:\pcre\pcre-xx and C:\pcre\build for the source and build
322 ph10 434 directories, respectively.
323 ph10 319
324 ph10 316 6. Hit the "Configure" button.
325 ph10 319
326 ph10 434 7. Select the particular IDE / build tool that you are using (Visual
327     Studio, MSYS makefiles, MinGW makefiles, etc.)
328 ph10 319
329 ph10 461 8. The GUI will then list several configuration options. This is where
330 ph10 434 you can enable UTF-8 support or other PCRE optional features.
331 ph10 319
332 ph10 461 9. Hit "Configure" again. The adjacent "Generate" button should now be
333 ph10 434 active.
334 ph10 258
335 ph10 434 10. Hit "Generate".
336 ph10 258
337     11. The build directory should now contain a usable build system, be it a
338 ph10 434 solution file for Visual Studio, makefiles for MinGW, etc. Exit from
339     cmake-gui and use the generated build system with your compiler or IDE.
340 ph10 258
341    
342 ph10 306 USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS
343    
344     A PCRE user comments as follows:
345 ph10 309
346 ph10 306 I thought that others may want to know the current state of
347     CMAKE_USE_RELATIVE_PATHS support on Windows.
348    
349     Here it is:
350     -- AdditionalIncludeDirectories is only partially modified (only the
351     first path - see below)
352     -- Only some of the contained file paths are modified - shown below for
353     pcre.vcproj
354     -- It properly modifies
355    
356     I am sure CMake people can fix that if they want to. Until then one will
357     need to replace existing absolute paths in project files with relative
358     paths manually (e.g. from VS) - relative to project file location. I did
359     just that before being told to try CMAKE_USE_RELATIVE_PATHS. Not a big
360 ph10 309 deal.
361 ph10 306
362     AdditionalIncludeDirectories="E:\builds\pcre\build;E:\builds\pcre\pcre-7.5;"
363     AdditionalIncludeDirectories=".;E:\builds\pcre\pcre-7.5;"
364    
365     RelativePath="pcre.h">
366     RelativePath="pcre_chartables.c">
367     RelativePath="pcre_chartables.c.rule">
368    
369    
370     TESTING WITH RUNTEST.BAT
371    
372 ph10 258 1. Copy RunTest.bat into the directory where pcretest.exe has been created.
373    
374     2. Edit RunTest.bat and insert a line that indentifies the relative location of
375     the pcre source, e.g.:
376    
377     set srcdir=..\pcre-7.4-RC3
378    
379     3. Run RunTest.bat from a command shell environment. Test outputs will
380     automatically be compared to expected results, and discrepancies will
381     identified in the console output.
382    
383     4. To test pcrecpp, run pcrecpp_unittest.exe, pcre_stringpiece_unittest.exe and
384     pcre_scanner_unittest.exe.
385    
386 ph10 309
387 ph10 131 BUILDING UNDER WINDOWS WITH BCC5.5
388 nigel 63
389 ph10 131 Michael Roy sent these comments about building PCRE under Windows with BCC5.5:
390 nigel 63
391 ph10 131 Some of the core BCC libraries have a version of PCRE from 1998 built in,
392     which can lead to pcre_exec() giving an erroneous PCRE_ERROR_NULL from a
393     version mismatch. I'm including an easy workaround below, if you'd like to
394     include it in the non-unix instructions:
395 nigel 63
396 ph10 131 When linking a project with BCC5.5, pcre.lib must be included before any of
397     the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command
398     line.
399 nigel 63
400 ph10 392
401 ph10 382 BUILDING UNDER WINDOWS CE WITH VISUAL STUDIO 200x
402 ph10 259
403 ph10 392 Vincent Richomme sent a zip archive of files to help with this process. They
404     can be found in the file "pcre-vsbuild.zip" in the Contrib directory of the FTP
405 ph10 382 site.
406    
407    
408 nigel 75 BUILDING PCRE ON OPENVMS
409    
410 nigel 79 Dan Mooney sent the following comments about building PCRE on OpenVMS. They
411     relate to an older version of PCRE that used fewer source files, so the exact
412     commands will need changing. See the current list of source files above.
413 nigel 75
414     "It was quite easy to compile and link the library. I don't have a formal
415     make file but the attached file [reproduced below] contains the OpenVMS DCL
416     commands I used to build the library. I had to add #define
417     POSIX_MALLOC_THRESHOLD 10 to pcre.h since it was not defined anywhere.
418    
419     The library was built on:
420     O/S: HP OpenVMS v7.3-1
421     Compiler: Compaq C v6.5-001-48BCD
422     Linker: vA13-01
423    
424     The test results did not match 100% due to the issues you mention in your
425     documentation regarding isprint(), iscntrl(), isgraph() and ispunct(). I
426     modified some of the character tables temporarily and was able to get the
427     results to match. Tests using the fr locale did not match since I don't have
428     that locale loaded. The study size was always reported to be 3 less than the
429     value in the standard test output files."
430    
431     =========================
432     $! This DCL procedure builds PCRE on OpenVMS
433     $!
434     $! I followed the instructions in the non-unix-use file in the distribution.
435     $!
436     $ COMPILE == "CC/LIST/NOMEMBER_ALIGNMENT/PREFIX_LIBRARY_ENTRIES=ALL_ENTRIES
437     $ COMPILE DFTABLES.C
438     $ LINK/EXE=DFTABLES.EXE DFTABLES.OBJ
439     $ RUN DFTABLES.EXE/OUTPUT=CHARTABLES.C
440     $ COMPILE MAKETABLES.C
441     $ COMPILE GET.C
442     $ COMPILE STUDY.C
443     $! I had to set POSIX_MALLOC_THRESHOLD to 10 in PCRE.H since the symbol
444     $! did not seem to be defined anywhere.
445     $! I edited pcre.h and added #DEFINE SUPPORT_UTF8 to enable UTF8 support.
446     $ COMPILE PCRE.C
447     $ LIB/CREATE PCRE MAKETABLES.OBJ, GET.OBJ, STUDY.OBJ, PCRE.OBJ
448     $! I had to set POSIX_MALLOC_THRESHOLD to 10 in PCRE.H since the symbol
449     $! did not seem to be defined anywhere.
450     $ COMPILE PCREPOSIX.C
451     $ LIB/CREATE PCREPOSIX PCREPOSIX.OBJ
452     $ COMPILE PCRETEST.C
453     $ LINK/EXE=PCRETEST.EXE PCRETEST.OBJ, PCRE/LIB, PCREPOSIX/LIB
454     $! C programs that want access to command line arguments must be
455     $! defined as a symbol
456     $ PCRETEST :== "$ SYS$ROADSUSERS:[DMOONEY.REGEXP]PCRETEST.EXE"
457     $! Arguments must be enclosed in quotes.
458     $ PCRETEST "-C"
459     $! Test results:
460     $!
461     $! The test results did not match 100%. The functions isprint(), iscntrl(),
462     $! isgraph() and ispunct() on OpenVMS must not produce the same results
463     $! as the system that built the test output files provided with the
464     $! distribution.
465     $!
466     $! The study size did not match and was always 3 less on OpenVMS.
467     $!
468     $! Locale could not be set to fr
469     $!
470     =========================
471    
472 ph10 441
473     BUILDING PCRE ON STRATUS OPENVOS
474    
475     These notes on the port of PCRE to VOS (lightly edited) were supplied by
476     Ashutosh Warikoo, whose email address has the local part awarikoo and the
477     domain nse.co.in. The port was for version 7.9 in August 2009.
478    
479     1. Building PCRE
480    
481     I built pcre on OpenVOS Release 17.0.1at using GNU Tools 3.4a without any
482     problems. I used the following packages to build PCRE:
483    
484     ftp://ftp.stratus.com/pub/vos/posix/ga/posix.save.evf.gz
485 ph10 461
486 ph10 441 Please read and follow the instructions that come with these packages. To start
487     the build of pcre, from the root of the package type:
488    
489     ./build.sh
490    
491     2. Installing PCRE
492    
493     Once you have successfully built PCRE, login to the SysAdmin group, switch to
494     the root user, and type
495    
496     [ !create_dir (master_disk)>usr --if needed ]
497     [ !create_dir (master_disk)>usr>local --if needed ]
498     !gmake install
499    
500     This installs PCRE and its man pages into /usr/local. You can add
501     (master_disk)>usr>local>bin to your command search paths, or if you are in
502     BASH, add /usr/local/bin to the PATH environment variable.
503    
504     4. Restrictions
505    
506     This port requires readline library optionally. However during the build I
507     faced some yet unexplored errors while linking with readline. As it was an
508     optional component I chose to disable it.
509    
510     5. Known Problems
511    
512     I ran a the test suite, but you will have to be your own judge of whether this
513     command, and this port, suits your purposes. If you find any problems that
514     appear to be related to the port itself, please let me know. Please see the
515     build.log file in the root of the package also.
516    
517    
518     =========================
519 ph10 672 Last Updated: 23 August 2011
520 nigel 41 ****

Properties

Name Value
svn:eol-style native
svn:keywords "Author Date Id Revision Url"

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12