1
0
mirror of https://sourceware.org/git/glibc.git synced 2025-09-01 05:02:03 +03:00

Regenerated: /usr/unsupported/bin/perl scripts/gen-FAQ.pl FAQ.in

This commit is contained in:
Ulrich Drepper
1999-02-27 10:59:20 +00:00
parent 521c0ad579
commit 2ee511d907
2 changed files with 42 additions and 0 deletions

20
FAQ.in
View File

@@ -876,6 +876,26 @@ solutions:
- if you need NIS/NIS+, use the Name Service Cache Daemon nscd that comes
with glibc 2.1.
?? Compiling programs I get parse errors in libio.h (e.g. "parse error
before `_IO_seekoff'"). How should I fix this?
{AJ} You might get the following errors when upgrading to glibc 2.1:
In file included from /usr/include/stdio.h:57,
from ...
/usr/include/libio.h:335: parse error before `_IO_seekoff'
/usr/include/libio.h:335: parse error before `_G_off64_t'
/usr/include/libio.h:336: parse error before `_IO_seekpos'
/usr/include/libio.h:336: parse error before `_G_fpos64_t'
The problem is a wrong _G_config.h file in your include path. The
_G_config.h file that comes with glibc 2.1 should be used and not one from
libc5 or from a compiler directory. To check which _G_config.h file the
compiler uses, compile your program with `gcc -E ...|grep G_config.h' and
remove that file. Your compiler should pick up the file that has been
installed by glibc 2.1 in your include directory.
? Source and binary incompatibilities, and what to do about them
?? I expect GNU libc to be 100% source code compatible with