All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15814] C++ not supported by bootlin toolchain
Date: Sat, 07 Oct 2023 08:52:32 +0000	[thread overview]
Message-ID: <bug-15814-163-F627IXFUUd@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15814-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15814

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998@free.fr
         Resolution|---                         |INVALID

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
stsp, All,

> So it seems the config doesn't allow to
> enable C++ support together with selecting
> bootlin toolchain.

Have you actually tried to enable a package written in C++?

The symbols you reference are just intermediate symbols, that ultimately
select BR2_INSTALL_LIBSTDCPP, which is the one symbol that represents
whether C++ is available in the toolchain. All Bootlin toolchains with
C++ support do select that symbol.

> Is there anything that can be done with that?

No, because it is already working as expected.

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

       reply	other threads:[~2023-10-07  8:52 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 ` bugzilla [this message]
2023-10-07  8:57 ` [Buildroot] [Bug 15814] C++ not supported by bootlin toolchain 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
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-F627IXFUUd@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.