From bee1e289fafbf1d429f401eb4d7ea4be27282f17 Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Fri, 9 Jul 1999 09:58:27 +0000 Subject: Update. 1999-07-09 Ulrich Drepper * hesiod/Versions [GLIBC_2.2]: Add _nss_hesiod_initgroups. * hesiod/hesiod-grp.c: Add initgroups support. Patch by Nalin Dahyabhai . --- FAQ.in | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'FAQ.in') diff --git a/FAQ.in b/FAQ.in index 72b3ad38c2..b368744f1f 100644 --- a/FAQ.in +++ b/FAQ.in @@ -342,6 +342,23 @@ against the previous version of the GNU libc (version 2.0) but also against all future versions. +?? 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. + + ? Installation and configuration issues ?? Can I replace the libc on my Linux system with GNU libc? -- cgit v1.2.3