From owner-freebsd-emulation@FreeBSD.ORG Tue Mar 15 05:18:36 2005 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCE3A16A4CE for ; Tue, 15 Mar 2005 05:18:36 +0000 (GMT) Received: from a.outbound.bsdwebsolutions.com (a.outbound.bsdwebsolutions.com [64.72.68.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7243443D54 for ; Tue, 15 Mar 2005 05:18:36 +0000 (GMT) (envelope-from mqbs@mu42.net) Received: from [64.72.68.15] (helo=mail.bsdwebsolutions.com) by a.outbound.bsdwebsolutions.com with esmtp (Exim 4.44; FreeBSD) id 1DB4Rv-0004ny-Q4 for freebsd-emulation@freebsd.org ; Tue, 15 Mar 2005 00:18:35 -0500 Received: from 69.118.10.154 (SquirrelMail authenticated user mqbs@mu42.net) by mail.bsdwebsolutions.com with HTTP; Tue, 15 Mar 2005 00:18:35 -0500 (EST) Message-ID: <60653.69.118.10.154.1110863915.squirrel@mail.bsdwebsolutions.com> Date: Tue, 15 Mar 2005 00:18:35 -0500 (EST) From: "Max" To: freebsd-emulation@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Attempts to bootstrap emulated gentoo dies X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 05:18:36 -0000 I've been working on this for a few days, so far without luck. I'd like to be able to compile linux programs which die on my FreeBSD-5.3-RELEASE-p5 by having a working chrootable source-based linux toolkit set up. The linux_base-gentoo-stage1 port seemed like a logical choice, since I know it should be able to build all of the required tools on its own. The port installs fine, and I can `emerge sync' without difficulty, as specified in the pkg-message. The problem comes after I chroot into /compat/linux and attempt to run `/usr/portage/scripts/bootstrap.sh' as the pkg-message suggests I do. I make it all the way up to building glibc, which goes for ahwile then quits with this message: /bin/sh: line 1: /var/tmp/portage/glibc-2.3.4.20040808-r1/work/build/elf/ld-linux.so.2: cannot execute binary file make[2]: *** [/var/tmp/portage/glibc-2.3.4.20040808-r1/work/build/sunrpc/xbootparam_prot.stmp] Error 126 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20040808-r1/work/glibc-2.3.3/sunrpc' make[1]: *** [sunrpc/others] Error 2 make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.4.20040808-r1/work/glibc-2.3.3' make: *** [all] Error 2 !!! ERROR: sys-libs/glibc-2.3.4.20040808-r1 failed. !!! Function src_compile, Line 690, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. I've tried deleting it, refetching it, and recompiling it three times, to no avail. This is what the file which it is unable to excecute looks like, from within the chroot: bash-2.05b# file ld-linux.so.2 ld-linux.so.2: symbolic link to `ld.so' bash-2.05b# file ld.so ld.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped bash-2.05b# ls -l ld.so -rwxr-xr-x 1 root portage 112985 Mar 15 01:42 ld.so I know that my machine has excecuted other linux binaries because gcc ran without fail quite a lot of times before this error was generated, emerge works fine, and bash worked perfectly. Anybody know what's up, or what else I could provide that might lead towards a solution? Does this port compile for other people? Max