Print this page
11461 should use a native link-editor during the build
11463 SUNWonld has passed its use-by date
11464 cmd/sgs/tools should contain tools, not common code
11465 sgsmsg should be built with the rest of the build tools
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/cmd/sgs/tools/man/chkmsg.1l
+++ new/usr/src/cmd/sgs/tools/chkmsg.1l
1 -.\" ident "%Z%%M% %I% %E% SMI"
2 1 .\" Copyright 2005 Sun Microsystems, Inc. All rights reserved.
3 2 .\" Use is subject to license terms.
4 3 .\"
5 4 .\" CDDL HEADER START
6 5 .\"
7 6 .\" The contents of this file are subject to the terms of the
8 7 .\" Common Development and Distribution License, Version 1.0 only
9 8 .\" (the "License"). You may not use this file except in compliance
10 9 .\" with the License.
11 10 .\"
12 11 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
13 12 .\" or http://www.opensolaris.org/os/licensing.
14 13 .\" See the License for the specific language governing permissions
15 14 .\" and limitations under the License.
|
↓ open down ↓ |
4 lines elided |
↑ open up ↑ |
16 15 .\"
17 16 .\" When distributing Covered Code, include this CDDL HEADER in each
18 17 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
19 18 .\" If applicable, add the following below this CDDL HEADER, with the
20 19 .\" fields enclosed by brackets "[]" replaced with your own identifying
21 20 .\" information: Portions Copyright [yyyy] [name of copyright owner]
22 21 .\"
23 22 .\" CDDL HEADER END
24 23 .\"
25 24 .if n .tr \--
26 -.TH chkmsg 1l "5 Apr 1997"
25 +.TH chkmsg 1l "Apr 5, 1997"
27 26 .SH NAME
28 -chkmsg \- cross check messages
27 +chkmsg \- cross check messages
29 28 .SH SYNOPSIS
30 29 .B chkmsg
31 30 .BI [ -64 ]
32 31 .BI file
33 32 .BI source_files ...
34 33 .SH AVAILABILITY
35 34 Internal to the linker group
36 35 .SH DESCRIPTION
37 36 chkmsg checks the message identifiers defined in the input file
38 37 and the message identifyer used in the input source_files. The input
39 38 file is the input file which is used by the sgsmsg command.
40 39 .P
41 -The chkmsg command reads the input file and
40 +The chkmsg command reads the input file and
42 41 generates two sets of message identifiers.
43 42 The first set is
44 43 the identifiers defined in between the _START_ and _END_ key words.
45 44 These identifiers are intended to be referenced by MSG_INTL().
46 45 This set is named as MSG_INTL_FROM_INPUT.
47 46 .P
48 47 The other set is
49 48 the identifiers defined after the _END_ key words.
50 49 These identifiers are intended to be referenced by MSG_ORIG().
51 50 This set is named as MSG_ORIG_FROM_INPUT.
52 51 .P
53 52 The chkmsg command reads the specified input source_files and
54 53 generates two sets of message identifiers. The first set is
55 54 the message identifiers referenced by MSG_INTL() macro.
56 55 This set is named as MSG_INTL_FROM_SRC.
57 56 .P
58 57 The other set is the message identifiers referenced by the
59 58 MSG_ORIG() macro.
60 59 This set is named as MSG_ORIG_FROM_SRC.
61 60 .P
62 61 The chkmsg command compares MSG_INTL_FROM_SRC and MSG_INTL_FROM_INPUT.
63 62 If these two sets are different, the command gives the warning
64 63 message and print the identifiers which are different.
65 64 .P
66 65 The chkmsg command compares MSG_ORIG_FROM_SRC and MSG_ORIG_FROM_INPUT.
67 66 If these two sets are different, the command gives the warning
68 67 message and print the identifiers which are different.
69 68 .P
70 69 The identifiers in MSG_INTL_FROM_SRC and MSG_ORIG_FROM_SRC are
71 70 extracted from the source files only if they are
72 71 directly passed to MSG_INTL() or MSG_ORIG(). Therefore, for example:
73 72 .RS
74 73 .nf
75 74 .ft 3
|
↓ open down ↓ |
24 lines elided |
↑ open up ↑ |
76 75 char *msg;
77 76 |
78 77 msg = MSG_ERROR_01;
79 78 |
80 79 printf(MSG_INTL(msg));
81 80 |
82 81 .fi
83 82 .RE
84 83 the identifyer MSG_ERROR_01 will not be included in MSG_INTL_FROM_SRC set.
85 84 .P
86 -There are two key words which can be used in the input file
87 -to control whether the identifier will be extracted into
85 +There are two key words which can be used in the input file
86 +to control whether the identifier will be extracted into
88 87 MSG_{INTL,ORIG}_FROM_ORIG or not. If the identifyer are
89 88 surrounded by _CHKMSG_SKIP_BEGIN_ {sparc,i386}
90 89 and _CHKMSG_SKIP_END_ {sparc,i386}, then
91 90 the identifiers will not be included in the output set.
92 91 The architecture being checked should be specified after
93 92 the key works.
94 93 These key words should be specified in the comment lines.
95 94 For example, the input file could contain:
96 95 .RS
97 96 .nf
98 97 .ft 3
99 98 # _CHKMSG_SKIP_BEGIN_ sparc
100 99 @ MSG_ERROR_01 "This identifier is not defined."
101 100 # _CHKMSG_SKIP_END_ sparc
102 101 .fi
103 102 .RE
104 103 .P
105 104 It is assumed that the message identifier names are composed
106 105 of only upper letters.
|
↓ open down ↓ |
9 lines elided |
↑ open up ↑ |
107 106 .SH OPTIONS
108 107 .TP 12
109 108 .B \-64
110 109 Use a 64-bit version of the machine type (i.e. sparc => sparcv9).
111 110 Note that this option must be specified first on the command line.
112 111 .SH "SEE ALSO"
113 112 .BR gencat (1),
114 113 .BR ld (1),
115 114 .BR msgfmt (1),
116 115 .BR catgets (3C),
117 -.BR gettext (3I).
118 -.BR sgsmsg (1l).
119 -.br
120 -.TZ LLM
116 +.BR gettext (3C).
117 +.BR sgsmsg (1ONBLD).
121 118 .if n .tr \-\-
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX