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 10:46:15 +0200 [thread overview]
Message-ID: <3a95180b-c9f8-4a23-cac8-0cf8433e1b6d@ipfire.org> (raw)
In-Reply-To: <1492589579.11653.66.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2493 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
>
> ??
Hopefully: Done. ;-)
Now on 'next', "git log" shows:
...
commit 1e885a0f4dd5549a28d1fe0122817f112f97d26a
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Wed Apr 19 10:37:30 2017 +0200
Revert "gdbm: update to 1.13"
This reverts commit dc539daf8823ef97c931f12b514453c25e867c45.
commit f6af7e75988067fe90feac21943e98b98e28be56
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Wed Apr 19 10:09:27 2017 +0200
php 5.3.27: Source format improvements
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
commit a0217fd2b5d8f0675ba27aed5605ad4da8794d57
Merge: 57cd622c0 4c6b20349
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Tue Apr 18 22:28:18 2017 +0200
Merge branch 'next' of ssh://git.ipfire.org/pub/git/ipfire-2.x into next
commit 4c6b2034921fcfbff5fc92ab567c56c47fe99137
Author: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
Date: Tue Apr 18 14:56:05 2017 +0200
git: update to 2.12.1
Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
...
> configure also writes a log file called config.log with some debugging
> information in case the script aborts.
Found. Last lines were:
...
configure:29303: gcc -o conftest -O2 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fPIC -fstack-protector-strong --param=ssp-buffer-size=4
-march=i586 -mtune=generic -fomit-frame-pointer -fvisibility=hidden
-lcurl conftest.c -lcurl -lcurl -lbz2 -lz -lrt -lm -ldl -lnsl -lxml2
-lz -lm -ldl -lcurl 1>&5
configure:30177: checking for QDBM support
...
Devel is running...
Best,
Matthias
> -Michael
>
> On Wed, 2017-04-19 at 09:16 +0200, Matthias Fischer wrote:
>> Hi,
>>
>> current 'next' always fails with the same error while building 'php 5.3.27':
>>
>> ...
>> checking for curl_multi_strerror in -lcurl... yes
>> checking for QDBM support... no
>> configure: error: DBA: Could not find necessary header file(s).
>> make: *** [php:81: /usr/src/log/php-5.3.27] Error 1
>> ...
>>
>> This seems to be related to Berkeley, but I can't find the reason. I
>> tried several times, but had no luck.
>>
>> Can anyone confirm?
>>
>> Best,
>> Matthias
>
next prev parent reply other threads:[~2017-04-19 8:46 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 [this message]
2017-04-19 11:27 ` Matthias Fischer
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=3a95180b-c9f8-4a23-cac8-0cf8433e1b6d@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