From: Ryan Coe <bluemrp9@gmail.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 08:47:21 -0700 [thread overview]
Message-ID: <57D18809.8060701@gmail.com> (raw)
In-Reply-To: <44537d0b-3c8b-edd0-1286-7f02e06694b9@je-eigen-domein.nl>
Floris, Thomas, All,
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.
On a side note, I am not using MySql version supplied by Buildroot. I
have replaced MySql with MariaDB 10.0.
On 09/07/2016 05:06 PM, Floris Bos wrote:
> On 09/08/2016 01:36 AM, Ryan Coe wrote:
>> Floris, Thomas, All,
>>
>> After applying my patch and rebuilding my system, I was still having
>> trouble.
>> I tracked it down to needing to set mysqli.default_socket in my
>> php.ini configuration.
>> This wasn't necessary before. I am going to revert my patch,
>> rebuild, and test again.
>> This might have been a false alarm. I will report back my findings.
>
> Hmm, perhaps there needs to be an --with-mysql-sock option added to
> set the default socket path to the right location for the buildroot
> MySQL server.
> I tend to use TCP instead for communication, so did not notice there
> may be something wrong with localhost through unix sockets.
>
>
> BTW did notice the MySQL server version shipped by buildroot is old
> and EOL.
> If you are planning to use that, you might want to look at upgrading it.
>
>
> Yours sincerely,
>
> Floris Bos
>
next prev parent reply other threads:[~2016-09-08 15:47 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 [this message]
2016-09-08 15:52 ` Thomas Petazzoni
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=57D18809.8060701@gmail.com \
--to=bluemrp9@gmail.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.