stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Commented: (STDCXX-23) [Cygwin] messages.cpp needs catopen, catgets etc
Date Wed, 14 Sep 2005 16:09:56 GMT
    [ ] 

Martin Sebor commented on STDCXX-23:

At the very least, we need to avoid using the functions if they are not defined on Cygwin
so that the library links. This should be done the same way all other libc functions are configured.
I.e., there ought to be a pair of config macros: _RWSTD_NO_CATOPEN and _RWSTD_NO_CATOPEN_IN_LIBC,
the former corresponding to a declaration of the function in <nl_types.h> and the latter
that corresponds to the definition in libc (or libcatgets). The tricky part will be handling
the declaration-with-no-definition type of a configuration result. We currently assume that
a declaration implies a definition (see etc/config/src/

A robust solution should probably involve letting users decide whether to use catopen and
catgets (assuming it's installed) or the Windows native messaging facility. I would probably
choose catopen as the default (if it's installed) and let users #define a config macro to
use the Windows stuff instead.

> [Cygwin] messages.cpp needs catopen, catgets etc
> ------------------------------------------------
>          Key: STDCXX-23
>          URL:
>      Project: STDCXX
>         Type: Bug
>   Components: 22. Localization
>     Versions: 4.1.2
>  Environment: Cygwin
>     Reporter: Lance Diduck
>      Fix For: 4.1.3

> shows that libc does not have
catopen, catgets, etc. Library compiles but does not link. 
> A recent thread (Jun 2005) discusses adding "libcatgets"

> There are at least these approaches:
> 1. Implement the missing stuff ourselves
> 2. Implement messages.cpp in terms of the underlying Windows messaging subsystem (i.e.
FormatMessage, etc)
> 3. Require libcatgets , change build 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message