summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-07-09 09:58:27 +0000
committerUlrich Drepper <drepper@redhat.com>1999-07-09 09:58:27 +0000
commitbee1e289fafbf1d429f401eb4d7ea4be27282f17 (patch)
tree0138033ca265a704c6ca771ddf64353f97842726 /FAQ.in
parent110215a9a76594e808903af957f3273e3bc11a87 (diff)
downloadglibc-bee1e289fafbf1d429f401eb4d7ea4be27282f17.tar.gz
glibc-bee1e289fafbf1d429f401eb4d7ea4be27282f17.tar.xz
glibc-bee1e289fafbf1d429f401eb4d7ea4be27282f17.zip
Update.
1999-07-09  Ulrich Drepper  <drepper@cygnus.com>

	* hesiod/Versions [GLIBC_2.2]: Add _nss_hesiod_initgroups.
	* hesiod/hesiod-grp.c: Add initgroups support.
	Patch by Nalin Dahyabhai <nsdahya1@pobox.com>.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in17
1 files changed, 17 insertions, 0 deletions
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?