From: alexperl <alexondi@rambler.ru>
To: buildroot@busybox.net
Subject: [Buildroot] Qt fails to build
Date: Tue, 5 Jan 2010 06:09:40 -0800 (PST) [thread overview]
Message-ID: <27026618.post@talk.nabble.com> (raw)
In-Reply-To: <27026610.post@talk.nabble.com>
Besides,
I don't how would be better do it but if I compile target with x86_64 then
your patch fails too
I replace x86 -> x86_64 but maybe you know how do this right?
--
View this message in context: http://old.nabble.com/Qt-fails-to-build-tp26204234p27026618.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-01-05 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 20:37 [Buildroot] Qt fails to build Ormund Williams
2009-11-15 19:36 ` Peter Korsgaard
2009-11-15 20:28 ` Ormund Williams
2009-12-02 23:44 ` Ormund Williams
2009-12-03 10:31 ` Peter Korsgaard
2009-12-03 22:26 ` Ormund Williams
2009-12-04 0:38 ` Thiago A. Corrêa
2010-01-04 9:43 ` alexperl
2010-01-05 1:19 ` Ormund Williams
2010-01-05 13:27 ` alexperl
2010-01-05 14:09 ` alexperl [this message]
2010-01-05 16:58 ` Ormund Williams
2010-01-05 16:55 ` Ormund Williams
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=27026618.post@talk.nabble.com \
--to=alexondi@rambler.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.