/[pcre]/code/trunk/NON-AUTOTOOLS-BUILD
ViewVC logotype

Contents of /code/trunk/NON-AUTOTOOLS-BUILD

Parent Directory Parent Directory | Revision Log Revision Log


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

  ViewVC Help
Powered by ViewVC 1.1.5