From owner-freebsd-current@FreeBSD.ORG Mon Jul 29 21:37:47 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 88019C07; Mon, 29 Jul 2013 21:37:47 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 566052256; Mon, 29 Jul 2013 21:37:47 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r6TLbhVR075588 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Jul 2013 21:37:45 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: ldd runs linux programs From: David Chisnall In-Reply-To: <20130729205449.GA6007@dft-labs.eu> Date: Mon, 29 Jul 2013 22:37:38 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <4DD4BD93-0218-4FCC-A63F-E408D6291687@FreeBSD.org> References: <20130728193110.GB17514@gpr.nnz-home.ru> <20130728204958.GA32322@dft-labs.eu> <51F5D491.1080803@freebsd.org> <20130729081254.GB32322@dft-labs.eu> <20130729155625.GA2544@charmander> <20130729205449.GA6007@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.1508) Cc: Gennady Proskurin , Mark Johnston , freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 21:37:47 -0000 On 29 Jul 2013, at 21:54, Mateusz Guzik wrote: > Well, there was linux_kdump in ports but it apparently got obsolete as > necessary support for included in our regular kdump. >=20 > So it may make sense to teach our ldd how to deal with Linux binaries > for consistency, but its unclear for me if this is better than = providing > linux_ldd. Also there is the problem of (not) appending /compat/linux = to > printed paths (for Linux binaries the kernel performs file lookups = against > /compat/linux first). I'm not that interested in this problem though. = :P >=20 > That being said, if you want to do something with this, I suggest > cleaning up PRs and reviving discussion in > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/127276 What would be the correct behaviour for non-native binaries? Stacy Son = and Brooks Davis have been working on providing a kernel activator for = QEMU user mode, which lets us run, for example, MIPS or ARM binaries on = x86. If you have a MIPS64 ELF file and you run ldd on it, what would = the correct behaviour be? David