From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qtopia4 Failure
Date: Sun, 23 Sep 2007 17:25:45 +0100 [thread overview]
Message-ID: <d6cda7730709230925t2cbe4dc0q149a98cdce2a0350@mail.gmail.com> (raw)
In-Reply-To: <1190563965.7015.21.camel@elrond.atmel.sweden>
I built for AVR32. I even have some patches here that I'm not sure
were applied or not. I haven't updated the svn for a little while as I
have been working on the application lately.
It seams like the include path issue, if I'm not mistaken there is
some header (uClib I guess, not sure, and not Qt's) that does a
#define index
which is very bad :P
On 9/23/07, Ulf Samuelsson <ulf@atmel.com> wrote:
> Anyone building qtopia?
> I get (when compiling with gcc-4.2.1/binutils-2.18/uclibc-0.9.29):
>
>
> arm-linux-g++ -c -pipe -g -g -fvisibility=hidden
> -fvisibility-inlines-hidden -Wall -W -D_REENTRANT -fPIC -DQT_SHARED
> -DTSLIBMOUSEHANDLER_DEBUG -DQT_BUILD_CORE_LIB -DQT_NO_CAST_TO_ASCII
> -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT
> -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE
> -I../../mkspecs/qws/linux-arm-g++ -I. -I../../include
> -I../../include/QtCore -Iglobal -I.moc/debug-shared-emb-arm
> -I.uic/debug-shared-emb-arm
> -o .obj/debug-shared-emb-arm/qresource_iterator.o
> io/qresource_iterator.cpp
> io/qresource_iterator.cpp:46:66: error: macro "index" requires 2
> arguments, but only 1 given
> io/qresource_iterator.cpp: In constructor
> 'QResourceFileEngineIterator::QResourceFileEngineIterator(QFlags<QDir::Filter>, const QStringList&)':
> io/qresource_iterator.cpp:47: error: expected `(' before '{' token
> make[2]: *** [.obj/debug-shared-emb-arm/qresource_iterator.o] Fel 1
>
>
> when compiling "src/corelib/io/qresource_iterator.cpp"
> This is the line giving problems.
>
> QResourceFileEngineIterator::QResourceFileEngineIterator(QDir::Filters
> filters,
> const
> QStringList &filterNames)
> : QAbstractFileEngineIterator(filters, filterNames), index(-1)
> {
> }
>
>
>
> Best Regards
> Ulf Samuelsson
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2007-09-23 16:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 16:12 [Buildroot] Qtopia4 Failure Ulf Samuelsson
2007-09-23 16:25 ` Thiago A. Corrêa [this message]
2007-09-23 23:55 ` Adam Hawes
2007-09-24 0:56 ` Thiago A. Corrêa
2007-09-24 1:06 ` Adam Hawes
2007-09-24 1:41 ` Thiago A. Corrêa
2007-09-24 2:16 ` Adam Hawes
2007-09-24 3:43 ` Thiago A. Corrêa
2007-09-24 3:55 ` Adam Hawes
2007-09-24 8:13 ` Bernhard Fischer
2007-09-24 12:59 ` Thiago A. Corrêa
2007-09-24 13:22 ` Bernhard Fischer
2007-09-24 15:13 ` Ulf Samuelsson
2007-09-24 15:34 ` Thiago A. Corrêa
2007-09-24 23:31 ` Adam Hawes
2007-09-25 0:09 ` [Buildroot] MPlayer using LEGACY Functions (was: Qtopia4 Failure) Adam Hawes
2007-09-25 7:27 ` [Buildroot] Qtopia4 Failure Bernhard Fischer
2007-09-24 8:12 ` Ulf Samuelsson
2007-09-24 9:12 ` Bernhard Fischer
2007-09-24 9:34 ` Ulf Samuelsson
2007-09-24 12:27 ` Bernhard Fischer
2007-09-24 14:25 ` Ulf Samuelsson
2007-09-24 14:51 ` Ulf Samuelsson
2007-09-24 18:41 ` Bernhard Fischer
2007-09-24 8:06 ` Ulf Samuelsson
2007-09-24 8:02 ` Ulf Samuelsson
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=d6cda7730709230925t2cbe4dc0q149a98cdce2a0350@mail.gmail.com \
--to=thiago.correa@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