Closed Bug 198772 Opened 21 years ago Closed 19 years ago

Warning of incompatible data type that will be a future error.

Categories

(Core :: XPCOM, defect)

Other
HP-UX
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: m4341, Assigned: dougt)

References

(Blocks 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 Version 1.3, attempted build under HP-UX with HP compilers/linkers

Building under HP-UX 11.00/32-bit results in the following warning, best
displayed with fixed-width font:

Error (future) 212: "nsNativeCharsetUtils.cpp", line 119 # Argument type 'const
char **' does not match expected parameter type 'char **'.
        res = iconv(converter, ICONV_INPUT(input), inputLeft, output, outputLeft
);
                               ^^^^^^^^^^^

Warning:        1 future errors were detected and ignored. Add a '+p' option to
detect and fix them before they become fatal errors in a future release. Behavio
r of this ill-formed program is not guaranteed to match that of a well-formed pr
ogram


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
-> xpcom
Assignee: seawood → dougt
Component: Build Config → XPCOM
QA Contact: granrose → scc
OS: other → HP-UX
Blocks: buildwarning
MXR: nsNativeCharsetUtils.cpp | 1.18 |
{
 99 #include <iconv.h>    // iconv_open, iconv, iconv_close

102 #if defined(HAVE_ICONV_WITH_CONST_INPUT)
103 #define ICONV_INPUT(x) (x)
104 #else
105 #define ICONV_INPUT(x) ((char **)x)
106 #endif

125     res = iconv(converter, ICONV_INPUT(input), inputLeft, output, outputLeft);
}

Reporter:
Could you check (on your HP-UX)
1) What the |icon(...)| declaration is ?
2) If |HAVE_ICONV_WITH_CONST_INPUT| is defined or not ?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
R.WontFix: no answer to comment 2, no apparent interest :-/
URL: N/A
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.