From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] HOWTO build a completely static php?
Date: Tue, 26 Feb 2013 20:07:24 +0100 [thread overview]
Message-ID: <20130226200724.44b6692f@skate> (raw)
In-Reply-To: <512CF95D.3050202@linuxtoys.org>
Dear Bob Smith,
On Tue, 26 Feb 2013 10:05:17 -0800, Bob Smith wrote:
> I would like to build a completely static executable for
> php. What is the easiest way to do this?
>
> A separate, but easier to solve problem, will be to add
> a postgresql binding to it. The goal is to run it on an
> Android system as a one-off project.
You don't have to build things statically to make things work in
Android. You can just add uClibc or glibc to Android, next to Bionic.
Just last week, Maxime Ripard and myself have helped Karim Yaghmour
integrate a root filesystem generated by Buildroot directly into
Android, it worked like a charm. Basically, just build a Buildroot
system as usual (select a tarball root filesystem image), and then
extract this tarball in the root directory of the Android filesystem.
Since a Linux filesystem and Android filesystem use completely
different paths for the libraries and binaries, it just works without
any problem.
Karim has written a small modification to the Android build system to
automate the integration of such a Buildroot generated filesystem. He
has said he will share this small piece of code, but I know he is busy
traveling at the moment, so he might takes a bit of time before it gets
published.
Best regards,
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:[~2013-02-26 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 18:05 [Buildroot] HOWTO build a completely static php? Bob Smith
2013-02-26 19:07 ` Thomas Petazzoni [this message]
2013-02-26 19:24 ` Bob Smith
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=20130226200724.44b6692f@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