Compiler warnings from HP-UX's C++

[Richard Lloyd]

When compiling FileZilla Client 3.1.6 in HP-UX 11.X, there are a fair number of fussy compiler warnings from HP's C++ compiler (plus a link failure that I've documented in a separate bug). I've attached the output from the build so that you can look through the warnings and decide if any of them need fixing (the trailing comma in an enum warning is an easy fix). The output is from a PA-RISC HP-UX 11.11 machine using HP's latest C++ compiler (A.03.85) and is after I've fixed any build issues mentioned in the recent bugs I filed for HP-UX 11.X.

[Richard Lloyd]

gmake build of FileZilla Client 3.1.6 using HP's C++, wxGTK 2.8.9 and HP-UX 11.11

[Tim Kosse]

Many of these warnings are just false positives I think.

Also, you want to compile wxWidgets with --enable-unicode

I've fixed the legitimate warnings.

[Richard Lloyd]

Unfortunately, wxGTK 2.8.9's unicode support is incomplete, especially when compiling with HP-UX 11.11. In wxGTK 2.8.9, src/common/wxchar.cpp has both unimplemented functions (wxscanf() at line 1315 and vfwscanf() at line 1339) and partially/incorrectly coded functions (vswscanf() at line 1322, which also has a bad type for the first parameter of the vsscanf() call at line 1336). Also, there is an incorrect assumption that if vwprintf() is present (it is in HP-UX 11.11/23/31) then all the other unicode functions are present (not the case for HP-UX 11.11 or 11.23).

Also, include/wx/wxchar.h hits the #error at line 694 with HP-UX 11.11 if --enable-unicode is supplied, because WCHAR_TYPE (with underscores, but that messes up this bug report formatting) isn't defined by HP-UX's header files. An easy fix is to add defined(hpux) (with 2 leading underscores before hpux and 2 vertical bars before the defined()) to the check in line 524. I guess these issues will have to be reported to the wxGTK folks and hopefully they'll roll them into the next release.