Summary: | Adding support for different targets in gdb ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Scott Price <prices> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gdb-6.3-r1.ebuild
Updated ebuild |
Description
Scott Price
2005-04-06 08:17:51 UTC
Created attachment 55479 [details]
gdb-6.3-r1.ebuild
Ebuild to add different targets to gdb. The changes were minor.
well i'll be damned, is it really that easy ? do cross-compile versions overwrite files of native gdb ? (i.e. try `FEATURES=collision-protect emerge gdb && FEATURES=collision-protect CTARGET=arm-blah emerge gdb` ... Created attachment 55534 [details]
Updated ebuild
This ebuild puts docs in:
/usr/share/doc/gdb-6.3-r1/${CTARGET}
and Info in:
/usr/share/info/gdb/${CTARGET}
so that different versions don't collide. in the info and documentation.
how about we just not install docs when CTARGET != CHOST ? is there any reason to ? The only reason I can think of is if the user doesn't install the one for their arch they wouldn't have the docs. Is that a killer? Scott =) eh, i say just make user have 1 native gdb rather than a bunch of wasted duplicated docs ... one thing about the libdir though ... is anything ever actually installed into it ? /usr/lib/gdb/avr/libiberty.a I don't even know if it is needed, though. It is also provided by binutils. I will remove the docs from the cross builds tonight. Scott =) ok, that stuff is provided by binutils, so that's not an issue updated the ebuild now so basically the only thing installed in cross-gdb mode are the binaries thanks ! :) |