From: webmaster@zutroll.de
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] PHP7.3 support? Since 5.6.x is End Of Life
Date: Fri, 22 Feb 2019 12:39:53 +0100 [thread overview]
Message-ID: <85c097d5c993744f42d0f7f3bccede26@zutroll.de> (raw)
In-Reply-To: <7D174A0F-FD8E-4AB5-A194-74C86957C950@diehl.com>
Am 2019-02-22 10:24, schrieb Thorsten LIEPERT:
> Hello,
>
> A while back I already did a transition to PHP7.2 but harnet time to
> populate it here yet.
>
> I just tried to upgrade to 7.3.2 and it work without any problems.
> I’ll attach my patches. I also did clean up the lighted rule and
> removed php5 with this stack.
>
>
>
>
>
>
> Thorsten Liepert
> Development Software
>
> Phone +49 911 97479 839 | thorsten.liepert@diehl.com
>
> Diehl Connectivity Solutions GmbH
> Stephanstraße 49
> 90478 Nürnberg
> https://www.diehl-cs.com
Hello,
thanks for your patches, has mysql be gone in the php7? its missing in
your files.
Also it is not linking against the shared library from ptxdist it is
still php bundled sqlite 3.24.0.
But anyway very good starting point, now with correct config in files.
Should:
--with-config-file-path=/etc/php7 \
be
--with-config-file-path=/etc/php \
regarding the make install?
Regards
>
>> Am 22.02.2019 um 09:59 schrieb webmaster@zutroll.de:
>>
>> Hello,
>>
>> PHP 7.3.2 seems to work well with sqlite, since it uses its own
>> bundeled sqlite3.
>> I use with --with-sqlite3, so not specifing any special src.
>>
>> I have attached my modified php make file.
>> I kept the naming php5.make due limited time, but the target file is
>> now named php instead of php5.
>>
>> Hope this helps to getting this working again with ptxdist builded
>> sqlite3.so
>>
>> Regards
>>
>>
>>
>> Am 2019-02-22 09:28, schrieb Michael Olbrich:
>>> Hi,
>>> On Mon, Feb 11, 2019 at 03:31:38PM +0100, Simon Agostini wrote:
>>>> is PHP 7.3 suppot planned?
>>> I'd be happy to accept patches for this, but I currently don't have
>>> plans
>>> to do this myself.
>>>> I tried to adapt the PHP5 make file but I get:
>>>> /build-target/php-7.3.2/ext/pdo_sqlite/libsqlite/sqlite3.c',
>>>> needed by
>>>> 'ext/pdo_sqlite/libsqlite/sqlite3.lo'. Stop.
>>>> with --with-sqlite3=$(PTXDIST_SYSROOT_TARGET)/usr
>>>> if I remove the dir path it works, but I think this shall not be
>>>> the
>>>> optimal build!?
>>> The php5 package is not maintained very well. It has no priority for
>>> me and
>>> other than the occasional minor version bump, nobody else seems to
>>> care
>>> either.
>>> I'm guessing, that the php build system is broken and there is some
>>> mixup
>>> about internal vs. system sqlite. Do you get sqlite support at all if
>>> you
>>> remove --with-sqlite3=...?
>>> Michael
>> <php5.make>_______________________________________________
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-02-22 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 9:24 Thorsten LIEPERT
2019-02-22 11:39 ` webmaster [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-22 11:50 Thorsten LIEPERT
[not found] <d548c3cbcb30e579ec8938218ff79876@zutroll.de>
2019-02-11 14:31 ` Simon Agostini
2019-02-22 8:28 ` Michael Olbrich
2019-02-22 8:59 ` webmaster
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=85c097d5c993744f42d0f7f3bccede26@zutroll.de \
--to=webmaster@zutroll.de \
--cc=ptxdist@pengutronix.de \
/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