On Dec 28, 2013, at 7:32 PM, John-Mark Gurney <[email protected]> wrote:
> Marcel Moolenaar wrote this message on Sat, Dec 28, 2013 at 18:49 -0800: >> >> On Dec 28, 2013, at 5:08 PM, John-Mark Gurney <[email protected]> wrote: >> >>> Marcel Moolenaar wrote this message on Sat, Dec 28, 2013 at 23:01 +0000: >>>> Author: marcel >>>> Date: Sat Dec 28 23:01:57 2013 >>>> New Revision: 260022 >>>> URL: http://svnweb.freebsd.org/changeset/base/260022 >>>> >>>> Log: >>>> Allow building a cross libkvm by setting TARGET_ARCH. The library so >>>> produced will be called libkvm-${ARCH} instead of libkvm. This allows >>>> installing it alongside the native version. >>>> For symbol lookups, use ps_pglobal_lookup() instead of __fdnlist() >>>> when building a cross libkvm. It is assumed that the cross tool that >>>> uses the cross libkvm also provides an implementation for this >>>> proc_services function. >>>> >>>> Note that this commit does not change any of the architecture-specific >>>> code for cross-compilation. >>> >>> Shouldn't we be putting cross compiled libaries in another location >>> than /lib? Kind of like the compat32 libs? >> >> I don't think we're there yet. libkvm is not ready for generic >> cross building and we don't really have the infrastructure for >> it either. For one, we really need to install CPU-specific >> headers on the host. >> >> We can manually cross-build a few things, like binutils and gdb >> and I see value to extend that to kgdb, but that's about it. > > Then what was the goal of this commit? Was it to have an i386 > compatible libkvm that links w/ amd64 binaries? or? The goal was to get a step closer to having useful cross-tools, including those that need libkvm. In this case it allowed me to make an ia64 cross-kgdb, useful for core analysis and/or remote debugging. -- Marcel Moolenaar [email protected]
signature.asc
Description: Message signed with OpenPGP using GPGMail
