From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Trouble compiling Qt with CodeSourcery 2011.09-50 external toolchain
Date: Thu, 09 Aug 2012 17:32:39 +0200 [thread overview]
Message-ID: <5023D817.4070104@lucaceresoli.net> (raw)
In-Reply-To: <CALo-6+jm1Erc88r0q9fMx0z8oNtuygF1APZYurfATRoN5uLrsA@mail.gmail.com>
Charles Krinke wrote:
> In trying to use the CodeSourcery 2011.09-50 external toolchain which
> I downloaded and referenced externally, I get bolloxed up in Qt
> compile with "output number X not directly addressable" and wonder if
> someone could suggest a reason why?
Are you sure you mean 2011.09 and not 2010.09?
I had a similar issue with Qt and Sourcery 2010.09. It's reported, with
a workaround, here: https://bugs.busybox.net/show_bug.cgi?id=5408.
Let us know your results, adding a comment on the bug tracker.
Luca
prev parent reply other threads:[~2012-08-09 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 14:36 [Buildroot] Trouble compiling Qt with CodeSourcery 2011.09-50 external toolchain Charles Krinke
2012-07-17 14:43 ` Thomas Petazzoni
2012-08-09 15:32 ` Luca Ceresoli [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=5023D817.4070104@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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