mbchar.h
Kaveh R. Ghazi
ghazi@caip.rutgers.edu
Tue Oct 5 09:16:00 GMT 1999
> From: Jeffrey A Law <law@cygnus.com>
>
> I guess nobody's been using multi-byte characters recently -- GCC
> wouldn't even build with mbchars because of a missing #endif..
>
> * mbchar.h: Add missing #endif.
Okay, I gave it a try. I noticed one oddity. The entry for
--enable-c-mbchar looks like this:
> AC_ARG_ENABLE(c-mbchar,
> [ --enable-c-mbchar Enable multibyte characters for C and
> C++.],
> if [[[ x$enable_c_mbchar != xno ]]]; then
> extra_c_flags=-DMULTIBYTE_CHARS=1
> fi)
However there is an entry for --enable-c-cpplib which uses the same
variable extra_c_flags:
> AC_ARG_ENABLE(c-cpplib,
> [ --enable-c-cpplib link cpplib directly into C and C++
> compilers
> (EXPERIMENTAL) (implies --enable-cpplib).],
> if test x$enable_c_cpplib != xno; then
> extra_c_objs="${extra_c_objs} libcpp.a"
> extra_cxx_objs="${extra_cxx_objs} ../libcpp.a"
> extra_c_flags="${extra_c_flags} -DUSE_CPPLIB=1"
> cpp_main=cppmain
> fi)
Note that the mbchar entry overwrites the extra_c_flags variable while
the cpplib one appends to it. Is this intentional (possibly due to
lack of mbchar support in cpplib?)
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions
More information about the Gcc-patches
mailing list