From: Eric Buddington <eric@sparrow.nad.adelphia.net>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: ebuddington@mail.wesleyan.edu, Brian Gerst <bgerst@didntduck.org>,
linux-kernel@vger.kernel.org
Subject: Re: 386 'ls' gets SIGILL iff /proc is mounted
Date: Thu, 29 Mar 2001 10:05:27 -0500 [thread overview]
Message-ID: <20010329100527.P80@sparrow.nad.adelphia.net> (raw)
In-Reply-To: <20010327012709.I59@sparrow.nad.adelphia.net> <3AC09F14.53D06AC7@didntduck.org> <20010327091205.B80@sparrow.nad.adelphia.net> <3AC0A21B.438EFE02@didntduck.org> <20010328124845.I80@sparrow.nad.adelphia.net> <m3wv99vk8o.fsf@otr.mynet.cygnus.com>
In-Reply-To: <m3wv99vk8o.fsf@otr.mynet.cygnus.com>; from drepper@redhat.com on Wed, Mar 28, 2001 at 10:09:11AM -0800
On Wed, Mar 28, 2001 at 10:09:11AM -0800, Ulrich Drepper wrote:
> Eric Buddington <eric@sparrow.nad.adelphia.net> writes:
>
> > OK. Context again (since I clipped preceding notes): 386SX/20 nfsroot,
> > getting SIGILL on lots of processes, math emulation is enabled, ls and
> > glibc were compiled with '-march=i386 -mcpu=i386' to be sure.
>
> This isn't enough. You compiled glibc on a i586 or later without
> telling configure to use the i386 configuration. Run configure with
> the usual options and
>
> i386-linux-gnu
>
> at the end of the command line and then use the options above.
This seems to have solved the problem. Thanks!
-Eric
prev parent reply other threads:[~2001-03-29 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 6:27 Eric Buddington
2001-03-27 14:09 ` Brian Gerst
2001-03-27 14:12 ` Eric Buddington
2001-03-27 14:22 ` Brian Gerst
[not found] ` <20010328124845.I80@sparrow.nad.adelphia.net>
[not found] ` <m3wv99vk8o.fsf@otr.mynet.cygnus.com>
2001-03-29 15:05 ` Eric Buddington [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010329100527.P80@sparrow.nad.adelphia.net \
--to=eric@sparrow.nad.adelphia.net \
--cc=bgerst@didntduck.org \
--cc=drepper@cygnus.com \
--cc=ebuddington@mail.wesleyan.edu \
--cc=ebuddington@wesleyan.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®