diff options
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 22 |
1 files changed, 22 insertions, 0 deletions
@@ -100,6 +100,8 @@ please let me know. 2.27. What needs to be recompiled when upgrading from glibc 2.0 to glibc 2.1? 2.28. Why is extracting files via tar so slow? +2.29. Compiling programs I get parse errors in libio.h (e.g. "parse error + before `_IO_seekoff'"). How should I fix this? 3. Source and binary incompatibilities, and what to do about them @@ -1064,6 +1066,26 @@ solutions: - if you need NIS/NIS+, use the Name Service Cache Daemon nscd that comes with glibc 2.1. + +2.29. 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. + . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |