Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem #including <string>
Date: Wed, 29 Aug 2007 11:02:58 +0100	[thread overview]
Message-ID: <46D54452.7080204@carallon.com> (raw)

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.

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Senior Project Engineer                  Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 14551 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070829/aa8a1ec6/attachment-0001.xml 

             reply	other threads:[~2007-08-29 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 10:02 Will Wagner [this message]
2007-08-29 10:12 ` [Buildroot] Problem #including <string> Carmelo AMOROSO
     [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=46D54452.7080204@carallon.com \
    --to=will_wagner@carallon.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