From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] php: force cross-compilation
Date: Mon, 25 Jun 2012 10:06:41 +0200 [thread overview]
Message-ID: <20120625100641.7850a1a2@skate> (raw)
In-Reply-To: <87k3yv95r9.fsf@macbook.be.48ers.dk>
Le Mon, 25 Jun 2012 10:04:42 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> True. Looking at the autobuilder results it seems htop has a similar
> problem (I don't quite understand why it cannot find /proc/stat on your
> builder though):
>
> http://autobuild.buildroot.net/results/7d670efa247dfcbcbf6cd088d1157779af441333/build-end.log
I'm building in a chroot, and I don't have /proc mounted. I'm not sure
it's a useful scenario to support?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-25 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 22:22 [Buildroot] [PATCH] php: force cross-compilation Thomas Petazzoni
2012-06-23 20:11 ` Peter Korsgaard
2012-06-25 7:12 ` Thomas Petazzoni
2012-06-25 8:04 ` Peter Korsgaard
2012-06-25 8:06 ` Thomas Petazzoni [this message]
2012-06-25 8:50 ` Peter Korsgaard
2012-06-25 9:06 ` Thomas Petazzoni
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=20120625100641.7850a1a2@skate \
--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