From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' fails with error while building 'php'
Date: Wed, 19 Apr 2017 13:27:20 +0200 [thread overview]
Message-ID: <b18fc3e4-2654-ca78-1379-87e4f92fac50@ipfire.org> (raw)
In-Reply-To: <1492589579.11653.66.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On 19.04.2017 10:12, Michael Tremer wrote:
> Hi,
>
> could you try reverting
>
> http://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=dc539daf8823ef97c931f12b514453c25e867c45
>
> ??
Seems that this worked:
Build is still running without errors - 'php 5.3.27'' looged:
...
checking for curl_multi_strerror in -lcurl... yes
checking for QDBM support... no
checking for gdbm_open in -lgdbm... yes
checking for GDBM support... yes
checking for NDBM support... no
checking for DB4 minor version and patch level... ok
checking if dba can be used as shared extension... yes
checking for Berkeley DB4 support... yes
checking for Berkeley DB3 support... no
checking for Berkeley DB2 support... no
checking for DB1 support... no
checking for DBM support... no
checking for CDB support... builtin
...
Best,
Matthias
prev parent reply other threads:[~2017-04-19 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 7:16 Matthias Fischer
2017-04-19 8:12 ` Michael Tremer
2017-04-19 8:46 ` Matthias Fischer
2017-04-19 11:27 ` Matthias Fischer [this message]
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=b18fc3e4-2654-ca78-1379-87e4f92fac50@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/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