From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16000] New: GDB will not build
Date: Sat, 16 Mar 2024 16:31:41 +0000 [thread overview]
Message-ID: <bug-16000-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=16000
Bug ID: 16000
Summary: GDB will not build
Product: buildroot
Version: 2024.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: fli4l@franke-prem.de
CC: buildroot@uclibc.org
Target Milestone: ---
On my system (Debian 11 System gcc 10.2.1-6) with gcc-12.3 active in buildroot
will the package gdb not be build.
Only when i install the (old) patch
0004-libgcc-Exclude-UCLIBC-from-GLIBC-thread-check.patch
the gdb-package (13.2) will be build fine.
I have not found any hint, why this patch was deleted between Buildroot
2023.08.3 and the actual version 2024.02.
I will also not know or have tested, if the patch will be need by some other
versions of gcc.
So this Bug-Report is more as information to you
--
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 reply other threads:[~2024-03-16 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 16:31 bugzilla [this message]
2024-03-16 17:27 ` [Buildroot] [Bug 16000] GDB will not build 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox