[wx-dev] Compilation failures on Solaris 9

[Stefan.Neis at t-online.de]

       Hi,

> So> Solaris 9's gtknotebook.h really has this prototype:
> 
> Which GTK+ version do you have on this system? I.e. what does
> "pkg-config --modversion gtk+-2.0" output?

2.1.0 (I.e. the one it was delivered with, AFAIK). BTW, Solaris 10
seems to have 2.4.9.

> so I've modified the code to just use it.

Thanks, although looking at the version number, I now suppose
this build isn't going to work anyway ...

BTW, I think it might be a good idea to do buildbot logs with
"make --keep-going",  so you don't have to go through build errors
one by one. However, that probably should be a general policy,
otherwise it's just going to be confusing...
 
> You can define __EXTENSIONS__ under Solaris to get non-standard but
> also not conflicting with standards declarations from the standard
> headers, see standards(5). So we could presumably do it in configure.

Unfortunately, that doesn't work - I didn't think of gcc's "fixincludes"
script.
The function is/should be  there in /usr/include/stdio.h (if
__EXTENSIONS__
is defined), but not in the modified headers that gcc is using ... :-(

> Well, yes, we assumed vsscanf(), being ANSI C, would be available
> everywhere. Looks like we need to add a configure test for it (taking
> care to use C++ for the test).

ATM, I've just added a declaration of vsscanf to wxcrt to see if that
way
also the linker is going to work ...

> Normally it should be as simple as
> adding WX_CHECK_FUNCS(vsscanf) to "Check for functions" section of
> configure and using HAVE_VSSCANF instead of current HAVE_NO_VSSCANF
> whose definition in the beginning of wx/wxcrt.h should be replaced
> with HAVE_VSSCANF one. Could you please check if this works?

I wonder, if we really want to do this, or if we want an extra case to
handle
the missing declaration (and still use the system function if it is
available in
this case)...

         Regards,
                Stefan