From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16000] GDB will not build
Date: Mon, 01 Apr 2024 11:40:16 +0000 [thread overview]
Message-ID: <bug-16000-163-qWpdVtBgYi@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-16000-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=16000
--- Comment #7 from Peter Seiderer <ps.report@gmx.net> ---
Do not tailor the configuration by hand, use 'make savedefconfig' instead, I
doubt your given config reproduces the problem as neither BR2_PACKAGE_HOST_GDB
nor BR2_PACKAGE_GDB are set...
Problem not reproducable on openSUSE Tumbleweed with the following defconfig
for me (using buildroot git master):
BR2_x86_nocona=y
BR2_TOOLCHAIN_BUILDROOT_UCLIBC=y
BR2_KERNEL_HEADERS_6_1=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PTHREAD_DEBUG=y
BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
BR2_BINUTILS_VERSION_2_40_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_HOST_GDB=y
BR2_CCACHE=y
BR2_PER_PACKAGE_DIRECTORIES=y
BR2_SSP_REGULAR=y
BR2_RELRO_PARTIAL=y
BR2_PACKAGE_GDB=y
BR2_PACKAGE_GDB_SERVER=y
BR2_PACKAGE_GDB_DEBUGGER=y
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-01 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 16:31 [Buildroot] [Bug 16000] New: GDB will not build bugzilla
2024-03-16 17:27 ` [Buildroot] [Bug 16000] " bugzilla
2024-03-17 9:44 ` bugzilla
2024-03-18 12:46 ` bugzilla
2024-03-20 21:42 ` bugzilla
2024-03-21 16:49 ` bugzilla
2024-03-22 18:31 ` bugzilla
2024-04-01 11:40 ` bugzilla [this message]
2024-06-15 15:23 ` bugzilla
2024-06-15 15:23 ` bugzilla
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-16000-163-qWpdVtBgYi@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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.