Date: Mon, 29 Jul 2013 22:37:38 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Mateusz Guzik <mjguzik@gmail.com> Cc: Gennady Proskurin <gprspb@mail.ru>, Mark Johnston <markj@FreeBSD.org>, freebsd-current@FreeBSD.org Subject: Re: ldd runs linux programs Message-ID: <4DD4BD93-0218-4FCC-A63F-E408D6291687@FreeBSD.org> In-Reply-To: <20130729205449.GA6007@dft-labs.eu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 Jul 2013, at 21:54, Mateusz Guzik <mjguzik@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DD4BD93-0218-4FCC-A63F-E408D6291687>