From owner-freebsd-questions Tue Nov 17 08:02:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28371 for freebsd-questions-outgoing; Tue, 17 Nov 1998 08:00:28 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from elrond.rosmail.com (elrond.rosmail.com [195.90.128.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28339 for ; Tue, 17 Nov 1998 08:00:13 -0800 (PST) (envelope-from 0824@08700000.mhs.rosmail.com) From: 0824@08700000.mhs.rosmail.com Received: (from uucp@localhost) by elrond.rosmail.com (8.9.1a/8.9-V) with UUCP id SAA27132 for freebsd-questions@freebsd.org; Tue, 17 Nov 1998 18:54:56 +0300 (MSK) To: freebsd-questions@freebsd.org Date: Tue, 17 Nov 98 18:48:09 +0300 (MSK) Message-ID: Organization: JSC "ROSNET" Subject: Re: Linux emulation problem : RH5.0 binaries on 2.2.7R. Sender: owner-freebsd-questions@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG > > > > I have Freebsd 2.2.7R and Redhat 5.0 Linux. I have installed > > linux emulation on FreeBSD box the way it was recommended in the > > handbook. Then I wrote and compile a simple program (a sort of > > "hello world") on my Linux box and tried to run it under Freebsd. > > Well, the helloworld program complaied about missing libraries > > ld-linux.so.2, libc.so.6. So I retreived these files from Linux > > box an put them to /compat/linux/lib, reran /compat/linux/sbin/ > > ldconfig and ran helloworld again. This what I got: > > Did you: > > 1. Install the linux_lib port? > 2. Install the Linux mulator? Yes, I did. I did everything what was recommended in FreeBSD HandBook "Linux emulation". I even compile the helloworld.c with option "-static" : gcc -o hw -static helloworld.c so the program does not need dynamic libraries. When I run it I got the same message: Segmentation fault. I have no idea what to do! Is that a problem of Redhat 5.0 (because its new c lib "glibc2")?? Sincerely, Vlad Safronov. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message