From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] eaccelerator
Date: Wed, 19 Sep 2012 22:10:12 +0200 [thread overview]
Message-ID: <20120919221012.3646aa7b@skate> (raw)
In-Reply-To: <CAE9DZURE9s7eH_N2vhv1wK73Pip9wAVDmYtbU8Ynxn_3XpGpdQ@mail.gmail.com>
Dear Dallas Clement,
On Wed, 19 Sep 2012 10:34:51 -0500, Dallas Clement wrote:
> Can any of you provide guidance on the proper way to build a PHP
> extension such as eaccelerator? Should I create its own .mk or should
> I modify the php.mk to extract into $(PHP_DIR)/ext and make all
> together? I have examined the eaccelerator tar ball contents and
> there is no configure script present, so I am assuming the intent is
> for it to be built with PHP. Would appreciate any tips you might
> have.
The compilation instructions are detailed in
https://github.com/eaccelerator/eaccelerator/blob/master/README.
Apparently, you need to call phpize (which comes with PHP, but I don't
know if we build it for the host at the moment, I don't think so), it
probably generates a configure script, that you execute, and then you
can build the extension.
For sure, this extension needs to be a separate package from the php
package.
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:[~2012-09-19 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 15:34 [Buildroot] eaccelerator Dallas Clement
2012-09-19 20:10 ` Thomas Petazzoni [this message]
2012-09-19 20:36 ` Dallas Clement
2012-09-20 9:10 ` Thomas Petazzoni
2012-09-20 16:37 ` Dallas Clement
[not found] ` <CAE9DZUSLuiDgK0fPGoSE=bBQLinvDRKFLBq6ifzPxJwpMBD-zQ@mail.gmail.com>
2012-09-20 18:44 ` Thomas Petazzoni
2012-09-20 23:02 ` Dallas Clement
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=20120919221012.3646aa7b@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 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.