[PATCH v2 7/9] compile: New 'compile print'
Jan Kratochvil
jan.kratochvil@redhat.com
Wed Apr 8 20:03:00 GMT 2015
On Mon, 06 Apr 2015 19:58:31 +0200, Paul_Koning@dell.com wrote:
> On Apr 6, 2015, at 1:52 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > On Mon, 06 Apr 2015 19:49:28 +0200, Paul_Koning@dell.com wrote:
> > > Also, “the compiler” begs the question: which one, i.e., how is “the
> > > compiler” found?
> >
> > A complicated way, for non-native targets an appropriate cross-gcc should be
> > found.
>
> Ok. I would not expect that to be documented in NEWS, but it seems like it
> should be in gdb.texinfo or some similar spot. I have a whole pile of
> cross-compilers in various places; I would need to understand what the
> algorithm looks like to be able to ensure that the correct one is found.
I find it should "just work":
gdb:
compile_to_object():
ARCH(-[^-]*)?-OS
ARCH=gdbarch_gnu_triplet_regexp
i386/x86_64: (x86_64|i.86)
s390/s390x: s390x?
*: bfd_arch_info::arch_name
OS=gdb_osabi_names.regexp
GNU/Linux: linux(-gnu)?
*: ""
gcc:
libcc1_set_arguments()->find_compiler():
$PATH
Just make your cross-compiler accessible by $PATH and cross your fingers.
If it does not work it is a bug that should be filed+fixed.
It is questionable whether it should be in GDB manual or GCC manual.
So far the GCC manual does not mention GCC's libcc1 GDB interface at all.
Jan
More information about the Gdb-patches
mailing list