[Bug libstdc++/11170] bug in ctype_inline.h header file (undefined __istype will break compilation)

["ronald at landheer dot com" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11170



------- Additional Comments From ronald@landheer.com  2003-06-13 08:30 -------
Subject: Re:  bug in ctype_inline.h header file (undefined
 __istype will break compilation)

Most of your reply has more to do with PR 11171 than with PR 11170 - is 
that intentional? (PR 11171 notes that the wrong headers are being pulled 
in; PR 11170 is about the FreeBSD headers and __istype)

As for:
> Ah, BTW, you thought it was an error to use __istype before checking it
> to guard the use of another entity called __maskrune.  That is not-a-bug
> (you will have to study the *full* history of /usr/include/ctype.h on
> freebsd to understand why).
I'd love to study the full history of the FreeBSD headers, but I don't 
currently have the time for that. If you say it's not a bug, that's good 
enough for me. (but in that case, shouldn't the PR be resolved as 
"invalid"?)

thx

rlc


On 12 Jun 2003, rittle@latour.rsch.comm.mot.com wrote:
> This is not a supported configuration at the moment (this is true for
> many "UNIX" cross-targets within libstdc++-v3 AFAIK).  I have no
> opinion on whether the above should or should not be supported but we
> will review any patches posted to the libstdc++ list to improve that
> situation.  For one thing, AFAIK, the libstdc++-v3 configuration
> method looks at target triple without regard to presence of
> --with-newlib to decide which configuration files to select.  Those
> selected files clearly use knowledge of the target OS and expect
> system headers to be present not newlib headers.
> 
> I.e. if there is a bug, then I suggest it is not in:
> libstdc++-v3/config/os/bsd/freebsd/ctype_inline.h
> rather it is in the selection process in:
> libstdc++-v3/configure* (which should be selecting
> libstdc++-v3/config/os/newlib/ctype_inline.h et al. in the presence
> of --with-newlib).
> 
> Ah, BTW, you thought it was an error to use __istype before checking
> it to guard the use of another entity called __maskrune.  That is
> not-a-bug (you will have to study the *full* history of
> /usr/include/ctype.h on freebsd to understand why).
> 
> Regards,
> Loren (with both libstdc++-v3 and freebsd maintainer hat on)
> 
> 
> 
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>