Skip to content

Commit 5f9f8b2

Browse files
alexgubanowmarkusicu
authored andcommitted
ICU-22714 fix zos build, use OpenXL
See unicode-org#3008
1 parent 8f82fac commit 5f9f8b2

File tree

26 files changed

+276
-650
lines changed

26 files changed

+276
-650
lines changed

.gitattributes

Lines changed: 103 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -9,78 +9,121 @@
99
# The only difference between the two is that git will do EOL conversion for text files.
1010
# "!eol" is the equivalent of "svneol=native".
1111

12-
*.bat text !eol
13-
*.c text !eol diff=cpp
14-
*.cc text !eol diff=cpp
15-
*.classpath text !eol
12+
*.bat text !eol zos-working-tree-encoding=IBM-1047
13+
*.c text !eol zos-working-tree-encoding=UTF-8 diff=cpp
14+
*.cc text !eol zos-working-tree-encoding=UTF-8 diff=cpp
15+
*.classpath text !eol zos-working-tree-encoding=IBM-1047
1616
*.cmd text eol=crlf
17-
*.cpp text !eol diff=cpp
18-
*.css text !eol diff=css
19-
*.dsp text !eol
20-
*.dsw text !eol
21-
*.dtd text !eol
22-
*.el text !eol
23-
*.filters text !eol
24-
*.h text !eol diff=cpp
25-
*.htm text !eol diff=html
26-
*.html text !eol diff=html
27-
*.in text !eol
28-
*.java text !eol diff=java
29-
*.launch text !eol
30-
*.m4 text !eol
31-
*.mak text !eol
32-
*.md text !eol
33-
*.MF text !eol
34-
*.mk text !eol
35-
*.pl text !eol diff=perl
36-
*.pm text !eol diff=perl
37-
*.project text !eol
38-
*.properties text !eol
39-
*.props text !eol
40-
*.py text !eol diff=python
41-
*.rc text !eol
17+
*.cpp text !eol zos-working-tree-encoding=UTF-8 diff=cpp
18+
*.css text !eol zos-working-tree-encoding=IBM-1047 diff=css
19+
*.dsp text !eol zos-working-tree-encoding=IBM-1047
20+
*.dsw text !eol zos-working-tree-encoding=IBM-1047
21+
*.dtd text !eol zos-working-tree-encoding=IBM-1047
22+
*.el text !eol zos-working-tree-encoding=IBM-1047
23+
*.filters text !eol zos-working-tree-encoding=IBM-1047
24+
*.h text !eol zos-working-tree-encoding=UTF-8 diff=cpp
25+
*.htm text !eol zos-working-tree-encoding=UTF-8 diff=html
26+
*.html text !eol zos-working-tree-encoding=UTF-8 diff=html
27+
*.in text !eol zos-working-tree-encoding=IBM-1047
28+
*.java text !eol zos-working-tree-encoding=UTF-8 diff=java
29+
*.launch text !eol zos-working-tree-encoding=IBM-1047
30+
*.m4 text !eol zos-working-tree-encoding=IBM-1047
31+
*.mak text !eol zos-working-tree-encoding=IBM-1047
32+
*.md text !eol zos-working-tree-encoding=UTF-8
33+
*.MF text !eol zos-working-tree-encoding=IBM-1047
34+
*.mk text !eol zos-working-tree-encoding=IBM-1047
35+
*.pl text !eol zos-working-tree-encoding=UTF-8 diff=perl
36+
*.pm text !eol zos-working-tree-encoding=IBM-1047 diff=perl
37+
*.project text !eol zos-working-tree-encoding=IBM-1047
38+
*.properties text !eol zos-working-tree-encoding=UTF-8
39+
*.props text !eol zos-working-tree-encoding=IBM-1047
40+
*.py text !eol zos-working-tree-encoding=UTF-8 diff=python
41+
*.rc text !eol zos-working-tree-encoding=IBM-1047
4242
*.sh text eol=lf
4343
*.sed text eol=lf
44-
*.sln text !eol
45-
*.stub text !eol
46-
*.targets text !eol
47-
*.txt text !eol
48-
*.ucm text !eol
49-
*.vcproj text !eol
50-
*.vcxproj text !eol
51-
*.xml text !eol
52-
*.xsl text !eol
53-
*.xslt text !eol
54-
AUTHORS text !eol
55-
BUILD text !eol
56-
COPYING text !eol
57-
Changelog text !eol
58-
LICENSE text !eol
59-
Makefile text !eol
60-
README text !eol
61-
SConscript text !eol
62-
SConstruct text !eol
63-
configure text !eol
44+
*.sln text !eol zos-working-tree-encoding=UTF-8
45+
*.stub text !eol zos-working-tree-encoding=IBM-1047
46+
*.targets text !eol zos-working-tree-encoding=UTF-8
47+
*.txt text !eol zos-working-tree-encoding=UTF-8
48+
*.ucm text !eol zos-working-tree-encoding=IBM-1047
49+
*.vcproj text !eol zos-working-tree-encoding=UTF-8
50+
*.vcproj.filters text !eol zos-working-tree-encoding=UTF-8
51+
*.vcxproj text !eol zos-working-tree-encoding=UTF-8
52+
*.vcxproj.filters text !eol zos-working-tree-encoding=UTF-8
53+
*.xml text !eol zos-working-tree-encoding=UTF-8
54+
*.xsl text !eol zos-working-tree-encoding=IBM-1047
55+
*.xslt text !eol zos-working-tree-encoding=IBM-1047
56+
AUTHORS text !eol zos-working-tree-encoding=IBM-1047
57+
BUILD text !eol zos-working-tree-encoding=IBM-1047
58+
COPYING text !eol zos-working-tree-encoding=IBM-1047
59+
Changelog text !eol zos-working-tree-encoding=IBM-1047
60+
LICENSE text !eol zos-working-tree-encoding=IBM-1047
61+
Makefile text !eol zos-working-tree-encoding=IBM-1047
62+
README text !eol zos-working-tree-encoding=UTF-8
63+
SConscript text !eol zos-working-tree-encoding=IBM-1047
64+
SConstruct text !eol zos-working-tree-encoding=IBM-1047
65+
config* text !eol zos-working-tree-encoding=IBM-1047
6466

6567
# Explicitly set the following file types as binary files.
66-
*.bin -text
67-
*.brk -text
68-
*.cnv -text
69-
*.icu -text
70-
*.res -text
71-
*.nrm -text
72-
*.spp -text
73-
*.tri2 -text
74-
*.otf -text
75-
*.utf16be -text
68+
*.bin -text zos-working-tree-encoding=UTF-8
69+
*.brk -text zos-working-tree-encoding=UTF-8
70+
*.cnv -text zos-working-tree-encoding=UTF-8
71+
*.icu -text zos-working-tree-encoding=UTF-8
72+
*.res -text zos-working-tree-encoding=UTF-8
73+
*.nrm -text zos-working-tree-encoding=UTF-8
74+
*.spp -text zos-working-tree-encoding=UTF-8
75+
*.tri2 -text zos-working-tree-encoding=UTF-8
76+
*.otf -text zos-working-tree-encoding=UTF-8
77+
*.utf16be -text zos-working-tree-encoding=UTF-8
7678

7779
# The following file types are stored in Git-LFS.
7880
# Only .jars
79-
*.jar filter=lfs diff=lfs merge=lfs -text
81+
*.jar filter=lfs diff=lfs merge=lfs -text zos-working-tree-encoding=UTF-8
8082

8183
# Enable syntax highlighting on GitHub.com
8284
.cpyskip.txt linguist-language=Ignore-List
8385

8486
# Use JSONC for syntax highlighting on GitHub.com
8587
*.json linguist-language=jsonc
8688

89+
#Files below should be IBM-1047 on mainframe, while other txt shall stay UTF-8
90+
icu4c/source/runConfigureICU zos-working-tree-encoding=IBM-1047
91+
icu4c/source/install-sh zos-working-tree-encoding=IBM-1047
92+
icu4c/source/mkinstalldirs zos-working-tree-encoding=IBM-1047
93+
sources.txt zos-working-tree-encoding=IBM-1047
94+
*.sub zos-working-tree-encoding=IBM-1047
95+
icu4c/source/data/mappings/convrtrs.txt zos-working-tree-encoding=IBM-1047
96+
icu4c/source/data/sprep/*.txt text !eol zos-working-tree-encoding=IBM-1047
97+
icu4c/source/data/unidata/NormalizationCorrections.txt text !eol zos-working-tree-encoding=IBM-1047
98+
icu4c/source/data/zone/tzdbNames.txt text !eol zos-working-tree-encoding=IBM-1047
99+
icu4c/source/test/testdata/*.txt text !eol zos-working-tree-encoding=IBM-1047
100+
icu4c/source/test/testdata/filters/*.txt text !eol zos-working-tree-encoding=IBM-1047
101+
icu4c/source/test/testdata/*.ucm text !eol zos-working-tree-encoding=IBM-1047
102+
103+
#simpler to say who should stay UTF-8 from test data
104+
icu4c/source/data/misc/*.txt text !eol zos-working-tree-encoding=UTF-8
105+
icu4c/source/test/cintltst/usrchdat.inc text !eol zos-working-tree-encoding=UTF-8
106+
icu4c/source/test/testdata/Burmese_graphclust_model5_heavy.txt text !eol zos-working-tree-encoding=UTF-8
107+
icu4c/source/test/testdata/Burmese_graphclust_model5_heavy_Test.txt text !eol zos-working-tree-encoding=UTF-8
108+
icu4c/source/test/testdata/ConverterSelectorTestUTF8.txt text !eol zos-working-tree-encoding=UTF-8
109+
icu4c/source/test/testdata/IdnaTestV2.txt text !eol zos-working-tree-encoding=UTF-8
110+
icu4c/source/test/testdata/NumberFormatTestCases.txt text !eol zos-working-tree-encoding=UTF-8
111+
icu4c/source/test/testdata/Thai_codepoints_exclusive_model5_heavy.txt text !eol zos-working-tree-encoding=UTF-8
112+
icu4c/source/test/testdata/Thai_codepoints_exclusive_model5_heavy_Test.txt text !eol zos-working-tree-encoding=UTF-8
113+
icu4c/source/test/testdata/Thai_graphclust_model4_heavy.txt text !eol zos-working-tree-encoding=UTF-8
114+
icu4c/source/test/testdata/Thai_graphclust_model4_heavy_Test.txt text !eol zos-working-tree-encoding=UTF-8
115+
icu4c/source/test/testdata/casing.txt text !eol zos-working-tree-encoding=UTF-8
116+
icu4c/source/test/testdata/collationtest.txt text !eol zos-working-tree-encoding=UTF-8
117+
icu4c/source/test/testdata/dcfmtest.txt text !eol zos-working-tree-encoding=UTF-8
118+
icu4c/source/test/testdata/emoji-test.txt text !eol zos-working-tree-encoding=UTF-8
119+
icu4c/source/test/testdata/format.txt text !eol zos-working-tree-encoding=UTF-8
120+
icu4c/source/test/testdata/idna_conf.txt text !eol zos-working-tree-encoding=UTF-8
121+
icu4c/source/test/testdata/metaZones.txt text !eol zos-working-tree-encoding=UTF-8
122+
icu4c/source/test/testdata/numberformattestspecification.txt text !eol zos-working-tree-encoding=UTF-8
123+
icu4c/source/test/testdata/numberpermutationtest.txt text !eol zos-working-tree-encoding=UTF-8
124+
icu4c/source/test/testdata/rbbitst.txt text !eol zos-working-tree-encoding=UTF-8
125+
icu4c/source/test/testdata/regextst.txt text !eol zos-working-tree-encoding=UTF-8
126+
icu4c/source/test/testdata/riwords.txt text !eol zos-working-tree-encoding=UTF-8
127+
icu4c/source/test/testdata/te_IN.txt text !eol zos-working-tree-encoding=UTF-8
128+
icu4c/source/test/testdata/timezoneTypes.txt text !eol zos-working-tree-encoding=UTF-8
129+
icu4c/source/test/testdata/windowsZones.txt text !eol zos-working-tree-encoding=UTF-8

docs/userguide/icu4c/build.md

Lines changed: 29 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -368,55 +368,54 @@ Some platforms use package management tools to control the installation and unin
368368
369369
## How To Build And Install On z/OS (OS/390)
370370
371-
You can install ICU on z/OS or OS/390 (the previous name of z/OS), but IBM tests only the z/OS installation. You install ICU in a z/OS UNIX system services file system such as HFS or zFS. On this platform, it is important that you understand a few details:
371+
You can install ICU on z/OS or OS/390 (the previous name of z/OS), but IBM tests only the z/OS installation. You install ICU in a z/OS UNIX System Services (z/OS UNIX) file system such as HFS or zFS. On this platform, it is important that you understand a few details:
372372
373373
* The makedep and GNU make tools are required for building ICU. If it is not already installed on your system, it is available at the [z/OS UNIX - Tools and Toys](http://www-03.ibm.com/servers/eserver/zseries/zos/unix/bpxa1toy.html) site. The PATH environment variable should be updated to contain the location of this executable prior to build. Failure to add these tools to your PATH will cause ICU build failures or cause pkgdata to fail to run.
374-
* Since USS does not support using the mmap() function over NFS, it is recommended that you build ICU on a local filesystem. Once ICU has been built, you should not have this problem while using ICU when the data library has been built as a shared library, which is this is the default setting.
375-
* Encoding considerations: The source code assumes that it is compiled with codepage ibm-1047 (to be exact, the UNIX System Services variant of it). The pax command converts all of the source code files from ASCII to codepage ibm-1047 (USS) EBCDIC. However, some files are binary files and must not be converted, or must be converted back to their original state. You can use the [unpax-icu.sh](https://github.com/unicode-org/icu/blob/main/icu4c/as_is/os390/unpax-icu.sh) script to do this for you automatically. It will unpackage the tar file and convert all the necessary files for you automatically.
376-
* z/OS supports both native S/390 hexadecimal floating point and (with OS/390 2.6 and later) IEEE 754 binary floating point. This is a compile time option. Applications built with IEEE should use ICU DLLs that are built with IEEE (and vice versa). The environment variable IEEE390=0 will cause the z/OS version of ICU to be built without IEEE floating point support and use the native hexadecimal floating point. By default ICU is built with IEEE 754 support. Native floating point support is sufficient for codepage conversion, resource bundle and UnicodeString operations, but the Format APIs require IEEE binary floating point.
377-
* z/OS introduced the concept of Extra Performance Linkage (XPLINK) to bring performance improvement opportunities to call-intensive C and C++ applications such as ICU. XPLINK is enabled on a DLL-by-DLL basis, so if you are considering using XPLINK in your application that uses ICU, you should consider building the XPLINK-enabled version of ICU. You need to set ICU's environment variable `OS390_XPLINK=1` prior to invoking the make process to produce binaries that are enabled for XPLINK. The XPLINK option, which is available for z/OS 1.2 and later, requires the PTF PQ69418 to build XPLINK enabled binaries.
378-
* ICU requires XPLINK for the icuio library. If you want to use the rest of ICU without XPLINK, then you must use the --disable-icuio configure option.
379-
* The latest versions of z/OS use [XPLINK version (C128) of the C++ standard library](https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.cbcux01/oebind6.htm) by default. You may see [an error](https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.cbcux01/oebind5.htm) when running with XPLINK disabled. To avoid this error, set the following environment variable or similar:
374+
* Since z/OS UNIX does not support using the mmap() function over NFS, it is recommended that you build ICU on a local filesystem. Once ICU has been built, you should not have this problem while using ICU when the data library has been built as a shared library, which is this is the default setting.
375+
* Encoding considerations: The source code assumes that it is compiled with codepage ibm-1047 (to be exact, the z/OS UNIX variant of it). The pax command converts all of the source code files from ASCII to codepage ibm-1047 (z/OS UNIX) EBCDIC. However, some files are binary files and must not be converted, or must be converted back to their original state. You can use the [unpax-icu.sh](https://github.com/unicode-org/icu/blob/main/icu4c/as_is/os390/unpax-icu.sh) script to do this for you automatically. It will unpackage the tar file and convert all the necessary files for you automatically.
376+
* z/OS supports both native S/390 hexadecimal floating point and (with OS/390 2.6 and later) IEEE 754 binary floating point. This is a compile time option. Applications built with IEEE should use ICU DLLs that are built with IEEE (and vice versa). The environment variable ICU_IS_NOT_IEEE754=1 will disable IEEE floating point support on z/OS and use the native hexadecimal floating point. By default, ICU is built with IEEE 754 support. Native hexadecimal floating point support is sufficient for codepage conversion, resource bundle and UnicodeString operations, but the Format APIs require IEEE binary floating point.
377+
* Use IBM Open XL C/C++ 2.1 for z/OS (or later) for z/OS build of ICU library. IBM XL C/C++ for z/OS does not support C++17 and can only build up to ICU v58. Target architecture can be controlled with TARGET_ICU_ARCH enviromental variable, default is arch10.
380378
381-
```
382-
export _CXX_PSYSIX="CEE.SCEELIB(C128N)":"CBC.SCLBSID(IOSTREAM,COMPLEX)"
383-
```
384-
385-
* When building ICU data, the heap size may need to be increased with the following environment variable:
379+
When building ICU data, you might need to set the following environment variables:
386380
387381
```
388-
export _CEE_RUNOPTS="HEAPPOOLS(ON),HEAP(4M,1M,ANY,FREE,0K,4080)"
382+
export _ENCODE_FILE_NEW=IBM-1047
383+
export _ENCODE_FILE_EXISTING=IBM-1047
384+
export _CEE_RUNOPTS="FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)"
385+
export _BPXK_AUTOCVT=ON
386+
export _TAG_REDIR_ERR=txt
387+
export _TAG_REDIR_IN=txt
388+
export _TAG_REDIR_OUT=txt
389389
```
390390
391-
* The rest of the instructions for building and testing ICU on z/OS with UNIX System Services are the same as the [How To Build And Install On UNIX](#how-to-build-and-install-on-unix) section.
392-
393-
### z/OS (Batch/PDS) support outside the UNIX system services environment
391+
The rest of the instructions for building and testing ICU on z/OS UNIX are the same as the [How To Build And Install On UNIX](#how-to-build-and-install-on-unix) section.
394392
395-
By default, ICU builds its libraries into the UNIX file system (HFS). In addition, there is a z/OS specific environment variable (OS390BATCH) to build some libraries into the z/OS native file system. This is useful, for example, when your application is externalized via Job Control Language (JCL).
393+
### z/OS (Batch/PDS) support outside the z/OS UNIX environment
396394
397-
The OS390BATCH environment variable enables non-UNIX support including the batch environment. When OS390BATCH is set, the libicui18n_XX_.dll, libicuuc_XX_.dll, and libicudt_XX_e.dll binaries are built into data sets (the native file system). Turning on OS390BATCH does not turn off the normal z/OS UNIX build. This means that the z/OS UNIX (HFS) DLLs will always be created.
395+
ICU on z/OS builds its libraries into the z/OS UNIX file system (HFS). In addition, some libraries are built with batch-ready names. The default batch-ready ICU naming convention is LICU as prefix, 2 characters for version of ICU library, and 2 characters for specific ICU library name (see examples below). Use the following environmental variables to control z/OS batch-ready build of ICU:
398396
399-
Two additional environment variables indicate the names of the z/OS data sets to use. The LOADMOD environment variable identifies the name of the data set that contains the dynamic link libraries (DLLs) and the LOADEXP environment variable identifies the name of the data set that contains the side decks, which are normally the files with the .x suffix in the UNIX file system.
397+
* ICU_PDS_NAME_PREFIX sets the library name prefix.
398+
* ICU_PDS_NAME_SUFFIX sets the library name suffix. If not set, the suffix is empty by default.
399+
* ICU_PDS_NAME overrides ICU_PDS_NAME_PREFIX and two-character ICU library version. The two-character code for the specific ICU library will be appended.
400+
* ICU_PLUGINS_DD indicates the ICU plug-ins location. A value of 1 forces the ICU to load plug-ins from //DD:ICUPLUG. ICU_PLUGINS_DD is not set by default, which means the ICU reads plug-ins from an HFS directory.
400401
401-
A data set is roughly equivalent to a UNIX or Windows file. For most kinds of data sets the operating system maintains record boundaries. UNIX and Windows files are byte streams. Two kinds of data sets are PDS and PDSE. Each data set of these two types contains a directory. It is like a UNIX directory. Each "file" is called a "member". Each member name is limited to eight bytes, normally EBCDIC.
402-
403-
Here is an example of some environment variables that you can set prior to building ICU:
402+
Detailed schema of batch-ready naming:
404403
405404
```
406-
OS390BATCH=1
407-
LOADMOD=_USER_.ICU.LOAD
408-
LOADEXP=_USER_.ICU.EXP
405+
{ICU_PDS_NAME_PREFIX}{two-character ICU library version}{two-character ICU library code}{ICU_PDS_NAME_SUFFIX}
406+
{ ICU_PDS_NAME }
409407
```
410408
411-
The PDS member names for the DLL file names are as follows:
409+
Default batch-ready library subset names mapped to original UNIX names:
412410
413411
```
414-
IXMI_XX_IN --> libicui18n_XX_.dll
415-
IXMI_XX_UC --> libicuuc_XX_.dll
416-
IXMI_XX_DA --> libicudt_XX_e.dll
412+
LICU76DA - libicudata.so
413+
LICU76IN - libicui18n.so
414+
LICU76IO - libicuio.so
415+
LICU76UC - libicuuc.so
417416
```
418417
419-
You should point the LOADMOD environment variable at a partitioned data set extended (PDSE) and point the LOADEXP environment variable at a partitioned data set (PDS). The PDSE can be allocated with the following attributes:
418+
To use ICU from batch, copy the ICU libraries to a PDSE data set with the following attributes:
420419
421420
```
422421
Data Set Name . . . : USER.ICU.LOAD
@@ -434,24 +433,6 @@ Secondary cylinders : 5
434433
Data set name type : LIBRARY
435434
```
436435
437-
The PDS can be allocated with the following attributes:
438-
439-
```
440-
Data Set Name . . . : USER.ICU.EXP
441-
Management class. . : **None**
442-
Storage class . . . : BASE
443-
Volume serial . . . : TSO007
444-
Device type . . . . : 3390
445-
Data class. . . . . : **None**
446-
Organization . . . : PO
447-
Record format . . . : FB
448-
Record length . . . : 80
449-
Block size . . . . : 3200
450-
1st extent cylinders: 3
451-
Secondary cylinders : 3
452-
Data set name type : PDS
453-
```
454-
455436
## How To Build And Install On The IBM i Family (IBM i, i5/OS OS/400)
456437
457438
Before you start building ICU, ICU requires the following:

icu4c/source/common/Makefile.in

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -44,10 +44,10 @@ ifeq ($(ENABLE_SO_VERSION_DATA),1)
4444
SO_VERSION_DATA = common.res
4545
endif
4646

47-
ifeq ($(OS390BATCH),1)
47+
ifeq ($(BUILD_HOST_ICU),OS390)
4848
BATCH_TARGET = $(BATCH_COMMON_TARGET)
4949
BATCH_LIBS = $(BATCH_LIBICUDT) -lm
50-
endif # OS390BATCH
50+
endif
5151

5252
endif # ENABLE_SHARED
5353

@@ -58,10 +58,6 @@ DYNAMICCFLAGS = $(SHAREDLIBCFLAGS)
5858
DYNAMICCXXFLAGS = $(SHAREDLIBCXXFLAGS)
5959
CFLAGS += $(LIBCFLAGS)
6060
CXXFLAGS += $(LIBCXXFLAGS)
61-
ifeq ($(OS390BATCH),1)
62-
CFLAGS += -WI
63-
CXXFLAGS += -WI
64-
endif
6561

6662
CPPFLAGS += -I$(srcdir) $(LIBCPPFLAGS) $(CPPFLAGSICUUC)
6763
# we want DEFS here
@@ -191,10 +187,10 @@ ifneq ($(wildcard $(libdir)/$(MIDDLE_SO_TARGET)),)
191187
endif
192188
endif
193189

194-
ifeq ($(OS390BATCH),1)
190+
ifeq ($(BUILD_HOST_ICU),OS390)
195191
$(BATCH_TARGET):$(OBJECTS)
196-
$(SHLIB.cc) $(LD_SONAME) $(OUTOPT)$@ $^ $(BATCH_LIBS)
197-
endif # OS390BATCH
192+
$(SHLIB.cc) $(LD_SONAME) -Wl,-x$@.x $(OUTOPT)$@ $^ $(BATCH_LIBS)
193+
endif
198194
endif # ENABLE_SHARED
199195

200196
ifeq (,$(MAKECMDGOALS))

0 commit comments

Comments
 (0)