Debian Bug report logs - #668835
php5: 5.4.1~rc1 fails to build from source on OpenSSL and PCRE libraries

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Frederik Vanrenterghem <frederik@vanrenterghem.biz>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: php5: 5.4.1~rc1 fails to build from source on OpenSSL and PCRE libraries

Date: Sat, 14 Apr 2012 20:58:24 +0200

Source: php5
Version: 5.4.1~rc1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
I tried installing php5 from source, but it fails when running debian/rules
binary upon checking for the OpenSSL libraries

configure: error: Cannot find OpenSSL's libraries
make: *** [configure-apache2-stamp] Error 1

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I removed the /usr from the debian/rules file, which makes the OpenSSL
configuration pass. It again breaks on PCRE though, which can't be resolved as
easily. I provided as directory /usr/include for the headers, but that makes it
break again in the next step:

checking for PCRE headers location... /usr/include
checking for PCRE library location... configure: error: Could not find
libpcre.(a|so) in /usr
make: *** [configure-apache2-stamp] Error 1




-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Message #10 received at 668835-done@bugs.debian.org (full text, mbox, reply):

From: Ondřej Surý <ondrej@debian.org>

To: Frederik Vanrenterghem <frederik@vanrenterghem.biz>, 668835-done@bugs.debian.org

Subject: Re: [php-maint] Bug#668835: php5: 5.4.1~rc1 fails to build from source on OpenSSL and PCRE libraries

Date: Sat, 14 Apr 2012 22:11:09 +0200

Hi Frederik,

the php builds just fine:

https://buildd.debian.org/status/package.php?p=php5

We can probably help you, if you provide the system setup (version,
how do you build the package, full logs, etc.), but it's not the bug
if you cannot build it on your system.

BTW: Did you do apt-get build-dep php5 ?

O.

On Sat, Apr 14, 2012 at 20:58, Frederik Vanrenterghem
<frederik@vanrenterghem.biz> wrote:
> Source: php5
> Version: 5.4.1~rc1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
>
>   * What led up to the situation?
> I tried installing php5 from source, but it fails when running debian/rules
> binary upon checking for the OpenSSL libraries
>
> configure: error: Cannot find OpenSSL's libraries
> make: *** [configure-apache2-stamp] Error 1
>
>   * What exactly did you do (or not do) that was effective (or
>     ineffective)?
> I removed the /usr from the debian/rules file, which makes the OpenSSL
> configuration pass. It again breaks on PCRE though, which can't be resolved as
> easily. I provided as directory /usr/include for the headers, but that makes it
> break again in the next step:
>
> checking for PCRE headers location... /usr/include
> checking for PCRE library location... configure: error: Could not find
> libpcre.(a|so) in /usr
> make: *** [configure-apache2-stamp] Error 1
>
>
>
>
> -- System Information:
> Debian Release: wheezy/sid
>  APT prefers unstable
>  APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
>
>
>
> _______________________________________________
> pkg-php-maint mailing list
> pkg-php-maint@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint



-- 
Ondřej Surý <ondrej@sury.org>

Send a report that this bug log contains spam.