From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem #including <string>
Date: Sat, 1 Sep 2007 18:34:35 +0200 [thread overview]
Message-ID: <20070901163435.GN11697@aon.at> (raw)
In-Reply-To: <46D57790.1040204@st.com>
On Wed, Aug 29, 2007 at 03:41:36PM +0200, Carmelo AMOROSO wrote:
>Will Wagner wrote:
>> Carmelo AMOROSO wrote:
>>> Probably you have uClibc built with SUSv3_MACRO defined (among these
>>> there is index )
>>>
>>> Cheers,
>>> Carmelo
>>>> ------------------------------------------------------------------------
>>>>
>>
>> Thank you that fixed it. Why would you want the SUSv3_MACRO defined?
You don't want UCLIBC_SUSV3_LEGACY_MACROS nor UCLIBC_SUSV3_LEGACY, as a
general rule of thumb.
>>
>If some applications still call the legacy SUSv3 api, you may need
>to enable this option within uClibc, anyway, just to avoid name clashing
>when building some application (in your case), it's better to use
>the function version of the SUSv3 api and not macros... (if cannot patch
>the application)
>
>but if you doesn't needs this interfaces, safely remove this support
>from uClibc.
prev parent reply other threads:[~2007-09-01 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 10:02 [Buildroot] Problem #including <string> Will Wagner
2007-08-29 10:12 ` Carmelo AMOROSO
[not found] ` <46D573C8.7060701@carallon.com>
2007-08-29 13:41 ` Carmelo AMOROSO
2007-09-01 16:34 ` Bernhard Fischer [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=20070901163435.GN11697@aon.at \
--to=rep.dot.nop@gmail.com \
--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