diff options
| author | Ulrich Drepper <drepper@redhat.com> | 1999-07-26 02:38:26 +0000 |
|---|---|---|
| committer | Ulrich Drepper <drepper@redhat.com> | 1999-07-26 02:38:26 +0000 |
| commit | c7f7281eca160b12767b9e3c25b443bce13512a2 (patch) | |
| tree | 7d814d87dcbd5437bcaaa5bc19d94c78d7392ad2 /FAQ | |
| parent | 63f7cb448b3958d7520d7eab6d092d7e6f11f1d9 (diff) | |
Update.
* libio/iofclose.c (_IO_new_fclose): Detect new streams and handle
them appropriately.
* libio/oldiofclose.c (_IO_old_fclose): Likewise.
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 20 |
1 files changed, 20 insertions, 0 deletions
@@ -41,6 +41,9 @@ please let me know. 1.15. What's the problem with configure --enable-omitfp? 1.16. I get failures during `make check'. What should I do? 1.17. What is symbol versioning good for? Do I need it? +1.18. How can I compile on my fast ix86 machine a working libc for my slow + i386? After installing libc, programs abort with "Illegal + Instruction". 2. Installation and configuration issues @@ -514,6 +517,23 @@ compatibility - forever! The binary compatibility you lose is not only against the previous version of the GNU libc (version 2.0) but also against all future versions. + +1.18. How can I compile on my fast ix86 machine a working libc for my slow + i386? After installing libc, programs abort with "Illegal + Instruction". + +{AJ} glibc and gcc might generate some instructions on your machine that +aren't available on i386. You've got to tell glibc that you're configuring +for i386 with adding i386 as your machine, for example: + + ../configure --prefix=/usr i386-pc-linux-gnu + +And you need to tell gcc to only generate i386 code, just add `-mcpu=i386' +(just -m386 doesn't work) to your CFLAGS. + +{UD} This applies not only to the i386. Compiling on a i686 for any older +model will also fail if the above methods are not used. + . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |