From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16000] GDB will not build
Date: Wed, 20 Mar 2024 21:42:50 +0000 [thread overview]
Message-ID: <bug-16000-163-A0tJQ0QTXw@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 #4 from Peter Seiderer <ps.report@gmx.net> ---
Please read '22.6. Reporting issues/bugs or getting help' ([1]) and '8.2.
Understanding when a full rebuild is necessary' ([2]), please try to provide
and (minimal) .config or defconfig file reproducing your failure on a complete
build (e.g. 'make clean && make gdb')...
Which toolchain? Another reference to the mentioned patch, see [3]...
[1] https://buildroot.org/downloads/manual/manual.html#reporting-bugs
[2] https://buildroot.org/downloads/manual/manual.html#full-rebuild
[3]
https://github.com/crosstool-ng/crosstool-ng/blob/master/packages/gcc/13.2.0/0013-libgcc-Exclude-UCLIBC-from-GLIBC-thread-check.patch
--
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-03-20 21:42 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 [this message]
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-A0tJQ0QTXw@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