From: Carmelo AMOROSO <carmelo.amoroso@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem #including <string>
Date: Wed, 29 Aug 2007 15:41:36 +0200 [thread overview]
Message-ID: <46D57790.1040204@st.com> (raw)
In-Reply-To: <46D573C8.7060701@carallon.com>
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?
>
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.
Carmelo
P.S.
CC the buildroot ML to get other feedbacks it is the case
next prev parent reply other threads:[~2007-08-29 13:41 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 [this message]
2007-09-01 16:34 ` Bernhard Fischer
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=46D57790.1040204@st.com \
--to=carmelo.amoroso@st.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