mirror of
https://sourceware.org/git/glibc.git
synced 2025-12-24 17:51:17 +03:00
* charmaps/BIG5: Add mapping for <U20AC> back.
Patch by Tung-Han Hsieh <thhsieh@twcpro.phys.ntu.edu.tw>.
This commit is contained in:
19
FAQ
19
FAQ
@@ -114,6 +114,8 @@ please let me know.
|
||||
in /etc/nsswitch.conf?
|
||||
2.32. What has do be done when upgrading to glibc 2.2?
|
||||
2.33. The makefiles want to do a CVS commit.
|
||||
2.34. When compiling C++ programs, I get a compilation error in streambuf.h.
|
||||
2.35. When recompiling GCC, I get compilation errors in libio.
|
||||
|
||||
3. Source and binary incompatibilities, and what to do about them
|
||||
|
||||
@@ -1249,6 +1251,22 @@ time. This is what you always have to use if you are checking sources
|
||||
directly out of the public CVS repository or you have your own private
|
||||
repository.
|
||||
|
||||
|
||||
2.34. When compiling C++ programs, I get a compilation error in streambuf.h.
|
||||
|
||||
{BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to
|
||||
apply a patch to the include files in /usr/include/g++, because the fpos_t
|
||||
type has changed in glibc 2.2. The patch is at
|
||||
http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
||||
|
||||
|
||||
2.35. When recompiling GCC, I get compilation errors in libio.
|
||||
|
||||
{BH} You are trying to recompile gcc 2.95.2? After upgrading to glibc 2.2,
|
||||
you need to apply a patch to the gcc sources, because the fpos_t type and
|
||||
a few libio internals have changed in glibc 2.2. T he patch is at
|
||||
http://clisp.cons.org/~haible/gcc-glibc-2.2-compat.diff
|
||||
|
||||
|
||||
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
|
||||
|
||||
@@ -1830,6 +1848,7 @@ Answers were given by:
|
||||
{HJ} H.J. Lu, <hjl@gnu.org>
|
||||
{CG} Cristian Gafton, <gafton@redhat.com>
|
||||
{AO} Alexandre Oliva, <oliva@lsd.ic.unicamp.br>
|
||||
{BH} Bruno Haible, <haible@clisp.cons.org>
|
||||
|
||||
Local Variables:
|
||||
mode:outline
|
||||
|
||||
Reference in New Issue
Block a user