From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15814] C++ not supported by bootlin toolchain
Date: Sat, 07 Oct 2023 12:16:07 +0000 [thread overview]
Message-ID: <bug-15814-163-pZVo2KrFjO@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15814-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15814
--- Comment #7 from Yann E. MORIN <yann.morin.1998@free.fr> ---
stsp, All,0
> Treating such things anyhow but
> bugs, is quite unhelpful. :)
> If you know "make clean" is now needed,
> then please tell me so on exit from
> menuconfig. Either by printing such a
> message, or, better yet, asking to run
> "make clean" (ok/cancel) before exiting
> TUI.
Rebuilding from scratch after menuconfig is not always required; if one
just adds a new package which has no dependency and is not the dependency
of another, then this is usually OK, and running "make" again is often
just enough.
So no, this is not a bug, and this is expected behaviour. It has limitations,
and those are thoroughly explained in the manual.
Regards,
Yann E. MORIN.
--
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:[~2023-10-07 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15814-163@https.bugs.busybox.net/>
2023-10-07 8:52 ` [Buildroot] [Bug 15814] C++ not supported by bootlin toolchain bugzilla
2023-10-07 8:57 ` bugzilla
2023-10-07 9:26 ` bugzilla
2023-10-07 10:35 ` bugzilla
2023-10-07 10:45 ` bugzilla
2023-10-07 11:02 ` bugzilla
2023-10-07 12:16 ` bugzilla [this message]
2023-10-07 12:24 ` 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-15814-163-pZVo2KrFjO@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