From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10341] gdb install of py files when using buildroot toolchain includes build path
Date: Tue, 31 Oct 2017 21:15:30 +0000 [thread overview]
Message-ID: <bug-10341-163-ykC77kH36j@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10341-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10341
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Could you provide a defconfig that exhibits the problem?
The following defconfig builds host-gdb with Python support, but I don't have
this auto-load folder in host/share/gdb/.
BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2017.05-1078-g95b1dae.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_4_9=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_10=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_PACKAGE_HOST_GDB=y
BR2_PACKAGE_HOST_GDB_PYTHON=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
# BR2_TARGET_ROOTFS_TAR is not set
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-10-31 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:03 [Buildroot] [Bug 10341] New: gdb install of py files when using buildroot toolchain includes build path bugzilla at busybox.net
2017-10-31 21:15 ` bugzilla at busybox.net [this message]
2018-06-06 14:21 ` [Buildroot] [Bug 10341] " bugzilla at busybox.net
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=bug-10341-163-ykC77kH36j@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox