From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] C++ and uclibc++ ??
Date: Tue, 27 Jan 2009 13:57:30 +0100 [thread overview]
Message-ID: <87iqo029fp.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <OFCA721249.B9DBD6C6-ONC125754B.004638F2-C125754B.00464B2A@gidi.it> (Alessio Stella's message of "Tue\, 27 Jan 2009 13\:47\:23 +0100")
>>>>> "Alessio" == Alessio Stella <Alessio.Stella@gidi.it> writes:
Alessio> Dear Mr.,
Alessio> I don't understand if the fact that uclibc++ is an
Alessio> alpha release should prevent me from writing in C++ and
Alessio> force me to write me in C code instead.
Alessio> The question is: does uclibc++ affect only some C++
Alessio> libraries and operands like for instance the console IO <<
Alessio> and >> ? or does it affect C++ code as a whole in its
Alessio> compiling and linking??
You seem to have sent this to the wrong list. This list is about
buildroot, not uclibc++ - And we don't have an uclibc++ package in
buildroot.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-01-27 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 12:47 [Buildroot] C++ and uclibc++ ?? Alessio.Stella at gidi.it
2009-01-27 12:57 ` Peter Korsgaard [this message]
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=87iqo029fp.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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