# 'make install' fails when --enable-memory-limit is present

- Thread: https://externals.io/message/10722
- Original archive: https://news-web.php.net/php.internals/10722
- Started by Zeev Suraski on 2004-06-23T11:31:48+00:00
- Messages: 6
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #10722 — Zeev Suraski — 2004-06-23T11:31:48+00:00

URL: https://externals.io/message/10722#10722

Apparently, the default 8MB are not enough for the PEAR installation, so it 
bails out when trying to 'make install'.  Changing php.ini doesn't have any 
effect since the installation uses -n to ignore any php.ini's.

My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves 
the problem on my Linux box, but I think we should go higher to be on the 
safe side).

Was this ever discussed?  Any reason not to do it?

Zeev

---

## #10725 — Derick Rethans — 2004-06-23T13:21:26+00:00

URL: https://externals.io/message/10722#10725 · In reply to: #10722

> Apparently, the default 8MB are not enough for the PEAR installation, so it
> bails out when trying to 'make install'.

Those default 8MB works for me...

> My suggestion - add -dmemory_limit=32M to PEAR_INSTALL_FLAGS (16M solves
> the problem on my Linux box, but I think we should go higher to be on the
> safe side).

We prolly should highen the limit to a default 16M too for PHP 5.

Derick

---

## #10727 — Zeev Suraski — 2004-06-23T14:08:09+00:00

URL: https://externals.io/message/10722#10727 · In reply to: #10722

At 16:21 23/06/2004, Derick Rethans wrote:
>
>
> > […]
>
>Those default 8MB works for me...

It does not for me.  Maybe it's related to some modules I'm using, but it 
actually doesn't work for in neither 4.2.3 nor 4.3.7.

> > […]
>
>We prolly should highen the limit to a default 16M too for PHP 5.

Why?

Zeev

---

## #10887 — Derick Rethans — 2004-07-03T11:13:50+00:00

URL: https://externals.io/message/10722#10887 · In reply to: #10727

> > […]
>
> Why?

Because applications in PHP 5 will most likely be larger usually due to
the better support for OO. People will earlier attempt to create more
complex applications and easily get over the low limit of 8MB.
Additionaly to this, you can't even resize a truecolor jpg (1600x1200)
at this moment with the default memory limit because GD uses about 4
times the amount of pixels in an image as memory.

regards,
Derick

---

## #10891 — Gareth Ardron — 2004-07-03T22:10:09+00:00

URL: https://externals.io/message/10722#10891 · In reply to: #10887

> > […]

> Because applications in PHP 5 will most likely be larger usually due to
> the better support for OO. People will earlier attempt to create more
> complex applications and easily get over the low limit of 8MB.
> Additionaly to this, you can't even resize a truecolor jpg (1600x1200)
> at this moment with the default memory limit because GD uses about 4
> times the amount of pixels in an image as memory.

To be honest, I've never understood why. php_imlib2 seems to run though
things fine with large files, and the structure of that is hardly
uncommon, and it's not like I've been doing anything dodgy with fudging
the zend api to get it to work right.

Might take a look at that one tomorrow.

---

## #10900 — Derick Rethans — 2004-07-05T06:46:42+00:00

URL: https://externals.io/message/10722#10900 · In reply to: #10891

> 
>
> > […]
>
> > […]
>
> To be honest, I've never understood why. php_imlib2 seems to run though
> things fine with large files, and the structure of that is hardly
> uncommon, and it's not like I've been doing anything dodgy with fudging
> the zend api to get it to work right.

It was changed for a reason, that is that people could GD to crash
servers quite easily. Removing this restriction is not an option.

Derick