On 7/30/13 5:37 AM, David Chisnall wrote:
On 29 Jul 2013, at 21:54, Mateusz Guzik <mjgu...@gmail.com> wrote:
Well, there was linux_kdump in ports but it apparently got obsolete as
necessary support for included in our regular kdump.
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
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=bin/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?
Once you have identified the binary type, you chain to the appropriate
binary in libexec.
if you can't find it, then you just exit.
David
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
