Date: Tue, 1 Aug 2000 15:06:39 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Mark Abene <phiber@radicalmedia.com> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: em86 Message-ID: <14727.5008.699253.856165@grasshopper.cs.duke.edu> In-Reply-To: <20000801140037.C25790@radicalmedia.com> References: <20000731051254.M2866@radicalmedia.com> <14725.33823.884653.998738@grasshopper.cs.duke.edu> <20000731112927.O2866@radicalmedia.com> <14725.40416.628136.782665@grasshopper.cs.duke.edu> <20000731182649.P2866@radicalmedia.com> <14726.8485.261054.310851@grasshopper.cs.duke.edu> <20000731223126.T2866@radicalmedia.com> <14726.53916.585060.311869@grasshopper.cs.duke.edu> <20000801140037.C25790@radicalmedia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Abene writes: > This is a long shot, but it's possible you didn't enable the option > CONFIG_BINFMT_EM86 in your kernel. As far as that warning message, not > sure why you got that. I was running RedHat 6.0, and that uses glibc-2.1. > Also, if you look at the source RPM for em86-2.2-1 itself, there is a define > for glibc-2.1. I know it's definitely supported. It's also possible that > it's totally broken in newer kernels. But hopefully not. It looks like you can load it as a module (binfmt_em86.o) I did that, and now the "em86" is implicit... (eg, I can run /usr/bin/ldconfig86 directly) Unfortunately, the same thing happens: a segv after it calls getdents. This machine is running a virgin install of RH 6.2 as it came off the ISO image at the redhat mirrors. Its running kernel 2.2.14-6.0 I'm about to give up.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14727.5008.699253.856165>