Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #16318
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: .configure memory_limit building from source |
| Date | 2016-01-20 06:20 +0100 |
| Message-ID | <569F1909.8020705@arnowelzel.de> (permalink) |
| References | (2 earlier) <n7iblc$s9s$1@dont-email.me> <569CDBAE.2010406@arnowelzel.de> <n7l03l$32s$4@dont-email.me> <569E70D8.9060304@arnowelzel.de> <n7mcva$s4l$1@dont-email.me> |
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 <https://secure.php.net/license/> and <https://secure.php.net/license/distrib-guidelines-code.php>. -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de http://fahrradzukunft.de
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
.configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-17 15:59 -0700
Re: .configure memory_limit building from source "Peter H. Coffin" <hellsop@ninehells.com> - 2016-01-17 21:56 -0600
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-18 02:38 -0700
Re: .configure memory_limit building from source "J.O. Aho" <user@example.net> - 2016-01-18 13:08 +0100
Re: .configure memory_limit building from source Michael Vilain <vilain@NOspamcop.net> - 2016-01-18 17:48 -0800
Re: .configure memory_limit building from source "J.O. Aho" <user@example.net> - 2016-01-19 06:56 +0100
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-19 02:37 -0700
Re: .configure memory_limit building from source Arno Welzel <usenet@arnowelzel.de> - 2016-01-18 13:33 +0100
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-19 02:39 -0700
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-19 03:54 -0700
Re: .configure memory_limit building from source Arno Welzel <usenet@arnowelzel.de> - 2016-01-19 18:27 +0100
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-19 14:38 -0700
Re: .configure memory_limit building from source Arno Welzel <usenet@arnowelzel.de> - 2016-01-20 06:11 +0100
Re: .configure memory_limit building from source Arno Welzel <usenet@arnowelzel.de> - 2016-01-19 18:22 +0100
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-19 15:25 -0700
Re: .configure memory_limit building from source Arno Welzel <usenet@arnowelzel.de> - 2016-01-20 06:20 +0100
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-20 03:02 -0700
Re: .configure memory_limit building from source Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-01-21 01:43 +0100
Re: .configure memory_limit building from source Arno Welzel <usenet@arnowelzel.de> - 2016-01-18 09:07 +0100
Re: .configure memory_limit building from source crankypuss <invalid@invalid.invalid> - 2016-01-18 02:39 -0700
Re: .configure memory_limit building from source Matthew Carter <m@ahungry.com> - 2016-01-18 21:21 -0500
csiph-web