]>
Commit | Line | Data |
---|---|---|
61952351 UD |
1 | Frequently Asked Questions about the GNU C Library |
2 | ||
f12944ec UD |
3 | This document tries to answer questions a user might have when installing |
4 | and using glibc. Please make sure you read this before sending questions or | |
5 | bug reports to the maintainers. | |
61952351 | 6 | |
f12944ec | 7 | The GNU C library is very complex. The installation process has not been |
fdacb17d | 8 | completely automated; there are too many variables. You can do substantial |
f12944ec UD |
9 | damage to your system by installing the library incorrectly. Make sure you |
10 | understand what you are undertaking before you begin. | |
61952351 UD |
11 | |
12 | If you have any questions you think should be answered in this document, | |
13 | please let me know. | |
14 | ||
15 | --drepper@cygnus.com | |
16 | \f | |
17 | ? Compiling glibc | |
18 | ||
19 | ?? What systems does the GNU C Library run on? | |
20 | ||
f12944ec UD |
21 | {UD} This is difficult to answer. The file `README' lists the architectures |
22 | GNU libc was known to run on *at some time*. This does not mean that it | |
23 | still can be compiled and run on them now. | |
61952351 | 24 | |
f12944ec UD |
25 | The systems glibc is known to work on as of this release, and most probably |
26 | in the future, are: | |
61952351 UD |
27 | |
28 | *-*-gnu GNU Hurd | |
bd355af0 UD |
29 | i[3456]86-*-linux-gnu Linux-2.x on Intel |
30 | m68k-*-linux-gnu Linux-2.x on Motorola 680x0 | |
2bbc70d5 | 31 | alpha*-*-linux-gnu Linux-2.x on DEC Alpha |
61952351 | 32 | powerpc-*-linux-gnu Linux and MkLinux on PowerPC systems |
bd355af0 UD |
33 | sparc-*-linux-gnu Linux-2.x on SPARC |
34 | sparc64-*-linux-gnu Linux-2.x on UltraSPARC | |
a35cb74d | 35 | arm-*-none ARM standalone systems |
cb0509a8 | 36 | arm-*-linux Linux-2.x on ARM |
a35cb74d | 37 | arm-*-linuxaout Linux-2.x on ARM using a.out binaries |
2bbc70d5 AJ |
38 | mips*-*-linux-gnu Linux-2.x on MIPS |
39 | ia64-*-linux-gnu Linux-2.x on ia64 | |
92ec318f | 40 | s390-*-linux-gnu Linux-2.x on IBM S/390 |
4a5b72ff | 41 | s390x-*-linux-gnu Linux-2.x on IBM S/390 64-bit |
eacde9d0 | 42 | cris-*-linux-gnu Linux-2.4+ on CRIS |
61952351 | 43 | |
f12944ec UD |
44 | Ports to other Linux platforms are in development, and may in fact work |
45 | already, but no one has sent us success reports for them. Currently no | |
46 | ports to other operating systems are underway, although a few people have | |
47 | expressed interest. | |
61952351 | 48 | |
f12944ec UD |
49 | If you have a system not listed above (or in the `README' file) and you are |
50 | really interested in porting it, contact | |
61952351 | 51 | |
b9b49b44 | 52 | <bug-glibc@gnu.org> |
61952351 | 53 | |
57b4b78a | 54 | ??binsize What compiler do I need to build GNU libc? |
61952351 | 55 | |
f12944ec UD |
56 | {UD} You must use GNU CC to compile GNU libc. A lot of extensions of GNU CC |
57 | are used to increase portability and speed. | |
61952351 UD |
58 | |
59 | GNU CC is found, like all other GNU packages, on | |
f12944ec | 60 | |
2eb45444 | 61 | ftp://ftp.gnu.org/pub/gnu |
f12944ec | 62 | |
2eb45444 | 63 | and the many mirror sites. ftp.gnu.org is always overloaded, so try to find |
61952351 UD |
64 | a local mirror first. |
65 | ||
ceb27555 | 66 | You should always try to use the latest official release. Older versions |
f12944ec | 67 | may not have all the features GNU libc requires. The current releases of |
7b32d065 | 68 | gcc (2.95 or newer) should work with the GNU C library (for powerpc see |
92ec318f | 69 | ?powerpc; for ARM see ?arm; for MIPS see ?mips). |
61952351 | 70 | |
6e8afc1c | 71 | Please note that gcc 2.95 and 2.95.x cannot compile glibc on Alpha due to |
a125d9b4 UD |
72 | problems in the complex float support. |
73 | ||
61952351 UD |
74 | ?? When I try to compile glibc I get only error messages. |
75 | What's wrong? | |
76 | ||
b1418d8f | 77 | {UD} You definitely need GNU make to build GNU libc. No other make |
f12944ec | 78 | program has the needed functionality. |
61952351 | 79 | |
2bbc70d5 AJ |
80 | We recommend version GNU make version 3.79 or newer. Older versions have |
81 | bugs and/or are missing features. | |
61952351 | 82 | |
d89e7a96 | 83 | ?? Do I need a special linker or assembler? |
61952351 | 84 | |
d89e7a96 UD |
85 | {ZW} If you want a shared library, you need a linker and assembler that |
86 | understand all the features of ELF, including weak and versioned symbols. | |
87 | The static library can be compiled with less featureful tools, but lacks key | |
88 | features such as NSS. | |
61952351 | 89 | |
b0ed91ae AJ |
90 | For Linux or Hurd, you want binutils 2.10.1 or higher. These are the only |
91 | versions we've tested and found reliable. Other versions may work but we | |
92 | don't recommend them, especially not when C++ is involved. | |
7fd18ea2 | 93 | |
d89e7a96 UD |
94 | Other operating systems may come with system tools that have all the |
95 | necessary features, but this is moot because glibc hasn't been ported to | |
96 | them. | |
61952351 | 97 | |
8619129f | 98 | ??powerpc Which compiler should I use for powerpc? |
4775243a | 99 | |
83f6a990 | 100 | {GK} You want to use at least gcc 2.95 (together with the right versions |
3b019077 | 101 | of all the other tools, of course). See also ?excpt. |
4775243a | 102 | |
cb0509a8 UD |
103 | ??arm Which tools should I use for ARM? |
104 | ||
105 | {PB} You should use egcs 1.1 or a later version. For ELF systems some | |
106 | changes are needed to the compiler; a patch against egcs-1.1.x can be found | |
107 | at: | |
108 | ||
109 | <ftp://ftp.netwinder.org/users/p/philb/egcs-1.1.1pre2-diff-981126> | |
110 | ||
b0ed91ae | 111 | Binutils 2.10.1 or later is also required. |
cb0509a8 | 112 | |
d89e7a96 | 113 | ?? Do I need some more things to compile the GNU C Library? |
61952351 UD |
114 | |
115 | {UD} Yes, there are some more :-). | |
116 | ||
117 | * GNU gettext. This package contains the tools needed to construct | |
118 | `message catalog' files containing translated versions of system | |
2eb45444 | 119 | messages. See ftp://ftp.gnu.org/pub/gnu or better any mirror |
61952351 | 120 | site. (We distribute compiled message catalogs, but they may not be |
c26b4f64 | 121 | updated in patches.) |
61952351 | 122 | |
d89e7a96 UD |
123 | * Some files are built with special tools. E.g., files ending in .gperf |
124 | need a `gperf' program. The GNU version (now available in a separate | |
125 | package, formerly only as part of libg++) is known to work while some | |
126 | vendor versions do not. | |
61952351 UD |
127 | |
128 | You should not need these tools unless you change the source files. | |
129 | ||
d89e7a96 UD |
130 | * Perl 5 is needed if you wish to test an installation of GNU libc |
131 | as the primary C library. | |
bd355af0 | 132 | |
61952351 UD |
133 | * When compiling for Linux, the header files of the Linux kernel must |
134 | be available to the compiler as <linux/*.h> and <asm/*.h>. | |
135 | ||
02228370 | 136 | * lots of disk space (~400MB for i?86-linux; more for RISC platforms). |
61952351 UD |
137 | |
138 | * plenty of time. Compiling just the shared and static libraries for | |
d3d99893 UD |
139 | 35mins on a 2xPIII@550Mhz w/ 512MB RAM. On a 2xUltraSPARC-II@360Mhz |
140 | w/ 1GB RAM it takes about 14 minutes. Multiply this by 1.5 or 2.0 | |
141 | if you build profiling and/or the highly optimized version as well. | |
142 | For Hurd systems times are much higher. | |
61952351 UD |
143 | |
144 | You should avoid compiling in a NFS mounted filesystem. This is | |
145 | very slow. | |
146 | ||
d3d99893 UD |
147 | James Troup <J.J.Troup@comp.brad.ac.uk> reports a compile time for |
148 | an earlier (and smaller!) version of glibc of 45h34m for a full build | |
149 | (shared, static, and profiled) on Atari Falcon (Motorola 68030 @ 16 Mhz, | |
150 | 14 Mb memory) and Jan Barte <yann@plato.uni-paderborn.de> reports | |
151 | 22h48m on Atari TT030 (Motorola 68030 @ 32 Mhz, 34 Mb memory) | |
61952351 | 152 | |
83f6a990 | 153 | A full build of the PowerPC library took 1h on a PowerPC 750@400Mhz w/ |
6e8afc1c | 154 | 64MB of RAM, and about 9h on a 601@60Mhz w/ 72Mb. |
83f6a990 | 155 | |
61952351 UD |
156 | If you have some more measurements let me know. |
157 | ||
d111572f UD |
158 | ?? What version of the Linux kernel headers should be used? |
159 | ||
f12944ec UD |
160 | {AJ,UD} The headers from the most recent Linux kernel should be used. The |
161 | headers used while compiling the GNU C library and the kernel binary used | |
162 | when using the library do not need to match. The GNU C library runs without | |
163 | problems on kernels that are older than the kernel headers used. The other | |
164 | way round (compiling the GNU C library with old kernel headers and running | |
165 | on a recent kernel) does not necessarily work. For example you can't use | |
b1418d8f | 166 | new kernel features if you used old kernel headers to compile the GNU C |
f12944ec UD |
167 | library. |
168 | ||
ceb27555 | 169 | {ZW} Even if you are using a 2.0 kernel on your machine, we recommend you |
440d13e2 UD |
170 | compile GNU libc with 2.2 kernel headers. That way you won't have to |
171 | recompile libc if you ever upgrade to kernel 2.2. To tell libc which | |
ceb27555 | 172 | headers to use, give configure the --with-headers switch |
440d13e2 | 173 | (e.g. --with-headers=/usr/src/linux-2.2.0/include). |
ceb27555 | 174 | |
440d13e2 | 175 | Note that you must configure the 2.2 kernel if you do this, otherwise libc |
62595351 | 176 | will be unable to find <linux/version.h>. Just change the current directory |
440d13e2 | 177 | to the root of the 2.2 tree and do `make include/linux/version.h'. |
ceb27555 | 178 | |
f12944ec UD |
179 | ?? The compiler hangs while building iconvdata modules. What's |
180 | wrong? | |
181 | ||
7b32d065 | 182 | {} Removed. Does not apply anymore. |
d111572f | 183 | |
61952351 UD |
184 | ?? When I run `nm -u libc.so' on the produced library I still |
185 | find unresolved symbols. Can this be ok? | |
186 | ||
f12944ec | 187 | {UD} Yes, this is ok. There can be several kinds of unresolved symbols: |
61952351 UD |
188 | |
189 | * magic symbols automatically generated by the linker. These have names | |
190 | like __start_* and __stop_* | |
191 | ||
192 | * symbols starting with _dl_* come from the dynamic linker | |
193 | ||
61952351 UD |
194 | * weak symbols, which need not be resolved at all (fabs for example) |
195 | ||
196 | Generally, you should make sure you find a real program which produces | |
197 | errors while linking before deciding there is a problem. | |
198 | ||
199 | ??addon What are these `add-ons'? | |
200 | ||
f12944ec | 201 | {UD} To avoid complications with export rules or external source code some |
c0f53cdd UD |
202 | optional parts of the libc are distributed as separate packages, e.g., the |
203 | linuxthreads package. | |
61952351 | 204 | |
f12944ec UD |
205 | To use these packages as part of GNU libc, just unpack the tarfiles in the |
206 | libc source directory and tell the configuration script about them using the | |
207 | --enable-add-ons option. If you give just --enable-add-ons configure tries | |
208 | to find all the add-on packages in your source tree. This may not work. If | |
209 | it doesn't, or if you want to select only a subset of the add-ons, give a | |
210 | comma-separated list of the add-ons to enable: | |
61952351 | 211 | |
c0f53cdd | 212 | configure --enable-add-ons=linuxthreads |
61952351 UD |
213 | |
214 | for example. | |
215 | ||
f12944ec UD |
216 | Add-ons can add features (including entirely new shared libraries), override |
217 | files, provide support for additional architectures, and just about anything | |
218 | else. The existing makefiles do most of the work; only some few stub rules | |
219 | must be written to get everything running. | |
61952351 | 220 | |
5bb17dca | 221 | Most add-ons are tightly coupled to a specific GNU libc version. Please |
c0f53cdd UD |
222 | check that the add-ons work with the GNU libc. For example the linuxthreads |
223 | add-on has the same numbering scheme as the libc and will in general only | |
224 | work with the corresponding libc. | |
225 | ||
226 | {AJ} With glibc 2.2 the crypt add-on and with glibc 2.1 the localedata | |
227 | add-on have been integrated into the normal glibc distribution, crypt and | |
228 | localedata are therefore not anymore add-ons. | |
5bb17dca | 229 | |
61952351 UD |
230 | ?? My XXX kernel emulates a floating-point coprocessor for me. |
231 | Should I enable --with-fp? | |
232 | ||
f12944ec UD |
233 | {ZW} An emulated FPU is just as good as a real one, as far as the C library |
234 | is concerned. You only need to say --without-fp if your machine has no way | |
235 | to execute floating-point instructions. | |
61952351 UD |
236 | |
237 | People who are interested in squeezing the last drop of performance | |
238 | out of their machine may wish to avoid the trap overhead, but this is | |
239 | far more trouble than it's worth: you then have to compile | |
240 | *everything* this way, including the compiler's internal libraries | |
241 | (libgcc.a for GNU C), because the calling conventions change. | |
242 | ||
243 | ?? When compiling GNU libc I get lots of errors saying functions | |
244 | in glibc are duplicated in libgcc. | |
245 | ||
f12944ec UD |
246 | {EY} This is *exactly* the same problem that I was having. The problem was |
247 | due to the fact that configure didn't correctly detect that the linker flag | |
248 | --no-whole-archive was supported in my linker. In my case it was because I | |
249 | had run ./configure with bogus CFLAGS, and the test failed. | |
61952351 | 250 | |
f12944ec UD |
251 | One thing that is particularly annoying about this problem is that once this |
252 | is misdetected, running configure again won't fix it unless you first delete | |
253 | config.cache. | |
61952351 | 254 | |
f12944ec UD |
255 | {UD} Starting with glibc-2.0.3 there should be a better test to avoid some |
256 | problems of this kind. The setting of CFLAGS is checked at the very | |
257 | beginning and if it is not usable `configure' will bark. | |
61952351 | 258 | |
74015205 | 259 | ?? Why do I get messages about missing thread functions when I use |
da2d1bc5 | 260 | librt? I don't even use threads. |
74015205 | 261 | |
da2d1bc5 UD |
262 | {UD} In this case you probably mixed up your installation. librt uses |
263 | threads internally and has implicit references to the thread library. | |
f12944ec UD |
264 | Normally these references are satisfied automatically but if the thread |
265 | library is not in the expected place you must tell the linker where it is. | |
266 | When using GNU ld it works like this: | |
74015205 UD |
267 | |
268 | gcc -o foo foo.c -Wl,-rpath-link=/some/other/dir -lrt | |
269 | ||
f12944ec UD |
270 | The `/some/other/dir' should contain the thread library. `ld' will use the |
271 | given path to find the implicitly referenced library while not disturbing | |
272 | any other link path. | |
74015205 | 273 | |
61952351 UD |
274 | ?? What's the problem with configure --enable-omitfp? |
275 | ||
276 | {AJ} When --enable-omitfp is set the libraries are built without frame | |
fdacb17d | 277 | pointers. Some compilers produce buggy code for this model and therefore we |
f12944ec | 278 | don't advise using it at the moment. |
61952351 | 279 | |
fdacb17d | 280 | If you use --enable-omitfp, you're on your own. If you encounter problems |
f12944ec UD |
281 | with a library that was build this way, we advise you to rebuild the library |
282 | without --enable-omitfp. If the problem vanishes consider tracking the | |
283 | problem down and report it as compiler failure. | |
61952351 | 284 | |
b1418d8f UD |
285 | Since a library built with --enable-omitfp is undebuggable on most systems, |
286 | debuggable libraries are also built - you can use them by appending "_g" to | |
f12944ec | 287 | the library names. |
61952351 | 288 | |
f12944ec UD |
289 | The compilation of these extra libraries and the compiler optimizations slow |
290 | down the build process and need more disk space. | |
61952351 | 291 | |
b1418d8f | 292 | ?? I get failures during `make check'. What should I do? |
b0610668 | 293 | |
b1418d8f UD |
294 | {AJ} The testsuite should compile and run cleanly on your system; every |
295 | failure should be looked into. Depending on the failures, you probably | |
296 | should not install the library at all. | |
b0610668 UD |
297 | |
298 | You should consider using the `glibcbug' script to report the failure, | |
299 | providing as much detail as possible. If you run a test directly, please | |
300 | remember to set up the environment correctly. You want to test the compiled | |
301 | library - and not your installed one. The best way is to copy the exact | |
302 | command line which failed and run the test from the subdirectory for this | |
303 | test in the sources. | |
304 | ||
305 | There are some failures which are not directly related to the GNU libc: | |
b1418d8f UD |
306 | - Some compilers produce buggy code. No compiler gets single precision |
307 | complex numbers correct on Alpha. Otherwise, the egcs 1.1 release should be | |
308 | ok; gcc 2.8.1 might cause some failures; gcc 2.7.2.x is so buggy that | |
309 | explicit checks have been used so that you can't build with it. | |
b0610668 UD |
310 | - The kernel might have bugs. For example on Linux/Alpha 2.0.34 the |
311 | floating point handling has quite a number of bugs and therefore most of | |
440d13e2 | 312 | the test cases in the math subdirectory will fail. Linux 2.2 has |
b1418d8f UD |
313 | fixes for the floating point support on Alpha. The Linux/SPARC kernel has |
314 | also some bugs in the FPU emulation code (as of Linux 2.2.0). | |
d32a4020 UD |
315 | - Other tools might have problems. For example bash 2.03 gives a |
316 | segmentation fault running the tst-rpmatch.sh test script. | |
b0610668 | 317 | |
7fd18ea2 UD |
318 | ?? What is symbol versioning good for? Do I need it? |
319 | ||
320 | {AJ} Symbol versioning solves problems that are related to interface | |
321 | changes. One version of an interface might have been introduced in a | |
322 | previous version of the GNU C library but the interface or the semantics of | |
323 | the function has been changed in the meantime. For binary compatibility | |
324 | with the old library, a newer library needs to still have the old interface | |
b1418d8f | 325 | for old programs. On the other hand, new programs should use the new |
7fd18ea2 | 326 | interface. Symbol versioning is the solution for this problem. The GNU |
b1418d8f UD |
327 | libc version 2.1 uses symbol versioning by default if the installed binutils |
328 | supports it. | |
7fd18ea2 | 329 | |
b1418d8f UD |
330 | We don't advise building without symbol versioning, since you lose binary |
331 | compatibility - forever! The binary compatibility you lose is not only | |
332 | against the previous version of the GNU libc (version 2.0) but also against | |
333 | all future versions. | |
7fd18ea2 | 334 | |
bee1e289 UD |
335 | ?? How can I compile on my fast ix86 machine a working libc for my slow |
336 | i386? After installing libc, programs abort with "Illegal | |
337 | Instruction". | |
338 | ||
339 | {AJ} glibc and gcc might generate some instructions on your machine that | |
340 | aren't available on i386. You've got to tell glibc that you're configuring | |
341 | for i386 with adding i386 as your machine, for example: | |
342 | ||
343 | ../configure --prefix=/usr i386-pc-linux-gnu | |
344 | ||
345 | And you need to tell gcc to only generate i386 code, just add `-mcpu=i386' | |
346 | (just -m386 doesn't work) to your CFLAGS. | |
347 | ||
348 | {UD} This applies not only to the i386. Compiling on a i686 for any older | |
349 | model will also fail if the above methods are not used. | |
350 | ||
b2b28911 UD |
351 | ?? `make' complains about a missing dlfcn/libdl.so when building |
352 | malloc/libmemprof.so. How can I fix this? | |
353 | ||
354 | {AJ} Older make version (<= 3.78.90) have a bug which was hidden by a bug in | |
2bbc70d5 | 355 | glibc (<= 2.1.2). You need to upgrade make to a newer or fixed version. |
b2b28911 UD |
356 | |
357 | After upgrading make, you should remove the file sysd-sorted in your build | |
358 | directory. The problem is that the broken make creates a wrong order for | |
359 | one list in that file. The list has to be recreated with the new make - | |
360 | which happens if you remove the file. | |
361 | ||
362 | You might encounter this bug also in other situations where make scans | |
2bbc70d5 AJ |
363 | directories. I strongly advise to upgrade your make version to 3.79 or |
364 | newer. | |
b2b28911 | 365 | |
bee1e289 | 366 | |
92ec318f AJ |
367 | ??mips Which tools should I use for MIPS? |
368 | ||
4d2adf29 AJ |
369 | {AJ} You should use the current development version of gcc 2.97 from CVS. |
370 | gcc 2.95.x does not work correctly on mips-linux. | |
92ec318f | 371 | |
4d2adf29 AJ |
372 | You need also recent binutils, anything before and including 2.10 will not |
373 | work correctly. Either try the Linux binutils 2.10.0.33 from HJ Lu or the | |
7e5fc672 AJ |
374 | current development version of binutils from CVS. |
375 | ||
376 | Please note that `make check' might fail for a number of the math tests | |
377 | because of problems of the FPU emulation in the Linux kernel (the MIPS FPU | |
378 | doesn't handle all cases and needs help from the kernel). | |
92ec318f AJ |
379 | |
380 | For details check also my page <http://www.suse.de/~aj/glibc-mips.html>. | |
381 | ||
61952351 UD |
382 | ? Installation and configuration issues |
383 | ||
384 | ?? Can I replace the libc on my Linux system with GNU libc? | |
385 | ||
f12944ec UD |
386 | {UD} You cannot replace any existing libc for Linux with GNU libc. It is |
387 | binary incompatible and therefore has a different major version. You can, | |
388 | however, install it alongside your existing libc. | |
61952351 UD |
389 | |
390 | For Linux there are three major libc versions: | |
391 | libc-4 a.out libc | |
392 | libc-5 original ELF libc | |
393 | libc-6 GNU libc | |
394 | ||
f12944ec UD |
395 | You can have any combination of these three installed. For more information |
396 | consult documentation for shared library handling. The Makefiles of GNU | |
397 | libc will automatically generate the needed symbolic links which the linker | |
398 | will use. | |
61952351 UD |
399 | |
400 | ?? How do I configure GNU libc so that the essential libraries | |
401 | like libc.so go into /lib and the other into /usr/lib? | |
402 | ||
403 | {UD,AJ} Like all other GNU packages GNU libc is designed to use a base | |
404 | directory and install all files relative to this. The default is | |
f12944ec UD |
405 | /usr/local, because this is safe (it will not damage the system if installed |
406 | there). If you wish to install GNU libc as the primary C library on your | |
407 | system, set the base directory to /usr (i.e. run configure --prefix=/usr | |
408 | <other_options>). Note that this can damage your system; see ?safety for | |
409 | details. | |
410 | ||
411 | Some systems like Linux have a filesystem standard which makes a difference | |
412 | between essential libraries and others. Essential libraries are placed in | |
413 | /lib because this directory is required to be located on the same disk | |
414 | partition as /. The /usr subtree might be found on another | |
415 | partition/disk. If you configure for Linux with --prefix=/usr, then this | |
416 | will be done automatically. | |
61952351 UD |
417 | |
418 | To install the essential libraries which come with GNU libc in /lib on | |
f12944ec UD |
419 | systems other than Linux one must explicitly request it. Autoconf has no |
420 | option for this so you have to use a `configparms' file (see the `INSTALL' | |
421 | file for details). It should contain: | |
61952351 UD |
422 | |
423 | slibdir=/lib | |
424 | sysconfdir=/etc | |
425 | ||
f12944ec UD |
426 | The first line specifies the directory for the essential libraries, the |
427 | second line the directory for system configuration files. | |
61952351 UD |
428 | |
429 | ??safety How should I avoid damaging my system when I install GNU libc? | |
430 | ||
f12944ec UD |
431 | {ZW} If you wish to be cautious, do not configure with --prefix=/usr. If |
432 | you don't specify a prefix, glibc will be installed in /usr/local, where it | |
433 | will probably not break anything. (If you wish to be certain, set the | |
434 | prefix to something like /usr/local/glibc2 which is not used for anything.) | |
61952351 UD |
435 | |
436 | The dangers when installing glibc in /usr are twofold: | |
437 | ||
438 | * glibc will overwrite the headers in /usr/include. Other C libraries | |
27e309c1 UD |
439 | install a different but overlapping set of headers there, so the effect |
440 | will probably be that you can't compile anything. You need to rename | |
441 | /usr/include out of the way before running `make install'. (Do not throw | |
442 | it away; you will then lose the ability to compile programs against your | |
443 | old libc.) | |
61952351 UD |
444 | |
445 | * None of your old libraries, static or shared, can be used with a | |
446 | different C library major version. For shared libraries this is not a | |
447 | problem, because the filenames are different and the dynamic linker | |
448 | will enforce the restriction. But static libraries have no version | |
449 | information. You have to evacuate all the static libraries in | |
450 | /usr/lib to a safe location. | |
451 | ||
452 | The situation is rather similar to the move from a.out to ELF which | |
453 | long-time Linux users will remember. | |
454 | ||
455 | ?? Do I need to use GNU CC to compile programs that will use the | |
456 | GNU C Library? | |
457 | ||
f12944ec UD |
458 | {ZW} In theory, no; the linker does not care, and the headers are supposed |
459 | to check for GNU CC before using its extensions to the C language. | |
61952351 | 460 | |
f12944ec UD |
461 | However, there are currently no ports of glibc to systems where another |
462 | compiler is the default, so no one has tested the headers extensively | |
463 | against another compiler. You may therefore encounter difficulties. If you | |
464 | do, please report them as bugs. | |
61952351 UD |
465 | |
466 | Also, in several places GNU extensions provide large benefits in code | |
467 | quality. For example, the library has hand-optimized, inline assembly | |
f12944ec UD |
468 | versions of some string functions. These can only be used with GCC. See |
469 | ?string for details. | |
61952351 UD |
470 | |
471 | ??crypt When linking with the new libc I get unresolved symbols | |
472 | `crypt' and `setkey'. Why aren't these functions in the | |
473 | libc anymore? | |
474 | ||
61952351 | 475 | |
6abca68d | 476 | {} Removed. Does not apply anymore. |
61952351 UD |
477 | |
478 | ?? When I use GNU libc on my Linux system by linking against | |
479 | the libc.so which comes with glibc all I get is a core dump. | |
480 | ||
f12944ec | 481 | {UD} On Linux, gcc sets the dynamic linker to /lib/ld-linux.so.1 unless the |
b3864d70 | 482 | user specifies a --dynamic-linker argument. This is the name of the libc5 |
f12944ec | 483 | dynamic linker, which does not work with glibc. |
61952351 | 484 | |
a379e56a UD |
485 | For casual use of GNU libc you can just specify to the linker |
486 | --dynamic-linker=/lib/ld-linux.so.2 | |
61952351 | 487 | |
f12944ec | 488 | which is the glibc dynamic linker, on Linux systems. On other systems the |
a379e56a UD |
489 | name is /lib/ld.so.1. When linking via gcc, you've got to add |
490 | -Wl,--dynamic-linker=/lib/ld-linux.so.2 | |
491 | ||
492 | to the gcc command line. | |
61952351 | 493 | |
f12944ec UD |
494 | To change your environment to use GNU libc for compiling you need to change |
495 | the `specs' file of your gcc. This file is normally found at | |
61952351 UD |
496 | |
497 | /usr/lib/gcc-lib/<arch>/<version>/specs | |
498 | ||
499 | In this file you have to change a few things: | |
500 | ||
501 | - change `ld-linux.so.1' to `ld-linux.so.2' | |
502 | ||
503 | - remove all expression `%{...:-lgmon}'; there is no libgmon in glibc | |
504 | ||
505 | - fix a minor bug by changing %{pipe:-} to %| | |
506 | ||
f12944ec UD |
507 | Here is what the gcc-2.7.2 specs file should look like when GNU libc is |
508 | installed at /usr: | |
61952351 UD |
509 | |
510 | ----------------------------------------------------------------------- | |
511 | *asm: | |
512 | %{V} %{v:%{!V:-V}} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*} %{Wa,*:%*} | |
513 | ||
514 | *asm_final: | |
515 | %| | |
516 | ||
517 | *cpp: | |
518 | %{fPIC:-D__PIC__ -D__pic__} %{fpic:-D__PIC__ -D__pic__} %{!m386:-D__i486__} %{posix:-D_POSIX_SOURCE} %{pthread:-D_REENTRANT} | |
519 | ||
520 | *cc1: | |
521 | %{profile:-p} | |
522 | ||
523 | *cc1plus: | |
524 | ||
525 | ||
526 | *endfile: | |
527 | %{!shared:crtend.o%s} %{shared:crtendS.o%s} crtn.o%s | |
528 | ||
529 | *link: | |
530 | -m elf_i386 %{shared:-shared} %{!shared: %{!ibcs: %{!static: %{rdynamic:-export-dynamic} %{!dynamic-linker:-dynamic-linker /lib/ld-linux.so.2}} %{static:-static}}} | |
531 | ||
532 | *lib: | |
533 | %{!shared: %{pthread:-lpthread} %{profile:-lc_p} %{!profile: -lc}} | |
534 | ||
535 | *libgcc: | |
536 | -lgcc | |
537 | ||
538 | *startfile: | |
539 | %{!shared: %{pg:gcrt1.o%s} %{!pg:%{p:gcrt1.o%s} %{!p:%{profile:gcrt1.o%s} %{!profile:crt1.o%s}}}} crti.o%s %{!shared:crtbegin.o%s} %{shared:crtbeginS.o%s} | |
540 | ||
541 | *switches_need_spaces: | |
542 | ||
543 | ||
544 | *signed_char: | |
545 | %{funsigned-char:-D__CHAR_UNSIGNED__} | |
546 | ||
547 | *predefines: | |
548 | -D__ELF__ -Dunix -Di386 -Dlinux -Asystem(unix) -Asystem(posix) -Acpu(i386) -Amachine(i386) | |
549 | ||
550 | *cross_compile: | |
551 | 0 | |
552 | ||
553 | *multilib: | |
554 | . ; | |
555 | ||
556 | ----------------------------------------------------------------------- | |
557 | ||
f12944ec UD |
558 | Things get a bit more complicated if you have GNU libc installed in some |
559 | other place than /usr, i.e., if you do not want to use it instead of the old | |
560 | libc. In this case the needed startup files and libraries are not found in | |
561 | the regular places. So the specs file must tell the compiler and linker | |
562 | exactly what to use. | |
61952351 UD |
563 | |
564 | Version 2.7.2.3 does and future versions of GCC will automatically | |
565 | provide the correct specs. | |
566 | ||
c891b2df | 567 | ??nonsh Looking through the shared libc file I haven't found the |
61952351 UD |
568 | functions `stat', `lstat', `fstat', and `mknod' and while |
569 | linking on my Linux system I get error messages. How is | |
570 | this supposed to work? | |
571 | ||
f12944ec UD |
572 | {RM} Believe it or not, stat and lstat (and fstat, and mknod) are supposed |
573 | to be undefined references in libc.so.6! Your problem is probably a missing | |
574 | or incorrect /usr/lib/libc.so file; note that this is a small text file now, | |
575 | not a symlink to libc.so.6. It should look something like this: | |
61952351 | 576 | |
71bedb76 | 577 | GROUP ( libc.so.6 libc_nonshared.a ) |
61952351 | 578 | |
83f6a990 | 579 | ??excpt When I run an executable on one system which I compiled on |
d89e7a96 UD |
580 | another, I get dynamic linker errors. Both systems have the same |
581 | version of glibc installed. What's wrong? | |
582 | ||
583 | {ZW} Glibc on one of these systems was compiled with gcc 2.7 or 2.8, the | |
584 | other with egcs (any version). Egcs has functions in its internal | |
585 | `libgcc.a' to support exception handling with C++. They are linked into | |
586 | any program or dynamic library compiled with egcs, whether it needs them or | |
587 | not. Dynamic libraries then turn around and export those functions again | |
588 | unless special steps are taken to prevent them. | |
589 | ||
590 | When you link your program, it resolves its references to the exception | |
591 | functions to the ones exported accidentally by libc.so. That works fine as | |
592 | long as libc has those functions. On the other system, libc doesn't have | |
593 | those functions because it was compiled by gcc 2.8, and you get undefined | |
594 | symbol errors. The symbols in question are named things like | |
595 | `__register_frame_info'. | |
596 | ||
597 | For glibc 2.0, the workaround is to not compile libc with egcs. We've also | |
598 | incorporated a patch which should prevent the EH functions sneaking into | |
599 | libc. It doesn't matter what compiler you use to compile your program. | |
600 | ||
601 | For glibc 2.1, we've chosen to do it the other way around: libc.so | |
602 | explicitly provides the EH functions. This is to prevent other shared | |
57b4b78a UD |
603 | libraries from doing it. |
604 | ||
605 | {UD} Starting with glibc 2.1.1 you can compile glibc with gcc 2.8.1 or | |
606 | newer since we have explicitly add references to the functions causing the | |
607 | problem. But you nevertheless should use EGCS for other reasons | |
608 | (see ?binsize). | |
d89e7a96 | 609 | |
83f6a990 UD |
610 | {GK} On some Linux distributions for PowerPC, you can see this when you have |
611 | built gcc or egcs from the Web sources (gcc versions 2.95 or earlier), then | |
612 | re-built glibc. This happens because in these versions of gcc, exception | |
613 | handling is implemented using an older method; the people making the | |
614 | distributions are a little ahead of their time. | |
615 | ||
616 | A quick solution to this is to find the libgcc.a file that came with the | |
6e8afc1c | 617 | distribution (it would have been installed under /usr/lib/gcc-lib), do |
83f6a990 UD |
618 | `ar x libgcc.a frame.o' to get the frame.o file out, and add a line saying |
619 | `LDLIBS-c.so += frame.o' to the file `configparms' in the directory you're | |
620 | building in. You can check you've got the right `frame.o' file by running | |
621 | `nm frame.o' and checking that it has the symbols defined that you're | |
622 | missing. | |
623 | ||
624 | This will let you build glibc with the C compiler. The C++ compiler | |
625 | will still be binary incompatible with any C++ shared libraries that | |
626 | you got with your distribution. | |
627 | ||
61952351 UD |
628 | ?? How can I compile gcc 2.7.2.1 from the gcc source code using |
629 | glibc 2.x? | |
630 | ||
f12944ec | 631 | {AJ} There's only correct support for glibc 2.0.x in gcc 2.7.2.3 or later. |
5ef50d00 | 632 | But you should get at least gcc 2.95.2.1 (or later versions) instead. |
61952351 UD |
633 | |
634 | ?? The `gencat' utility cannot process the catalog sources which | |
635 | were used on my Linux libc5 based system. Why? | |
636 | ||
f12944ec UD |
637 | {UD} The `gencat' utility provided with glibc complies to the XPG standard. |
638 | The older Linux version did not obey the standard, so they are not | |
639 | compatible. | |
61952351 UD |
640 | |
641 | To ease the transition from the Linux version some of the non-standard | |
f12944ec UD |
642 | features are also present in the `gencat' program of GNU libc. This mainly |
643 | includes the use of symbols for the message number and the automatic | |
61952351 UD |
644 | generation of header files which contain the needed #defines to map the |
645 | symbols to integers. | |
646 | ||
f12944ec UD |
647 | Here is a simple SED script to convert at least some Linux specific catalog |
648 | files to the XPG4 form: | |
61952351 UD |
649 | |
650 | ----------------------------------------------------------------------- | |
651 | # Change catalog source in Linux specific format to standard XPG format. | |
652 | # Ulrich Drepper <drepper@cygnus.com>, 1996. | |
653 | # | |
654 | /^\$ #/ { | |
655 | h | |
656 | s/\$ #\([^ ]*\).*/\1/ | |
657 | x | |
658 | s/\$ #[^ ]* *\(.*\)/\$ \1/ | |
659 | } | |
660 | ||
661 | /^# / { | |
662 | s/^# \(.*\)/\1/ | |
663 | G | |
664 | s/\(.*\)\n\(.*\)/\2 \1/ | |
665 | } | |
666 | ----------------------------------------------------------------------- | |
667 | ||
da2d1bc5 UD |
668 | ?? Programs using libc have their messages translated, but other |
669 | behavior is not localized (e.g. collating order); why? | |
670 | ||
671 | {ZW} Translated messages are automatically installed, but the locale | |
f12944ec UD |
672 | database that controls other behaviors is not. You need to run localedef to |
673 | install this database, after you have run `make install'. For example, to | |
674 | set up the French Canadian locale, simply issue the command | |
da2d1bc5 UD |
675 | |
676 | localedef -i fr_CA -f ISO-8859-1 fr_CA | |
677 | ||
678 | Please see localedata/README in the source tree for further details. | |
679 | ||
61952351 UD |
680 | ?? I have set up /etc/nis.conf, and the Linux libc 5 with NYS |
681 | works great. But the glibc NIS+ doesn't seem to work. | |
682 | ||
f12944ec UD |
683 | {TK} The glibc NIS+ implementation uses a /var/nis/NIS_COLD_START file for |
684 | storing information about the NIS+ server and their public keys, because the | |
685 | nis.conf file does not contain all the necessary information. You have to | |
686 | copy a NIS_COLD_START file from a Solaris client (the NIS_COLD_START file is | |
687 | byte order independent) or generate it with nisinit from the nis-tools | |
688 | package; available at | |
689 | ||
50f301a8 | 690 | http://www.suse.de/~kukuk/linux/nisplus.html |
61952351 | 691 | |
da2d1bc5 | 692 | ?? I have killed ypbind to stop using NIS, but glibc |
3dcf8ea6 | 693 | continues using NIS. |
4d06461a | 694 | |
f12944ec UD |
695 | {TK} For faster NIS lookups, glibc uses the /var/yp/binding/ files from |
696 | ypbind. ypbind 3.3 and older versions don't always remove these files, so | |
697 | glibc will continue to use them. Other BSD versions seem to work correctly. | |
698 | Until ypbind 3.4 is released, you can find a patch at | |
699 | ||
66f6a52b | 700 | <ftp://ftp.kernel.org/pub/linux/utils/net/NIS/ypbind-3.3-glibc4.diff.gz> |
a788b6c2 | 701 | |
3dcf8ea6 UD |
702 | ?? Under Linux/Alpha, I always get "do_ypcall: clnt_call: |
703 | RPC: Unable to receive; errno = Connection refused" when using NIS. | |
a788b6c2 | 704 | |
f12944ec UD |
705 | {TK} You need a ypbind version which is 64bit clean. Some versions are not |
706 | 64bit clean. A 64bit clean implementation is ypbind-mt. For ypbind 3.3, | |
707 | you need the patch from ftp.kernel.org (See the previous question). I don't | |
708 | know about other versions. | |
a788b6c2 | 709 | |
4d06461a | 710 | |
61952351 UD |
711 | ?? After installing glibc name resolving doesn't work properly. |
712 | ||
f12944ec UD |
713 | {AJ} You probably should read the manual section describing nsswitch.conf |
714 | (just type `info libc "NSS Configuration File"'). The NSS configuration | |
715 | file is usually the culprit. | |
61952351 | 716 | |
3dcf8ea6 UD |
717 | |
718 | ?? How do I create the databases for NSS? | |
719 | ||
720 | {AJ} If you have an entry "db" in /etc/nsswitch.conf you should also create | |
721 | the database files. The glibc sources contain a Makefile which does the | |
7fd18ea2 | 722 | necessary conversion and calls to create those files. The file is |
3dcf8ea6 UD |
723 | `db-Makefile' in the subdirectory `nss' and you can call it with `make -f |
724 | db-Makefile'. Please note that not all services are capable of using a | |
725 | database. Currently passwd, group, ethers, protocol, rpc, services shadow | |
3b019077 | 726 | and netgroup are implemented. See also ?nssdb. |
3dcf8ea6 | 727 | |
61952351 UD |
728 | ?? I have /usr/include/net and /usr/include/scsi as symlinks |
729 | into my Linux source tree. Is that wrong? | |
730 | ||
f12944ec UD |
731 | {PB} This was necessary for libc5, but is not correct when using glibc. |
732 | Including the kernel header files directly in user programs usually does not | |
733 | work (see ?kerhdr). glibc provides its own <net/*> and <scsi/*> header | |
734 | files to replace them, and you may have to remove any symlink that you have | |
735 | in place before you install glibc. However, /usr/include/asm and | |
736 | /usr/include/linux should remain as they were. | |
61952351 UD |
737 | |
738 | ?? Programs like `logname', `top', `uptime' `users', `w' and | |
739 | `who', show incorrect information about the (number of) | |
740 | users on my system. Why? | |
741 | ||
742 | {MK} See ?getlog. | |
743 | ||
744 | ?? After upgrading to glibc 2.1 with symbol versioning I get | |
745 | errors about undefined symbols. What went wrong? | |
746 | ||
f12944ec UD |
747 | {AJ} The problem is caused either by wrong program code or tools. In the |
748 | versioned libc a lot of symbols are now local that were global symbols in | |
749 | previous versions. It seems that programs linked against older versions | |
750 | often accidentally used libc global variables -- something that should not | |
751 | happen. | |
61952351 | 752 | |
f12944ec UD |
753 | The only way to fix this is to recompile your program. Sorry, that's the |
754 | price you might have to pay once for quite a number of advantages with | |
755 | symbol versioning. | |
61952351 UD |
756 | |
757 | ?? When I start the program XXX after upgrading the library | |
758 | I get | |
759 | XXX: Symbol `_sys_errlist' has different size in shared | |
760 | object, consider re-linking | |
761 | Why? What should I do? | |
762 | ||
f12944ec UD |
763 | {UD} As the message says, relink the binary. The problem is that a few |
764 | symbols from the library can change in size and there is no way to avoid | |
765 | this. _sys_errlist is a good example. Occasionally there are new error | |
766 | numbers added to the kernel and this must be reflected at user level, | |
767 | breaking programs that refer to them directly. | |
61952351 | 768 | |
f12944ec UD |
769 | Such symbols should normally not be used at all. There are mechanisms to |
770 | avoid using them. In the case of _sys_errlist, there is the strerror() | |
771 | function which should _always_ be used instead. So the correct fix is to | |
772 | rewrite that part of the application. | |
61952351 | 773 | |
f12944ec UD |
774 | In some situations (especially when testing a new library release) it might |
775 | be possible that a symbol changed size when that should not have happened. | |
776 | So in case of doubt report such a warning message as a problem. | |
61952351 | 777 | |
da2d1bc5 UD |
778 | ?? What do I need for C++ development? |
779 | ||
d89e7a96 UD |
780 | {HJ,AJ} You need either egcs 1.1 which comes directly with libstdc++ or |
781 | gcc-2.8.1 together with libstdc++ 2.8.1.1. egcs 1.1 has the better C++ | |
782 | support and works directly with glibc 2.1. If you use gcc-2.8.1 with | |
783 | libstdc++ 2.8.1.1, you need to modify libstdc++ a bit. A patch is available | |
784 | as: | |
66f6a52b | 785 | <ftp://alpha.gnu.org/gnu/libstdc++-2.8.1.1-glibc2.1-diff.gz> |
d89e7a96 UD |
786 | |
787 | Please note that libg++ 2.7.2 (and the Linux Versions 2.7.2.x) doesn't work | |
788 | very well with the GNU C library due to vtable thunks. If you're upgrading | |
789 | from glibc 2.0.x to 2.1 you have to recompile libstdc++ since the library | |
790 | compiled for 2.0 is not compatible due to the new Large File Support (LFS) | |
791 | in version 2.1. | |
fb98e2bf UD |
792 | |
793 | {UD} But since in the case of a shared libstdc++ the version numbers should | |
794 | be different existing programs will continue to work. | |
da2d1bc5 | 795 | |
6ca96fe2 UD |
796 | ?? Even statically linked programs need some shared libraries |
797 | which is not acceptable for me. What can I do? | |
798 | ||
f12944ec UD |
799 | {AJ} NSS (for details just type `info libc "Name Service Switch"') won't |
800 | work properly without shared libraries. NSS allows using different services | |
801 | (e.g. NIS, files, db, hesiod) by just changing one configuration file | |
802 | (/etc/nsswitch.conf) without relinking any programs. The only disadvantage | |
803 | is that now static libraries need to access shared libraries. This is | |
804 | handled transparently by the GNU C library. | |
6ca96fe2 | 805 | |
f12944ec UD |
806 | A solution is to configure glibc with --enable-static-nss. In this case you |
807 | can create a static binary that will use only the services dns and files | |
808 | (change /etc/nsswitch.conf for this). You need to link explicitly against | |
809 | all these services. For example: | |
6ca96fe2 | 810 | |
b15cb495 UD |
811 | gcc -static test-netdb.c -o test-netdb \ |
812 | -Wl,--start-group -lc -lnss_files -lnss_dns -lresolv -Wl,--end-group | |
6ca96fe2 UD |
813 | |
814 | The problem with this approach is that you've got to link every static | |
815 | program that uses NSS routines with all those libraries. | |
816 | ||
817 | {UD} In fact, one cannot say anymore that a libc compiled with this | |
818 | option is using NSS. There is no switch anymore. Therefore it is | |
819 | *highly* recommended *not* to use --enable-static-nss since this makes | |
820 | the behaviour of the programs on the system inconsistent. | |
821 | ||
bf47fa23 UD |
822 | ?? I just upgraded my Linux system to glibc and now I get |
823 | errors whenever I try to link any program. | |
824 | ||
825 | {ZW} This happens when you have installed glibc as the primary C library but | |
826 | have stray symbolic links pointing at your old C library. If the first | |
827 | `libc.so' the linker finds is libc 5, it will use that. Your program | |
828 | expects to be linked with glibc, so the link fails. | |
829 | ||
830 | The most common case is that glibc put its `libc.so' in /usr/lib, but there | |
831 | was a `libc.so' from libc 5 in /lib, which gets searched first. To fix the | |
832 | problem, just delete /lib/libc.so. You may also need to delete other | |
833 | symbolic links in /lib, such as /lib/libm.so if it points to libm.so.5. | |
834 | ||
0e0316f4 UD |
835 | {AJ} The perl script test-installation.pl which is run as last step during |
836 | an installation of glibc that is configured with --prefix=/usr should help | |
837 | detect these situations. If the script reports problems, something is | |
838 | really screwed up. | |
839 | ||
48244d09 UD |
840 | ?? When I use nscd the machine freezes. |
841 | ||
d89e7a96 UD |
842 | {UD} You cannot use nscd with Linux 2.0.*. There is functionality missing |
843 | in the kernel and work-arounds are not suitable. Besides, some parts of the | |
844 | kernel are too buggy when it comes to using threads. | |
48244d09 | 845 | |
440d13e2 | 846 | If you need nscd, you have to use at least a 2.1 kernel. |
48244d09 UD |
847 | |
848 | Note that I have at this point no information about any other platform. | |
849 | ||
0155a773 UD |
850 | ?? I need lots of open files. What do I have to do? |
851 | ||
852 | {AJ} This is at first a kernel issue. The kernel defines limits with | |
853 | OPEN_MAX the number of simultaneous open files and with FD_SETSIZE the | |
854 | number of used file descriptors. You need to change these values in your | |
e8b1163e | 855 | kernel and recompile the kernel so that the kernel allows more open |
0155a773 UD |
856 | files. You don't necessarily need to recompile the GNU C library since the |
857 | only place where OPEN_MAX and FD_SETSIZE is really needed in the library | |
858 | itself is the size of fd_set which is used by select. | |
859 | ||
7b19af68 UD |
860 | The GNU C library is now select free. This means it internally has no |
861 | limits imposed by the `fd_set' type. Instead all places where the | |
0155a773 UD |
862 | functionality is needed the `poll' function is used. |
863 | ||
864 | If you increase the number of file descriptors in the kernel you don't need | |
6e8afc1c | 865 | to recompile the C library. |
0155a773 UD |
866 | |
867 | {UD} You can always get the maximum number of file descriptors a process is | |
868 | allowed to have open at any time using | |
869 | ||
870 | number = sysconf (_SC_OPEN_MAX); | |
871 | ||
872 | This will work even if the kernel limits change. | |
873 | ||
d8a167a5 UD |
874 | ?? How do I get the same behavior on parsing /etc/passwd and |
875 | /etc/group as I have with libc5 ? | |
876 | ||
877 | {TK} The name switch setup in /etc/nsswitch.conf selected by most Linux | |
878 | distributions does not support +/- and netgroup entries in the files like | |
879 | /etc/passwd. Though this is the preferred setup some people might have | |
880 | setups coming over from the libc5 days where it was the default to recognize | |
881 | lines like this. To get back to the old behaviour one simply has to change | |
882 | the rules for passwd, group, and shadow in the nsswitch.conf file as | |
883 | follows: | |
884 | ||
885 | passwd: compat | |
886 | group: compat | |
887 | shadow: compat | |
888 | ||
889 | passwd_compat: nis | |
890 | group_compat: nis | |
891 | shadow_compat: nis | |
892 | ||
4f7ea427 | 893 | ??libs What needs to be recompiled when upgrading from glibc 2.0 to glibc |
0f6052a8 UD |
894 | 2.1? |
895 | ||
896 | {AJ,CG} If you just upgrade the glibc from 2.0.x (x <= 7) to 2.1, binaries | |
897 | that have been linked against glibc 2.0 will continue to work. | |
898 | ||
899 | If you compile your own binaries against glibc 2.1, you also need to | |
70cafe50 UD |
900 | recompile some other libraries. The problem is that libio had to be changed |
901 | and therefore libraries that are based or depend on the libio of glibc, | |
902 | e.g. ncurses, slang and most C++ libraries, need to be recompiled. If you | |
903 | experience strange segmentation faults in your programs linked against glibc | |
904 | 2.1, you might need to recompile your libraries. | |
0f6052a8 UD |
905 | |
906 | Another problem is that older binaries that were linked statically against | |
907 | glibc 2.0 will reference the older nss modules (libnss_files.so.1 instead of | |
908 | libnss_files.so.2), so don't remove them. Also, the old glibc-2.0 compiled | |
909 | static libraries (libfoo.a) which happen to depend on the older libio | |
50b65db1 UD |
910 | behavior will be broken by the glibc 2.1 upgrade. We plan to produce a |
911 | compatibility library that people will be able to link in if they want | |
912 | to compile a static library generated against glibc 2.0 into a program | |
913 | on a glibc 2.1 system. You just add -lcompat and you should be fine. | |
914 | ||
915 | The glibc-compat add-on will provide the libcompat.a library, the older | |
916 | nss modules, and a few other files. Together, they should make it | |
917 | possible to do development with old static libraries on a glibc 2.1 | |
8d8c6efa | 918 | system. This add-on is still in development. You can get it from |
df08cc56 | 919 | <ftp://alpha.gnu.org/gnu/glibc/glibc-compat-2.1.tar.gz> |
50b65db1 | 920 | but please keep in mind that it is experimental. |
0155a773 | 921 | |
b7398be5 UD |
922 | ?? Why is extracting files via tar so slow? |
923 | ||
924 | {AJ} Extracting of tar archives might be quite slow since tar has to look up | |
925 | userid and groupids and doesn't cache negative results. If you have nis or | |
926 | nisplus in your /etc/nsswitch.conf for the passwd and/or group database, | |
927 | each file extractions needs a network connection. There are two possible | |
928 | solutions: | |
929 | ||
930 | - do you really need NIS/NIS+ (some Linux distributions add by default | |
931 | nis/nisplus even if it's not needed)? If not, just remove the entries. | |
932 | ||
933 | - if you need NIS/NIS+, use the Name Service Cache Daemon nscd that comes | |
934 | with glibc 2.1. | |
935 | ||
2ee511d9 UD |
936 | ?? Compiling programs I get parse errors in libio.h (e.g. "parse error |
937 | before `_IO_seekoff'"). How should I fix this? | |
938 | ||
939 | {AJ} You might get the following errors when upgrading to glibc 2.1: | |
940 | ||
941 | In file included from /usr/include/stdio.h:57, | |
942 | from ... | |
943 | /usr/include/libio.h:335: parse error before `_IO_seekoff' | |
944 | /usr/include/libio.h:335: parse error before `_G_off64_t' | |
945 | /usr/include/libio.h:336: parse error before `_IO_seekpos' | |
946 | /usr/include/libio.h:336: parse error before `_G_fpos64_t' | |
947 | ||
948 | The problem is a wrong _G_config.h file in your include path. The | |
949 | _G_config.h file that comes with glibc 2.1 should be used and not one from | |
950 | libc5 or from a compiler directory. To check which _G_config.h file the | |
951 | compiler uses, compile your program with `gcc -E ...|grep G_config.h' and | |
952 | remove that file. Your compiler should pick up the file that has been | |
953 | installed by glibc 2.1 in your include directory. | |
954 | ||
4f7ea427 UD |
955 | ?? After upgrading to glibc 2.1, libraries that were compiled against |
956 | glibc 2.0.x don't work anymore. | |
957 | ||
958 | {AJ} See ?libs. | |
959 | ||
14a6b4e4 UD |
960 | ??nssdb What happened to the Berkeley DB libraries? Can I still use db |
961 | in /etc/nsswitch.conf? | |
962 | ||
963 | {AJ} Due to too many incompatible changes in disk layout and API of Berkeley | |
964 | DB and a too tight coupling of libc and libdb, the db library has been | |
965 | removed completely from glibc 2.2. The only place that really used the | |
966 | Berkeley DB was the NSS db module. | |
967 | ||
968 | The NSS db module has been rewritten to support a number of different | |
969 | versions of Berkeley DB for the NSS db module. Currently the releases 2.x | |
970 | and 3.x of Berkeley DB are supported. The older db 1.85 library is not | |
971 | supported. You can use the version from glibc 2.1.x or download a version | |
972 | from Sleepycat Software (http://www.sleepycat.com). The library has to be | |
973 | compiled as shared library and installed in the system lib directory | |
974 | (normally /lib). The library needs to have a special soname to be found by | |
975 | the NSS module. | |
976 | ||
977 | If public structures change in a new Berkeley db release, this needs to be | |
978 | reflected in glibc. | |
979 | ||
980 | Currently the code searches for libraries with a soname of "libdb.so.3" | |
981 | (that's the name from db 2.4.14 which comes with glibc 2.1.x) and | |
982 | "libdb-3.0.so" (the name used by db 3.0.55 as default). | |
983 | ||
be5dc44c AJ |
984 | The nss_db module is now in a separate package since it requires a database |
985 | library being available. | |
986 | ||
987 | ?? What has do be done when upgrading to glibc 2.2? | |
988 | ||
989 | {AJ} The upgrade to glibc 2.2 should run smoothly, there's in general no | |
990 | need to recompile programs or libraries. Nevertheless, some changes might | |
991 | be needed after upgrading: | |
992 | - The utmp daemon has been removed and is not supported by glibc anymore. | |
993 | If it has been in use, it should be switched off. | |
994 | - Programs using IPv6 have to be recompiled due to incompatible changes in | |
995 | sockaddr_in6 by the IPv6 working group. | |
64c07817 | 996 | - The Berkeley db libraries have been removed (for details see ?nssdb). |
be5dc44c AJ |
997 | - The format of the locale files has changed, all locales should be |
998 | regenerated with localedef. All statically linked applications which use | |
999 | i18n should be recompiled, otherwise they'll not be localized. | |
1000 | - glibc comes with a number of new applications. For example ldconfig has | |
1001 | been implemented for glibc, the libc5 version of ldconfig is not needed | |
1002 | anymore. | |
1003 | - There's no more K&R compatibility in the glibc headers. The GNU C library | |
1004 | requires a C compiler that handles especially prototypes correctly. | |
e090caee | 1005 | Especially gcc -traditional will not work with glibc headers. |
be5dc44c AJ |
1006 | |
1007 | Please read also the NEWS file which is the authoritative source for this | |
1008 | and gives more details for some topics. | |
1009 | ||
4442d7e8 UD |
1010 | ?? The makefiles want to do a CVS commit. |
1011 | ||
1012 | {UD} Only if you are not specifying the --without-cvs flag at configure | |
1013 | time. This is what you always have to use if you are checking sources | |
1014 | directly out of the public CVS repository or you have your own private | |
1015 | repository. | |
1016 | ||
1324affa UD |
1017 | ?? When compiling C++ programs, I get a compilation error in streambuf.h. |
1018 | ||
1019 | {BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to | |
1020 | apply a patch to the include files in /usr/include/g++, because the fpos_t | |
1021 | type has changed in glibc 2.2. The patch is at | |
1022 | http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff | |
1023 | ||
1024 | ?? When recompiling GCC, I get compilation errors in libio. | |
1025 | ||
4a5b72ff | 1026 | {BH} You are trying to recompile gcc 2.95.2? Use gcc 2.95.3 instead. |
5ef50d00 | 1027 | This version is needed because the fpos_t type and a few libio internals |
4a5b72ff | 1028 | have changed in glibc 2.2, and gcc 2.95.3 contains a corresponding patch. |
1324affa | 1029 | |
4442d7e8 | 1030 | |
61952351 UD |
1031 | ? Source and binary incompatibilities, and what to do about them |
1032 | ||
1033 | ?? I expect GNU libc to be 100% source code compatible with | |
1034 | the old Linux based GNU libc. Why isn't it like this? | |
1035 | ||
f12944ec UD |
1036 | {DMT,UD} Not every extension in Linux libc's history was well thought-out. |
1037 | In fact it had a lot of problems with standards compliance and with | |
1038 | cleanliness. With the introduction of a new version number these errors can | |
1039 | now be corrected. Here is a list of the known source code | |
61952351 UD |
1040 | incompatibilities: |
1041 | ||
1042 | * _GNU_SOURCE: glibc does not make the GNU extensions available | |
1043 | automatically. If a program depends on GNU extensions or some | |
1044 | other non-standard functionality, it is necessary to compile it | |
1045 | with the C compiler option -D_GNU_SOURCE, or better, to put | |
1046 | `#define _GNU_SOURCE' at the beginning of your source files, before | |
1047 | any C library header files are included. This difference normally | |
1048 | manifests itself in the form of missing prototypes and/or data type | |
1049 | definitions. Thus, if you get such errors, the first thing you | |
1050 | should do is try defining _GNU_SOURCE and see if that makes the | |
1051 | problem go away. | |
1052 | ||
1053 | For more information consult the file `NOTES' in the GNU C library | |
1054 | sources. | |
1055 | ||
1056 | * reboot(): GNU libc sanitizes the interface of reboot() to be more | |
1057 | compatible with the interface used on other OSes. reboot() as | |
1058 | implemented in glibc takes just one argument. This argument | |
1059 | corresponds to the third argument of the Linux reboot system call. | |
1060 | That is, a call of the form reboot(a, b, c) needs to be changed into | |
1061 | reboot(c). Beside this the header <sys/reboot.h> defines the needed | |
1062 | constants for the argument. These RB_* constants should be used | |
1063 | instead of the cryptic magic numbers. | |
1064 | ||
1065 | * swapon(): the interface of this function didn't change, but the | |
1066 | prototype is in a separate header file <sys/swap.h>. This header | |
1067 | file also provides the SWAP_* constants defined by <linux/swap.h>; | |
1068 | you should use them for the second argument to swapon(). | |
1069 | ||
1070 | * errno: If a program uses the variable "errno", then it _must_ | |
1071 | include <errno.h>. The old libc often (erroneously) declared this | |
1072 | variable implicitly as a side-effect of including other libc header | |
1073 | files. glibc is careful to avoid such namespace pollution, which, | |
1074 | in turn, means that you really need to include the header files that | |
1075 | you depend on. This difference normally manifests itself in the | |
1076 | form of the compiler complaining about references to an undeclared | |
1077 | symbol "errno". | |
1078 | ||
1079 | * Linux-specific syscalls: All Linux system calls now have appropriate | |
1080 | library wrappers and corresponding declarations in various header files. | |
1081 | This is because the syscall() macro that was traditionally used to | |
1082 | work around missing syscall wrappers are inherently non-portable and | |
1083 | error-prone. The following table lists all the new syscall stubs, | |
1084 | the header-file declaring their interface and the system call name. | |
1085 | ||
1086 | syscall name: wrapper name: declaring header file: | |
1087 | ------------- ------------- ---------------------- | |
1088 | bdflush bdflush <sys/kdaemon.h> | |
1089 | syslog ksyslog_ctl <sys/klog.h> | |
1090 | ||
1091 | * lpd: Older versions of lpd depend on a routine called _validuser(). | |
1092 | The library does not provide this function, but instead provides | |
1093 | __ivaliduser() which has a slightly different interface. Simply | |
1094 | upgrading to a newer lpd should fix this problem (e.g., the 4.4BSD | |
1095 | lpd is known to be working). | |
1096 | ||
1097 | * resolver functions/BIND: like on many other systems the functions of | |
1098 | the resolver library are not included in libc itself. There is a | |
1099 | separate library libresolv. If you get undefined symbol errors for | |
1100 | symbols starting with `res_*' simply add -lresolv to your linker | |
1101 | command line. | |
1102 | ||
1103 | * the `signal' function's behavior corresponds to the BSD semantic and | |
1104 | not the SysV semantic as it was in libc-5. The interface on all GNU | |
1105 | systems shall be the same and BSD is the semantic of choice. To use | |
1106 | the SysV behavior simply use `sysv_signal', or define _XOPEN_SOURCE. | |
1107 | See ?signal for details. | |
1108 | ||
1109 | ??getlog Why does getlogin() always return NULL on my Linux box? | |
1110 | ||
f12944ec UD |
1111 | {UD} The GNU C library has a format for the UTMP and WTMP file which differs |
1112 | from what your system currently has. It was extended to fulfill the needs | |
1113 | of the next years when IPv6 is introduced. The record size is different and | |
1114 | some fields have different positions. The files written by functions from | |
1115 | the one library cannot be read by functions from the other library. Sorry, | |
1116 | but this is what a major release is for. It's better to have a cut now than | |
1117 | having no means to support the new techniques later. | |
61952351 | 1118 | |
61952351 UD |
1119 | ?? Where are the DST_* constants found in <sys/time.h> on many |
1120 | systems? | |
1121 | ||
f12944ec UD |
1122 | {UD} These constants come from the old BSD days and are not used anymore |
1123 | (libc5 does not actually implement the handling although the constants are | |
1124 | defined). | |
61952351 | 1125 | |
f12944ec | 1126 | Instead GNU libc contains zone database support and compatibility code for |
8b4a4715 UD |
1127 | POSIX TZ environment variable handling. For former is very much preferred |
1128 | (see ?tzdb). | |
61952351 UD |
1129 | |
1130 | ?? The prototypes for `connect', `accept', `getsockopt', | |
1131 | `setsockopt', `getsockname', `getpeername', `send', | |
1132 | `sendto', and `recvfrom' are different in GNU libc from | |
1133 | any other system I saw. This is a bug, isn't it? | |
1134 | ||
f12944ec UD |
1135 | {UD} No, this is no bug. This version of GNU libc already follows the new |
1136 | Single Unix specifications (and I think the POSIX.1g draft which adopted the | |
1137 | solution). The type for a parameter describing a size is now `socklen_t', a | |
1138 | new type. | |
61952351 UD |
1139 | |
1140 | ??kerhdr On Linux I've got problems with the declarations in Linux | |
1141 | kernel headers. | |
1142 | ||
f12944ec UD |
1143 | {UD,AJ} On Linux, the use of kernel headers is reduced to the minimum. This |
1144 | gives Linus the ability to change the headers more freely. Also, user | |
a9ddb793 | 1145 | programs are now insulated from changes in the size of kernel data |
f12944ec | 1146 | structures. |
61952351 | 1147 | |
f12944ec UD |
1148 | For example, the sigset_t type is 32 or 64 bits wide in the kernel. In |
1149 | glibc it is 1024 bits wide. This guarantees that when the kernel gets a | |
1150 | bigger sigset_t (for POSIX.1e realtime support, say) user programs will not | |
1151 | have to be recompiled. Consult the header files for more information about | |
1152 | the changes. | |
61952351 | 1153 | |
f12944ec UD |
1154 | Therefore you shouldn't include Linux kernel header files directly if glibc |
1155 | has defined a replacement. Otherwise you might get undefined results because | |
1156 | of type conflicts. | |
61952351 UD |
1157 | |
1158 | ?? I don't include any kernel headers myself but the compiler | |
1159 | still complains about redeclarations of types in the kernel | |
1160 | headers. | |
1161 | ||
f12944ec UD |
1162 | {UD} The kernel headers before Linux 2.1.61 and 2.0.32 don't work correctly |
1163 | with glibc. Compiling C programs is possible in most cases but C++ programs | |
1164 | have (due to the change of the name lookups for `struct's) problems. One | |
1165 | prominent example is `struct fd_set'. | |
61952351 | 1166 | |
f12944ec UD |
1167 | There might be some problems left but 2.1.61/2.0.32 fix most of the known |
1168 | ones. See the BUGS file for other known problems. | |
61952351 UD |
1169 | |
1170 | ??signal Why don't signals interrupt system calls anymore? | |
1171 | ||
f12944ec UD |
1172 | {ZW} By default GNU libc uses the BSD semantics for signal(), unlike Linux |
1173 | libc 5 which used System V semantics. This is partially for compatibility | |
1174 | with other systems and partially because the BSD semantics tend to make | |
1175 | programming with signals easier. | |
61952351 UD |
1176 | |
1177 | There are three differences: | |
1178 | ||
1179 | * BSD-style signals that occur in the middle of a system call do not | |
1180 | affect the system call; System V signals cause the system call to | |
1181 | fail and set errno to EINTR. | |
1182 | ||
1183 | * BSD signal handlers remain installed once triggered. System V signal | |
1184 | handlers work only once, so one must reinstall them each time. | |
1185 | ||
1186 | * A BSD signal is blocked during the execution of its handler. In other | |
1187 | words, a handler for SIGCHLD (for example) does not need to worry about | |
1188 | being interrupted by another SIGCHLD. It may, however, be interrupted | |
1189 | by other signals. | |
1190 | ||
1191 | There is general consensus that for `casual' programming with signals, the | |
1192 | BSD semantics are preferable. You don't need to worry about system calls | |
1193 | returning EINTR, and you don't need to worry about the race conditions | |
1194 | associated with one-shot signal handlers. | |
1195 | ||
1196 | If you are porting an old program that relies on the old semantics, you can | |
1197 | quickly fix the problem by changing signal() to sysv_signal() throughout. | |
1198 | Alternatively, define _XOPEN_SOURCE before including <signal.h>. | |
1199 | ||
1200 | For new programs, the sigaction() function allows you to specify precisely | |
1201 | how you want your signals to behave. All three differences listed above are | |
1202 | individually switchable on a per-signal basis with this function. | |
1203 | ||
f12944ec UD |
1204 | If all you want is for one specific signal to cause system calls to fail and |
1205 | return EINTR (for example, to implement a timeout) you can do this with | |
61952351 UD |
1206 | siginterrupt(). |
1207 | ||
1208 | ||
1209 | ??string I've got errors compiling code that uses certain string | |
1210 | functions. Why? | |
1211 | ||
f12944ec | 1212 | {AJ} glibc 2.1 has special string functions that are faster than the normal |
fdacb17d | 1213 | library functions. Some of the functions are additionally implemented as |
a9d75566 UD |
1214 | inline functions and others as macros. This might lead to problems with |
1215 | existing codes but it is explicitly allowed by ISO C. | |
61952351 UD |
1216 | |
1217 | The optimized string functions are only used when compiling with | |
fdacb17d | 1218 | optimizations (-O1 or higher). The behavior can be changed with two feature |
f12944ec | 1219 | macros: |
61952351 UD |
1220 | |
1221 | * __NO_STRING_INLINES: Don't do any string optimizations. | |
1222 | * __USE_STRING_INLINES: Use assembly language inline functions (might | |
1223 | increase code size dramatically). | |
1224 | ||
f12944ec UD |
1225 | Since some of these string functions are now additionally defined as macros, |
1226 | code like "char *strncpy();" doesn't work anymore (and is unnecessary, since | |
fdacb17d | 1227 | <string.h> has the necessary declarations). Either change your code or |
f12944ec | 1228 | define __NO_STRING_INLINES. |
61952351 | 1229 | |
f12944ec UD |
1230 | {UD} Another problem in this area is that gcc still has problems on machines |
1231 | with very few registers (e.g., ix86). The inline assembler code can require | |
1232 | almost all the registers and the register allocator cannot always handle | |
1233 | this situation. | |
61952351 UD |
1234 | |
1235 | One can disable the string optimizations selectively. Instead of writing | |
1236 | ||
1237 | cp = strcpy (foo, "lkj"); | |
1238 | ||
1239 | one can write | |
1240 | ||
1241 | cp = (strcpy) (foo, "lkj"); | |
1242 | ||
1243 | This disables the optimization for that specific call. | |
1244 | ||
4775243a UD |
1245 | ?? I get compiler messages "Initializer element not constant" with |
1246 | stdin/stdout/stderr. Why? | |
1247 | ||
1248 | {RM,AJ} Constructs like: | |
66f6a52b | 1249 | static FILE *InPtr = stdin; |
4775243a | 1250 | |
fdacb17d UD |
1251 | lead to this message. This is correct behaviour with glibc since stdin is |
1252 | not a constant expression. Please note that a strict reading of ISO C does | |
f12944ec | 1253 | not allow above constructs. |
4775243a | 1254 | |
f12944ec UD |
1255 | One of the advantages of this is that you can assign to stdin, stdout, and |
1256 | stderr just like any other global variable (e.g. `stdout = my_stream;'), | |
1257 | which can be very useful with custom streams that you can write with libio | |
fdacb17d | 1258 | (but beware this is not necessarily portable). The reason to implement it |
f12944ec | 1259 | this way were versioning problems with the size of the FILE structure. |
4775243a | 1260 | |
fdacb17d UD |
1261 | To fix those programs you've got to initialize the variable at run time. |
1262 | This can be done, e.g. in main, like: | |
1263 | ||
66f6a52b UD |
1264 | static FILE *InPtr; |
1265 | int main(void) | |
1266 | { | |
1267 | InPtr = stdin; | |
1268 | } | |
fdacb17d UD |
1269 | |
1270 | or by constructors (beware this is gcc specific): | |
1271 | ||
66f6a52b UD |
1272 | static FILE *InPtr; |
1273 | static void inPtr_construct (void) __attribute__((constructor)); | |
1274 | static void inPtr_construct (void) { InPtr = stdin; } | |
fdacb17d | 1275 | |
4775243a UD |
1276 | |
1277 | ?? I can't compile with gcc -traditional (or | |
1278 | -traditional-cpp). Why? | |
1279 | ||
1280 | {AJ} glibc2 does break -traditional and -traditonal-cpp - and will continue | |
fdacb17d | 1281 | to do so. For example constructs of the form: |
f12944ec | 1282 | |
66f6a52b UD |
1283 | enum {foo |
1284 | #define foo foo | |
1285 | } | |
f12944ec UD |
1286 | |
1287 | are useful for debugging purposes (you can use foo with your debugger that's | |
1288 | why we need the enum) and for compatibility (other systems use defines and | |
1289 | check with #ifdef). | |
4775243a UD |
1290 | |
1291 | ?? I get some errors with `gcc -ansi'. Isn't glibc ANSI compatible? | |
1292 | ||
1293 | {AJ} The GNU C library is compatible with the ANSI/ISO C standard. If | |
f12944ec | 1294 | you're using `gcc -ansi', the glibc includes which are specified in the |
fdacb17d | 1295 | standard follow the standard. The ANSI/ISO C standard defines what has to be |
f12944ec UD |
1296 | in the include files - and also states that nothing else should be in the |
1297 | include files (btw. you can still enable additional standards with feature | |
1298 | flags). | |
4775243a | 1299 | |
f12944ec UD |
1300 | The GNU C library is conforming to ANSI/ISO C - if and only if you're only |
1301 | using the headers and library functions defined in the standard. | |
4775243a | 1302 | |
4d42000c UD |
1303 | ?? I can't access some functions anymore. nm shows that they do |
1304 | exist but linking fails nevertheless. | |
1305 | ||
f12944ec UD |
1306 | {AJ} With the introduction of versioning in glibc 2.1 it is possible to |
1307 | export only those identifiers (functions, variables) that are really needed | |
1308 | by application programs and by other parts of glibc. This way a lot of | |
1309 | internal interfaces are now hidden. nm will still show those identifiers | |
1310 | but marking them as internal. ISO C states that identifiers beginning with | |
1311 | an underscore are internal to the libc. An application program normally | |
1312 | shouldn't use those internal interfaces (there are exceptions, | |
1313 | e.g. __ivaliduser). If a program uses these interfaces, it's broken. These | |
1314 | internal interfaces might change between glibc releases or dropped | |
1315 | completely. | |
4d42000c | 1316 | |
9de4e203 UD |
1317 | ?? When using the db-2 library which comes with glibc is used in |
1318 | the Perl db modules the testsuite is not passed. This did not | |
1319 | happen with db-1, gdbm, or ndbm. | |
1320 | ||
6abca68d | 1321 | {} Removed. Does not apply anymore. |
9de4e203 | 1322 | |
5148d49f UD |
1323 | ?? The pow() inline function I get when including <math.h> is broken. |
1324 | I get segmentation faults when I run the program. | |
1325 | ||
1326 | {UD} Nope, the implementation is correct. The problem is with egcs version | |
1327 | prior to 1.1. I.e., egcs 1.0 to 1.0.3 are all broken (at least on Intel). | |
1328 | If you have to use this compiler you must define __NO_MATH_INLINES before | |
1329 | including <math.h> to prevent the inline functions from being used. egcs 1.1 | |
1330 | fixes the problem. I don't know about gcc 2.8 and 2.8.1. | |
1331 | ||
05f732b3 UD |
1332 | ?? The sys/sem.h file lacks the definition of `union semun'. |
1333 | ||
1334 | {UD} Nope. This union has to be provided by the user program. Former glibc | |
1335 | versions defined this but it was an error since it does not make much sense | |
1336 | when thinking about it. The standards describing the System V IPC functions | |
1337 | define it this way and therefore programs must be adopted. | |
1338 | ||
a42134a7 UD |
1339 | ?? Why has <netinet/ip_fw.h> disappeared? |
1340 | ||
1341 | {AJ} The corresponding Linux kernel data structures and constants are | |
440d13e2 | 1342 | totally different in Linux 2.0 and Linux 2.2. This situation has to be |
a42134a7 UD |
1343 | taken care in user programs using the firewall structures and therefore |
1344 | those programs (ipfw is AFAIK the only one) should deal with this problem | |
1345 | themselves. | |
1346 | ||
ee586e0e UD |
1347 | ?? I get floods of warnings when I use -Wconversion and include |
1348 | <string.h> or <math.h>. | |
1349 | ||
1350 | {ZW} <string.h> and <math.h> intentionally use prototypes to override | |
1351 | argument promotion. -Wconversion warns about all these. You can safely | |
1352 | ignore the warnings. | |
1353 | ||
1354 | -Wconversion isn't really intended for production use, only for shakedown | |
1355 | compiles after converting an old program to standard C. | |
1356 | ||
4d42000c | 1357 | |
49b75f5e UD |
1358 | ?? After upgrading to glibc 2.1, I receive errors about |
1359 | unresolved symbols, like `_dl_initial_searchlist' and can not | |
1360 | execute any binaries. What went wrong? | |
1361 | ||
1362 | {AJ} This normally happens if your libc and ld (dynamic linker) are from | |
1363 | different releases of glibc. For example, the dynamic linker | |
1364 | /lib/ld-linux.so.2 comes from glibc 2.0.x, but the version of libc.so.6 is | |
1365 | from glibc 2.1. | |
1366 | ||
1367 | The path /lib/ld-linux.so.2 is hardcoded in every glibc2 binary but | |
1368 | libc.so.6 is searched via /etc/ld.so.cache and in some special directories | |
1369 | like /lib and /usr/lib. If you run configure with another prefix than /usr | |
1370 | and put this prefix before /lib in /etc/ld.so.conf, your system will break. | |
1371 | ||
1372 | So what can you do? Either of the following should work: | |
1373 | ||
1374 | * Run `configure' with the same prefix argument you've used for glibc 2.0.x | |
1375 | so that the same paths are used. | |
1376 | * Replace /lib/ld-linux.so.2 with a link to the dynamic linker from glibc | |
1377 | 2.1. | |
1378 | ||
1379 | You can even call the dynamic linker by hand if everything fails. You've | |
1380 | got to set LD_LIBRARY_PATH so that the corresponding libc is found and also | |
1381 | need to provide an absolute path to your binary: | |
1382 | ||
1383 | LD_LIBRARY_PATH=<path-where-libc.so.6-lives> \ | |
1384 | <path-where-corresponding-dynamic-linker-lives>/ld-linux.so.2 \ | |
1385 | <path-to-binary>/binary | |
1386 | ||
1387 | For example `LD_LIBRARY_PATH=/libold /libold/ld-linux.so.2 /bin/mv ...' | |
1388 | might be useful in fixing a broken system (if /libold contains dynamic | |
1389 | linker and corresponding libc). | |
1390 | ||
1391 | With that command line no path is used. To further debug problems with the | |
1392 | dynamic linker, use the LD_DEBUG environment variable, e.g. | |
1393 | `LD_DEBUG=help echo' for the help text. | |
1394 | ||
1395 | If you just want to test this release, don't put the lib directory in | |
1396 | /etc/ld.so.conf. You can call programs directly with full paths (as above). | |
1397 | When compiling new programs against glibc 2.1, you've got to specify the | |
1398 | correct paths to the compiler (option -I with gcc) and linker (options | |
1399 | --dynamic-linker, -L and --rpath). | |
1400 | ||
b74656f9 | 1401 | ?? bonnie reports that char i/o with glibc 2 is much slower than with |
9f6b6d8d UD |
1402 | libc5. What can be done? |
1403 | ||
1404 | {AJ} The GNU C library uses thread safe functions by default and libc5 used | |
1405 | non thread safe versions. The non thread safe functions have in glibc the | |
1406 | suffix `_unlocked', for details check <stdio.h>. Using `putc_unlocked' etc. | |
1407 | instead of `putc' should give nearly the same speed with bonnie (bonnie is a | |
1408 | benchmark program for measuring disk access). | |
1409 | ||
9de4e203 UD |
1410 | ?? Programs compiled with glibc 2.1 can't read db files made with glibc |
1411 | 2.0. What has changed that programs like rpm break? | |
1412 | ||
6abca68d | 1413 | {} Removed. Does not apply anymore. |
9de4e203 | 1414 | |
8a40ed68 UD |
1415 | ?? Autoconf's AC_CHECK_FUNC macro reports that a function exists, but |
1416 | when I try to use it, it always returns -1 and sets errno to ENOSYS. | |
1417 | ||
1418 | {ZW} You are using a 2.0 Linux kernel, and the function you are trying to | |
1419 | use is only implemented in 2.1/2.2. Libc considers this to be a function | |
1420 | which exists, because if you upgrade to a 2.2 kernel, it will work. One | |
1421 | such function is sigaltstack. | |
1422 | ||
1423 | Your program should check at runtime whether the function works, and | |
1424 | implement a fallback. Note that Autoconf cannot detect unimplemented | |
1425 | functions in other systems' C libraries, so you need to do this anyway. | |
1426 | ||
b5a9efcd UD |
1427 | ?? My program segfaults when I call fclose() on the FILE* returned |
1428 | from setmntent(). Is this a glibc bug? | |
1429 | ||
1430 | {GK} No. Don't do this. Use endmntent(), that's what it's for. | |
1431 | ||
1432 | In general, you should use the correct deallocation routine. For instance, | |
1433 | if you open a file using fopen(), you should deallocate the FILE * using | |
1434 | fclose(), not free(), even though the FILE * is also a pointer. | |
1435 | ||
1436 | In the case of setmntent(), it may appear to work in most cases, but it | |
1437 | won't always work. Unfortunately, for compatibility reasons, we can't | |
1438 | change the return type of setmntent() to something other than FILE *. | |
1439 | ||
c891b2df UD |
1440 | ?? I get "undefined reference to `atexit'" |
1441 | ||
1442 | {UD} This means that your installation is somehow broken. The situation is | |
1443 | the same as for 'stat', 'fstat', etc (see ?nonsh). Investigate why the | |
1444 | linker does not pick up libc_nonshared.a. | |
1445 | ||
1446 | If a similar message is issued at runtime this means that the application or | |
1447 | DSO is not linked against libc. This can cause problems since 'atexit' is | |
1448 | not exported anymore. | |
1449 | ||
49b75f5e | 1450 | |
61952351 UD |
1451 | ? Miscellaneous |
1452 | ||
1453 | ?? After I changed configure.in I get `Autoconf version X.Y. | |
1454 | or higher is required for this script'. What can I do? | |
1455 | ||
1456 | {UD} You have to get the specified autoconf version (or a later one) | |
2eb45444 | 1457 | from your favorite mirror of ftp.gnu.org. |
61952351 UD |
1458 | |
1459 | ?? When I try to compile code which uses IPv6 headers and | |
1460 | definitions on my Linux 2.x.y system I am in trouble. | |
1461 | Nothing seems to work. | |
1462 | ||
f12944ec UD |
1463 | {UD} The problem is that IPv6 development still has not reached a point |
1464 | where the headers are stable. There are still lots of incompatible changes | |
1465 | made and the libc headers have to follow. | |
61952351 | 1466 | |
cb0509a8 UD |
1467 | {PB} The 2.1 release of GNU libc aims to comply with the current versions of |
1468 | all the relevant standards. The IPv6 support libraries for older Linux | |
1469 | systems used a different naming convention and so code written to work with | |
1470 | them may need to be modified. If the standards make incompatible changes in | |
1471 | the future then the libc may need to change again. | |
1472 | ||
1473 | IPv6 will not work with a 2.0.x kernel. When kernel 2.2 is released it | |
1474 | should contain all the necessary support; until then you should use the | |
3f7b3d9b | 1475 | latest 2.1.x release you can find. As of 98/11/26 the currently recommended |
cb0509a8 UD |
1476 | kernel for IPv6 is 2.1.129. |
1477 | ||
1478 | Also, as of the 2.1 release the IPv6 API provided by GNU libc is not | |
b669ab02 | 1479 | 100% complete. |
61952351 | 1480 | |
8b4a4715 | 1481 | ??tzdb When I set the timezone by setting the TZ environment variable |
73237de3 UD |
1482 | to EST5EDT things go wrong since glibc computes the wrong time |
1483 | from this information. | |
1484 | ||
f12944ec UD |
1485 | {UD} The problem is that people still use the braindamaged POSIX method to |
1486 | select the timezone using the TZ environment variable with a format EST5EDT | |
8b4a4715 UD |
1487 | or whatever. People, if you insist on using TZ instead of the timezone |
1488 | database (see below), read the POSIX standard, the implemented behaviour is | |
f12944ec UD |
1489 | correct! What you see is in fact the result of the decisions made while |
1490 | POSIX.1 was created. We've only implemented the handling of TZ this way to | |
1491 | be POSIX compliant. It is not really meant to be used. | |
1492 | ||
1493 | The alternative approach to handle timezones which is implemented is the | |
1494 | correct one to use: use the timezone database. This avoids all the problems | |
1495 | the POSIX method has plus it is much easier to use. Simply run the tzselect | |
1496 | shell script, answer the question and use the name printed in the end by | |
8b4a4715 UD |
1497 | making a symlink /etc/localtime pointing to /usr/share/zoneinfo/NAME (NAME |
1498 | is the returned value from tzselect). That's all. You never again have to | |
1499 | worry. | |
f12944ec UD |
1500 | |
1501 | So, please avoid sending bug reports about time related problems if you use | |
1502 | the POSIX method and you have not verified something is really broken by | |
1503 | reading the POSIX standards. | |
73237de3 | 1504 | |
fdacb17d UD |
1505 | ?? What other sources of documentation about glibc are available? |
1506 | ||
1507 | {AJ} The FSF has a page about the GNU C library at | |
1508 | <http://www.gnu.org/software/libc/>. The problem data base of open and | |
1509 | solved bugs in GNU libc is available at | |
1510 | <http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl>. Eric Green has written | |
14a6b4e4 | 1511 | a HowTo for converting from Linux libc5 to glibc2. The HowTo is accessible |
fdacb17d UD |
1512 | via the FSF page and at <http://www.imaxx.net/~thrytis/glibc>. Frodo |
1513 | Looijaard describes a different way installing glibc2 as secondary libc at | |
1514 | <http://huizen.dds.nl/~frodol/glibc>. | |
1515 | ||
1516 | Please note that this is not a complete list. | |
1517 | ||
3f7b3d9b UD |
1518 | ?? The timezone string for Sydney/Australia is wrong since even when |
1519 | daylight saving time is in effect the timezone string is EST. | |
1520 | ||
1521 | {UD} The problem for some timezones is that the local authorities decided | |
1522 | to use the term "summer time" instead of "daylight saving time". In this | |
1523 | case the abbreviation character `S' is the same as the standard one. So, | |
1524 | for Sydney we have | |
1525 | ||
1526 | Eastern Standard Time = EST | |
1527 | Eastern Summer Time = EST | |
1528 | ||
1529 | Great! To get this bug fixed convince the authorities to change the laws | |
1530 | and regulations of the country this effects. glibc behaves correctly. | |
1531 | ||
eeabe877 UD |
1532 | ??make I've build make 3.77 against glibc 2.1 and now make gets |
1533 | segmentation faults. | |
1534 | ||
6abca68d | 1535 | {} Removed. Does not apply anymore, use make 3.79 or newer. |
eeabe877 | 1536 | |
c63598bf UD |
1537 | ?? Why do so many programs using math functions fail on my AlphaStation? |
1538 | ||
1539 | {AO} The functions floor() and floorf() use an instruction that is not | |
1540 | implemented in some old PALcodes of AlphaStations. This may cause | |
1541 | `Illegal Instruction' core dumps or endless loops in programs that | |
1542 | catch these signals. Updating the firmware to a 1999 release has | |
1543 | fixed the problem on an AlphaStation 200 4/166. | |
1544 | ||
8892c471 UD |
1545 | ?? The conversion table for character set XX does not match with |
1546 | what I expect. | |
1547 | ||
1548 | {UD} I don't doubt for a minute that some of the conversion tables contain | |
1549 | errors. We tried the best we can and relied on automatic generation of the | |
1550 | data to prevent human-introduced errors but this still is no guarantee. If | |
1551 | you think you found a problem please send a bug report describing it and | |
1552 | give an authoritive reference. The latter is important since otherwise | |
1553 | the current behaviour is as good as the proposed one. | |
1554 | ||
1555 | Before doing this look through the list of known problem first: | |
1556 | ||
1557 | - the GBK (simplified Chinese) encoding is based on Unicode tables. This | |
1558 | is good. These tables, however, differ slightly from the tables used | |
1559 | by the M$ people. The differences are these [+ Unicode, - M$]: | |
1560 | ||
1561 | +0xA1AA 0x2015 | |
1562 | +0xA844 0x2014 | |
1563 | -0xA1AA 0x2014 | |
1564 | -0xA844 0x2015 | |
1565 | ||
1566 | In addition the Unicode tables contain mappings for the GBK characters | |
1567 | 0xA8BC, 0xA8BF, 0xA989 to 0xA995, and 0xFE50 to 0xFEA0. | |
1568 | ||
ffa156af UD |
1569 | - when mapping from EUC-CN to GBK and vice versa we ignore the fact that |
1570 | the coded character at position 0xA1A4 maps to different Unicode | |
1571 | characters. Since the iconv() implementation can do whatever it wants | |
1572 | if it cannot directly map a character this is a perfectly good solution | |
1573 | since the semantics and appearance of the character does not change. | |
8892c471 | 1574 | |
be76803a UD |
1575 | ?? How can I find out which version of glibc I am using in the moment? |
1576 | ||
1577 | {UD} If you want to find out about the version from the command line simply | |
1578 | run the libc binary. This is probably not possible on all platforms but | |
1579 | where it is simply locate the libc DSO and start it as an application. On | |
1580 | Linux like | |
1581 | ||
1582 | /lib/libc.so.6 | |
1583 | ||
1584 | This will produce all the information you need. | |
1585 | ||
1586 | What always will work is to use the API glibc provides. Compile and run the | |
1587 | following little program to get the version information: | |
1588 | ||
1589 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
1590 | #include <stdio.h> | |
1591 | #include <gnu/libc-version.h> | |
1592 | int main (void) { puts (gnu_get_libc_version ()); return 0; } | |
1593 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
1594 | ||
1595 | This interface can also obviously be used to perform tests at runtime if | |
1596 | this should be necessary. | |
1597 | ||
5e014387 UD |
1598 | ?? Context switching with setcontext() does not work from within |
1599 | signal handlers. | |
1600 | ||
1601 | {DMT} The Linux implementations (IA-64, S390 so far) of setcontext() | |
1602 | supports synchronous context switches only. There are several reasons for | |
1603 | this: | |
1604 | ||
1605 | o UNIX provides no other (portable) way of effecting a synchronous | |
1606 | context switch (also known as co-routine switch). Some versions | |
1607 | support this via setjmp()/longjmp() but this does not work | |
1608 | universally. | |
1609 | ||
1610 | o As defined by the UNIX '98 standard, the only way setcontext() | |
1611 | could trigger an asychronous context switch is if this function | |
1612 | were invoked on the ucontext_t pointer passed as the third argument | |
1613 | to a signal handler. But according to draft 5, XPG6, XBD 2.4.3, | |
1614 | setcontext() is not among the set of routines that may be called | |
1615 | from a signal handler. | |
1616 | ||
1617 | o If setcontext() were to be used for asynchronous context switches, | |
1618 | all kinds of synchronization and re-entrancy issues could arise and | |
1619 | these problems have already been solved by real multi-threading | |
1620 | libraries (e.g., POSIX threads or Linux threads). | |
1621 | ||
1622 | o Synchronous context switching can be implemented entirely in | |
1623 | user-level and less state needs to be saved/restored than for an | |
1624 | asynchronous context switch. It is therefore useful to distinguish | |
1625 | between the two types of context switches. Indeed, some | |
1626 | application vendors are known to use setcontext() to implement | |
1627 | co-routines on top of normal (heavier-weight) pre-emptable threads. | |
1628 | ||
1629 | It should be noted that if someone was dead-bent on using setcontext() | |
1630 | on the third arg of a signal handler, then IA-64 Linux could support | |
1631 | this via a special version of sigaction() which arranges that all | |
1632 | signal handlers start executing in a shim function which takes care of | |
1633 | saving the preserved registers before calling the real signal handler | |
1634 | and restoring them afterwards. In other words, we could provide a | |
1635 | compatibility layer which would support setcontext() for asynchronous | |
1636 | context switches. However, given the arguments above, I don't think | |
1637 | that makes sense. setcontext() provides a decent co-routine interface | |
1638 | and we should just discourage any asynchronous use (which just calls | |
1639 | for trouble at any rate). | |
1640 | ||
1641 | ||
61952351 UD |
1642 | \f |
1643 | Answers were given by: | |
5e014387 UD |
1644 | {UD} Ulrich Drepper, <drepper@redhat.com> |
1645 | {DMT} David Mosberger-Tang, <davidm@hpl.hp.com> | |
61952351 | 1646 | {RM} Roland McGrath, <roland@gnu.org> |
14a6b4e4 | 1647 | {AJ} Andreas Jaeger, <aj@suse.de> |
61952351 UD |
1648 | {EY} Eric Youngdale, <eric@andante.jic.com> |
1649 | {PB} Phil Blundell, <Philip.Blundell@pobox.com> | |
1650 | {MK} Mark Kettenis, <kettenis@phys.uva.nl> | |
1651 | {ZW} Zack Weinberg, <zack@rabi.phys.columbia.edu> | |
50f301a8 | 1652 | {TK} Thorsten Kukuk, <kukuk@suse.de> |
5e014387 | 1653 | {GK} Geoffrey Keating, <geoffk@redhat.com> |
da2d1bc5 | 1654 | {HJ} H.J. Lu, <hjl@gnu.org> |
0f6052a8 | 1655 | {CG} Cristian Gafton, <gafton@redhat.com> |
5e014387 | 1656 | {AO} Alexandre Oliva, <aoliva@redhat.com> |
1324affa | 1657 | {BH} Bruno Haible, <haible@clisp.cons.org> |
61952351 UD |
1658 | \f |
1659 | Local Variables: | |
1660 | mode:outline | |
1661 | outline-regexp:"\\?" | |
f12944ec | 1662 | fill-column:76 |
61952351 | 1663 | End: |