From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt error.
Date: Tue, 23 Mar 2010 10:39:22 +0100 [thread overview]
Message-ID: <20100323103922.1c5a2917@surf> (raw)
In-Reply-To: <f70863321003230201l3573678cx3eaf40954eec82dc@mail.gmail.com>
Hello,
On Tue, 23 Mar 2010 11:01:24 +0200
Muhammed ER <er.muhammed@gmail.com> wrote:
> In "qt.mk" file,
> I commet
> line 489 # -nomake examples \
> line 490 # -nomake demos \
Because you want examples and demos, right ?
> So it tries to install /usr which is in MY PC.
>
> I think,
> line 485: -prefix /usr \
> and it doesn't write because of permissions.
>
> will be $(TARGET)/usr or something like this.
No, -prefix /usr is ok, because Qt will be installed as /usr on the
target. -hostprefix is already set to $(STAGING_DIR)/usr, where it will
be installed by "make install".
Can you report the exact error message you're having ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-03-23 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 9:01 [Buildroot] Qt error Muhammed ER
2010-03-23 9:15 ` Paul Jones
2010-03-23 9:39 ` Thomas Petazzoni [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=20100323103922.1c5a2917@surf \
--to=thomas.petazzoni@free-electrons.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