Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Arno Welzel Newsgroups: comp.lang.php Subject: Re: .configure memory_limit building from source Date: Wed, 20 Jan 2016 06:20:09 +0100 Lines: 58 Message-ID: <569F1909.8020705@arnowelzel.de> References: <569CDBAE.2010406@arnowelzel.de> <569E70D8.9060304@arnowelzel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Trace: individual.net sqLg018wXOqtNm3IraFoNASWkdK0CvwWy51Ve0mKP1Vjq9lZIy Cancel-Lock: sha1:CyOZbxlALrK+1qU0AVzs4J7+a6g= In-Reply-To: Xref: csiph.com comp.lang.php:16318 crankypuss schrieb am 2016-01-19 um 23:25: > Arno Welzel wrote: > >> crankypuss schrieb am 2016-01-19 um 10:39: >> >>> Arno Welzel wrote: >>> >>>> crankypuss schrieb am 2016-01-18 um 10:38: >> [...] >>>>> If nobody knows, or there is no way to do it, I'll need to modify >>>>> the source, so I would appreciate clues in order to avoid that. >>>> >>>> You can't avoid that. PHP is not designed to be completely self >>>> contained without any configuration at all. >>> >>> Then it's not designed at all, it's just an accumulation of hacks. >> >> Which applies to most runtime environments of this kind since the >> "totally self contained" use case is usually never required. What's >> the problem of putting a php.ini beside the PHP binary? > > I don't see any need for a config file, all that stuff gets read in > during startup and replaces default values set by the build. > > The objective of this little sub-project is to have a one-lump- > application written in PHP, that runs under any linux distro, whether > PHP is installed or not. Originally I was thinking of modifying main() > so that it would determine how large the actual module is, then read the > remainder of the executable file and use that as it's PHP source. I > might still go with that approach, undetermined yet, but if I do I'll > need to strip some of the extraneous funtionality out. Than you also have to link every library statically to the PHP binary and omit nearly every extension - otherwise the binary may depend on certain runtime libaries which are not found on the distribution or they are not provided in the right version. Well - I think it's easier to use shell scripts then ;-). [...] >> But as the source is available feel free to build your own version >> which does whatever you need. > > Why thank you. I'm still a bit unclear about how "free" the > distribution of binaries is, what's actually required, etc. I'll figure > it out. See and . -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de