cvs commit: src/gnu/usr.bin/gdb/kgdb Makefile
M. Warner Losh
imp at bsdimp.com
Tue Nov 30 00:35:54 PST 2004
In message: <41690958-42A5-11D9-A383-000D93C47836 at xcllnt.net>
Marcel Moolenaar <marcel at xcllnt.net> writes:
: On Nov 29, 2004, at 11:35 PM, Ruslan Ermilov wrote:
: > On Tue, Nov 30, 2004 at 02:56:53AM +0000, Marcel Moolenaar wrote:
: >> marcel 2004-11-30 02:56:53 UTC
: >> FreeBSD src repository
: >> Modified files:
: >> gnu/usr.bin/gdb/kgdb Makefile
: >> Log:
: >> s/MACHINE_ARCH/TARGET_ARCH/. We use TARGET_ARCH to pick the MD files
: >> for libgdb and should do so here as well.
: >> Revision Changes Path
: >> 1.2 +1 -1 src/gnu/usr.bin/gdb/kgdb/Makefile
: > We use TARGET_ARCH only for cross-tools. Once upon a time, gdb
: > was a cross-tool (as part of gnu/usr.bin/binutils). Not anymore.
: > If it's not going to change then we should be using MACHINE_ARCH.
: I disagree. The fact that gdb is not a cross-tool in the buildworld
: sense of the meaning is because we don't need gdb to cross-build world.
: This does not mean that gdb cannot be a cross-tool from a developers
: point of view. In fact, it's really handy to be able to debug a kernel
: remotely when the debugger doesn't run on the same architecture as
: the kernel. I for one do not want to have 2 machines per architecture
: for the only reason that I want to debug a kernel remotely. So, I made
: some changes to work towards that goal. I see no problems or harm,
: especially since I'm not misusing TARGET_ARCH. The ability to build a
: cross-debugger is simply not utilized as part of a buildworld.
But MACHINE_ARCH is set correctly during the build of gdb when you've
set TARGET_ARCH to build the rest of the world you need to build gdb
with. Or am I missing something?
More information about the cvs-all