From: Carmelo AMOROSO <carmelo.amoroso@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem #including <string>
Date: Wed, 29 Aug 2007 12:12:14 +0200 [thread overview]
Message-ID: <46D5467E.5010802@st.com> (raw)
In-Reply-To: <46D54452.7080204@carallon.com>
Will Wagner wrote:
> Hello,
>
> I have built buildroot with the attached config for x86, with support
> for c++.
>
> However whenever I include <string> I get errors in my code because it
> seems somewhere in <string> it is #defining index.
>
> If I attempt to compile the following code:
>
> #ifdef index
> #error foo
> #endif
>
> #include <string>
>
> #ifdef index
> #error bar
> #endif
>
> void do_nothing()
> {
> }
>
> Then I get the second error.
>
> I have tried searching through the headers to find where the #define
> index is but I have been unable to find it. Can anyone suggest the
> best way of locating where index is being erroneously defined?
>
> Many thanks,
>
> Will.
>
Probably you have uClibc built with SUSv3_MACRO defined (among these
there is index )
Cheers,
Carmelo
> ------------------------------------------------------------------------
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2007-08-29 10:12 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 [this message]
[not found] ` <46D573C8.7060701@carallon.com>
2007-08-29 13:41 ` Carmelo AMOROSO
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=46D5467E.5010802@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