Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] php: add --enable-mysqlnd to configure options when using mysql extensions
Date: Thu, 8 Sep 2016 17:52:05 +0200	[thread overview]
Message-ID: <20160908175205.4644bbc4@free-electrons.com> (raw)
In-Reply-To: <57D18809.8060701@gmail.com>

Hello,

On Thu, 8 Sep 2016 08:47:21 -0700, Ryan Coe wrote:

> I did build the system without my patch and was able to make everything 
> work after defining the MySql socket location in my php.ini file.  I 
> guess my patch can be marked rejected.  I was thrown off after looking 
> at the build log.  The statement "checking whether to enable mysqlnd... 
> no" from the configure step led me to think that that mysqlnd was not 
> getting built.  If desired, I can submit a patch to add --with-mysql-sock.

Yes, please. It would be good to have something that works out of the
box.

> On a side note, I am not using MySql version supplied by Buildroot.  I 
> have replaced MySql with MariaDB 10.0.

Patches adding MariaDB would be good too :)

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-08 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 15:48 [Buildroot] [PATCH 1/1] php: add --enable-mysqlnd to configure options when using mysql extensions Ryan Coe
2016-09-07 21:55 ` Thomas Petazzoni
2016-09-07 23:35   ` Floris Bos
2016-09-07 23:36     ` Ryan Coe
2016-09-08  0:06       ` Floris Bos
2016-09-08 15:47         ` Ryan Coe
2016-09-08 15:52           ` Thomas Petazzoni [this message]
2016-09-08 16:03           ` Floris Bos

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=20160908175205.4644bbc4@free-electrons.com \
    --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