Please add a ~sh keyword to sys-devel/gdb-6.8-r2; it seems to work fine for me (both cross-gdb on x86 and native on sh4). Reproducible: Always
Really? Fails to configure here, says sh4 isn't supported(and its not)
scarran ~ # sh4-unknown-linux-gnu-gdb warning: A handler for the OS ABI "GNU/Linux" is not built into this configuration of GDB. Attempting to continue with the default sh settings. GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=sh4-unknown-linux-gnu". (gdb) scarran ~ # emerge -p =cross-sh4-unknown-linux-gnu/gdb-6.8-r2 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] cross-sh4-unknown-linux-gnu/gdb-6.8-r2 (this is after manually adding the ~sh keyword to the ebuild. What am I doing wrong?)
(In reply to comment #2) > Calculating dependencies... done! > [ebuild R ] cross-sh4-unknown-linux-gnu/gdb-6.8-r2 > > (this is after manually adding the ~sh keyword to the ebuild. What am I doing > wrong?) > You aren't running it natively. Keywords are added to ebuilds that work natively, not crosscompiled.
Hrm, without that keyword I can't emerge it (yes /etc/portage/package.keywords has an entry for it but portage still won't merge it). I don't have the sh4 hardware with me right now, but I'll recheck tomorrow morning. I'm pretty sure it runs.
(In reply to comment #4) > Hrm, without that keyword I can't emerge it (yes /etc/portage/package.keywords > has an entry for it but portage still won't merge it). > > I don't have the sh4 hardware with me right now, but I'll recheck tomorrow > morning. I'm pretty sure it runs. > And? Did you put 'sys-devel/gdb **' on package.keywords? Because if you don't add the **, it won't work.
This is really for you sh people to work out :) If you need support from toolchain please CC us.
I'm closing this one as "invalid": The rebuild of gdb stopped midway because configure couldn't find a valid termcap. I've started to rebuild all dependecies but that may take a (long) while (can't use distcc since the native and cross compilers have some inconsistencies wrt. fpscr handling which screws up a lot of builds, and the build system is sloooow).
i think Raúl Porcel had a link to a patchset which added native gdb sh support
