Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10566] New: php.mk is missing option --with-pgsql
Date: Fri, 08 Dec 2017 19:13:37 +0000	[thread overview]
Message-ID: <bug-10566-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=10566

            Bug ID: 10566
           Summary: php.mk is missing option --with-pgsql
           Product: buildroot
           Version: 2017.02.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: Peter.Pashkov at utas.utc.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

When tried to install zabbix server using PostgreSQL database the setup page
gave an error message "At least one of MySQL, PostgreSQL, Oracle or IBM DB2
should be supported."
This pointed out to that php was configured without "--with-pgsql". The php.mk
file that is in charge of setting different configuration options to
"configure" script doesn't have the option at all.

The version of buildroot in use is: buildroot-2017.02.6

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-12-08 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 19:13 bugzilla at busybox.net [this message]
2018-01-10 20:04 ` [Buildroot] [Bug 10566] php.mk is missing option --with-pgsql bugzilla at busybox.net
2018-01-10 20:10 ` bugzilla at busybox.net
2018-01-10 20:15 ` bugzilla at busybox.net
2018-01-16 22:29 ` bugzilla at busybox.net
2018-01-16 22:29 ` bugzilla at busybox.net
2019-08-11 23:27 ` bugzilla at busybox.net

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=bug-10566-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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