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

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

Parent Directory Parent Directory | Revision Log Revision Log


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

  ViewVC Help
Powered by ViewVC 1.1.5