Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] PHP installation issues
Date: Thu, 25 Mar 2021 23:07:33 +0100	[thread overview]
Message-ID: <20210325230733.424f71cf@gmx.net> (raw)
In-Reply-To: <CAJ2YAHtdmiVyOZJNZbaWpGon15hznYV815QAhgKe4KY7YBBdmQ@mail.gmail.com>

Hello Alassane,

On Mon, 22 Mar 2021 15:13:47 +0100, Alassane <alassaneg@gmail.com> wrote:

> Hello,
>
> I have tried to generate a linux image with buildroot2020.11.1 but i'm
> having some issues after that.
> First of all, i've activated the external php extension "php-imagick" in
> target package after i run "make menuconfig".
> After that, i perform a full rebuild, reflash my sd card, launch my target
> but when i run the commande "php -m", it doesn't show me the "imagick"
> module...

	$ echo -e "[Imagick]\nextension=imagick.so" >> /etc/php.ini
	$ php -m
[PHP Modules]
Core
date
hash
imagick
pcre
posix
Reflection
session
SPL
standard
zlib

[Zend Modules]

Regards,
Peter

> And this is the following error message i'm facing when trying to run a
> program with the "php" command : *PHP Fatal error:  Uncaught Error: Class
> 'Imagick' not found*
>
> Also, i've selected the php "iconv" package and facing this error when i
> try to run my php program : *PHP Notice:  iconv(): Unknown error (22).*
>
> Do you know where these issues i'm facing could potentially come from?
>
> Kind regards
>
> Thank you
>
> Alassane

  parent reply	other threads:[~2021-03-25 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 14:13 [Buildroot] PHP installation issues Alassane
2021-03-25 12:44 ` Alassane
2021-03-25 22:07 ` Peter Seiderer [this message]
2021-03-25 22:28 ` Peter Seiderer
2021-03-25 22:41   ` Alassane

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=20210325230733.424f71cf@gmx.net \
    --to=ps.report@gmx.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