All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maupin, Chase" <chase.maupin@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>,
	"Dmytriyenko, Denys" <denys@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [arago-commits] Denys Dmytriyenko : external-arago-sdk-toolchain:	package up gdb from the toolchain as well
Date: Wed, 14 Nov 2012 03:58:42 +0000	[thread overview]
Message-ID: <DA9820EE-0593-4552-A1FC-6167B44C2CB9@ti.com> (raw)
In-Reply-To: <580F15A3-540F-480F-BEFC-9B7989D20BDF@ti.com>

[-- Attachment #1: Type: text/plain, Size: 6996 bytes --]

What were we doing in the past?  Qtcreator used to work correct?

Sent from my cell phone

----- Reply message -----
From: "Cooper Jr., Franklin" <fcooper@ti.com>
Date: Tue, Nov 13, 2012 8:44 pm
Subject: [meta-arago] [arago-commits] Denys Dmytriyenko : external-arago-sdk-toolchain: package up gdb from the toolchain as well
To: "Dmytriyenko, Denys" <denys@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>

Not being able to debug via Qt Creator is not an option.

If we need to pull recipes in so we can build against 7.2 then let's do that.

If we need to recompile the toolchain and package up this toolchain and distribute it as a prebuilt toolchain we can do that also.

Any other options I missed?


On Nov 13, 2012, at 8:27 PM, "Dmytriyenko, Denys" <denys@ti.com> wrote:

> Well, gdb from the Arago toolchain does not provide python support, as that's
> how it was built back then...
>
> The only way to get Python support built into gdb is to rebuild it from
> sources, which we discussed and agreed not to do. Moreover, if you want gdb
> built from sources, it will be of a different version - OE-Core provides
> version 7.4, while we got clearance for 7.2 and also we have target gdbserver
> of version 7.2 as well...
>
> Denys
>
>
> On Tue, Nov 13, 2012 at 01:31:37PM +0000, Cooper Jr., Franklin wrote:
>>
>> We need gdb with python support is required for Qt debugging via Qt Creator http://arago-project.org/pipermail/arago-commits/2012-January/001611.html.
>> Gdb-cross-canadian recipe seems to include this needed support.
>>
>> A simple test to determine if python support has been added to gdb.
>> Run gdb
>> Enter python print 23.
>> 23 should be echoed back to the console.
>>
>> My build that picked up your gdb changes did not include python support for gdb.
>>
>> -----Original Message-----
>> From: arago-commits-bounces@arago-project.org [mailto:arago-commits-bounces@arago-project.org] On Behalf Of Arago Project git
>> Sent: Monday, November 12, 2012 10:41 PM
>> To: arago-commits@arago-project.org
>> Subject: [arago-commits] Denys Dmytriyenko : external-arago-sdk-toolchain: package up gdb from the toolchain as well
>>
>> Module: meta-arago
>> Branch: master
>> Commit: 78bec05ff04e6e98def765e61a7a00c35c635938
>> URL:    http://arago-project.org/git/meta-arago.git?a=commit;h=78bec05ff04e6e98def765e61a7a00c35c635938
>>
>> Author: Denys Dmytriyenko <denys@ti.com>
>> Date:   Mon Nov 12 23:35:52 2012 -0500
>>
>> external-arago-sdk-toolchain: package up gdb from the toolchain as well
>>
>> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
>>
>> ---
>>
>> .../meta/external-arago-sdk-toolchain.bb           |   25 +++++++++++++++++++-
>> 1 files changed, 24 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta-arago-extras/recipes-core/meta/external-arago-sdk-toolchain.bb b/meta-arago-extras/recipes-core/meta/external-arago-sdk-toolchain.bb
>> index 4b16bc1..abd1caf 100644
>> --- a/meta-arago-extras/recipes-core/meta/external-arago-sdk-toolchain.bb
>> +++ b/meta-arago-extras/recipes-core/meta/external-arago-sdk-toolchain.b
>> +++ b
>> @@ -2,7 +2,7 @@ inherit cross-canadian
>>
>> require external-arago-toolchain.inc
>>
>> -PR = "r2"
>> +PR = "r3"
>>
>> INHIBIT_PACKAGE_STRIP = "1"
>> INHIBIT_DEFAULT_DEPS = "1"
>> @@ -16,15 +16,18 @@ LIC_FILES_CHKSUM = "\  "
>>
>> INSANE_SKIP_gcc-cross-canadian-arm = "dev-so"
>> +INSANE_SKIP_gdb-cross-canadian-arm = "dev-so"
>> INSANE_SKIP_binutils-cross-canadian-arm = "dev-so"
>>
>> PROVIDES = "\
>>    gcc-cross-canadian-arm \
>> +    gdb-cross-canadian-arm \
>>    binutils-cross-canadian-arm \
>> "
>>
>> PACKAGES = "\
>>    gcc-cross-canadian-arm \
>> +    gdb-cross-canadian-arm \
>>    binutils-cross-canadian-arm \
>> "
>>
>> @@ -32,6 +35,7 @@ PACKAGES = "\
>> bindir = "${exec_prefix}/bin/"
>> libdir = "${exec_prefix}/lib/"
>> libexecdir = "${exec_prefix}/libexec/"
>> +datadir = "${exec_prefix}/share/"
>>
>> gcclibdir = "${libdir}/gcc"
>>
>> @@ -55,6 +59,14 @@ FILES_gcc-cross-canadian-arm = "\
>>    ${libexecdir}/* \
>> "
>>
>> +FILES_gdb-cross-canadian-arm = "\
>> +    ${bindir}/${TARGET_PREFIX}gdb \
>> +    ${bindir}/${TARGET_PREFIX}gdbtui \
>> +    ${datadir}/gdb/* \
>> +    ${datadir}/info/* \
>> +    ${datadir}/man/man1/${TARGET_PREFIX}* \ "
>> +
>> FILES_binutils-cross-canadian-arm = "\
>>    ${prefix}/${ARAGO_TARGET_SYS}/bin/ld \
>>    ${prefix}/${ARAGO_TARGET_SYS}/bin/addr2line \ @@ -91,14 +103,17 @@ FILES_binutils-cross-canadian-arm = "\  "
>>
>> DESCRIPTION_gcc-cross-canadian-arm = "The GNU cc and gcc C compilers"
>> +DESCRIPTION_gdb-cross-canadian-arm = "gdb - GNU debugger"
>> DESCRIPTION_binutils-cross-canadian-arm = "A GNU collection of binary utilities"
>>
>> LICENSE = "${ARG_LIC_LIBC}"
>> LICENSE_gcc-cross-canadian-arm = "${ARG_LIC_GCC}"
>> +LICENSE_gdb-cross-canadian-arm = "${ARG_LIC_GDB}"
>> LICENSE_binutils-cross-canadian-arm = "${ARG_LIC_BFD}"
>>
>> PKGV = "${ARG_VER_MAIN}"
>> PKGV_gcc-cross-canadian-arm = "${ARG_VER_GCC}"
>> +PKGV_gdb-cross-canadian-arm = "${ARG_VER_GDB}"
>> PKGV_binutils-cross-canadian-arm = "${ARG_VER_BFD}"
>>
>> do_install() {
>> @@ -109,6 +124,9 @@ do_install() {
>>    install -d ${D}${libdir}/ldscripts
>>    install -d ${D}${includedir}
>>    install -d ${D}${libexecdir}
>> +    install -d ${D}${datadir}/gdb
>> +    install -d ${D}${datadir}/info
>> +    install -d ${D}${datadir}/man/man1
>>    install -d ${D}${gcclibdir}/${ARAGO_TARGET_SYS}/${ARG_VER_GCC}/include
>>    install -d ${D}${prefix}/i686-linux
>>
>> @@ -118,6 +136,11 @@ do_install() {
>>    cp -a ${TOOLCHAIN_PATH}/bin/${TARGET_PREFIX}{gcov,gccbug,gcc,g++,cpp} ${D}${bindir}
>>    cp -a ${TOOLCHAIN_PATH}/libexec/* ${D}${libexecdir}
>>
>> +    cp -a ${TOOLCHAIN_PATH}/bin/${TARGET_PREFIX}{gdb,gdbtui} ${D}${bindir}
>> +    cp -a ${TOOLCHAIN_PATH}/share/gdb/* ${D}${datadir}/gdb/
>> +    cp -a ${TOOLCHAIN_PATH}/share/info/* ${D}${datadir}/info/
>> +    cp -a ${TOOLCHAIN_PATH}/share/man/man1/${TARGET_PREFIX}*
>> +${D}${datadir}/man/man1/
>> +
>>    cp -a ${TOOLCHAIN_PATH}/${ARAGO_TARGET_SYS}/bin/{ld,addr2line,objcopy,readelf,strip,nm,ranlib,gprof,as,c++filt,ar,strings,objdump,size} ${D}${prefix}/${ARAGO_TARGET_SYS}/bin
>>    cp -a ${TOOLCHAIN_PATH}/include/*.h ${D}${includedir}
>>    cp -a ${TOOLCHAIN_PATH}/lib/ldscripts/* ${D}${libdir}/ldscripts
>>
>> _______________________________________________
>> arago-commits mailing list
>> arago-commits@arago-project.org
>> http://arago-project.org/cgi-bin/mailman/listinfo/arago-commits
>> _______________________________________________
>> meta-arago mailing list
>> meta-arago@arago-project.org
>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
_______________________________________________
meta-arago mailing list
meta-arago@arago-project.org
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

[-- Attachment #2: Type: text/html, Size: 10855 bytes --]

  parent reply	other threads:[~2012-11-14  3:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121113044034.9EA3D529AE@arago-project.org>
2012-11-13 13:31 ` [arago-commits] Denys Dmytriyenko : external-arago-sdk-toolchain: package up gdb from the toolchain as well Cooper Jr., Franklin
2012-11-14  2:27   ` Denys Dmytriyenko
2012-11-14  2:44     ` Cooper Jr., Franklin
2012-11-14  3:56       ` Denys Dmytriyenko
2012-11-14  3:58       ` Maupin, Chase [this message]
2012-11-14  4:05         ` Denys Dmytriyenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DA9820EE-0593-4552-A1FC-6167B44C2CB9@ti.com \
    --to=chase.maupin@ti.com \
    --cc=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.