[opensuse-packaging] php5 compile questions
Hi List, i try to compile php5 on my own to package and make my own setup. I have some difficulties at some extenstions. Is this list also intended to use for questions to php5-configure-line,needed packages and missing libs or only rpm-based questions? I asked in opensuse-list but answer was "why do you compile, you can download it"... and the php-lists are barely useful. Thanks, Andre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Andre Hübner napsal(a):
i try to compile php5 on my own to package and make my own setup. I have some difficulties at some extenstions. ... I asked in opensuse-list but answer was "why do you compile, you can download it"...
Why don't you take the openSUSE php5.spec as a starting point? :) Michal -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
i try to compile php5 on my own to package and make my own setup. I have some difficulties at some extenstions. ... I asked in opensuse-list but answer was "why do you compile, you can download it"...
Why don't you take the openSUSE php5.spec as a starting point? :)
Ok, thats a good point, thank you. I could solve my php5-Problems, wrong configure-switch i did not see. (humpf) Tried to adapt this solution to my php4-project but there are still some errors. Is there a opensuse11 php4-project with current version php4-4.4.9? Could not find anything under http://software.opensuse.org/search Thanks, Andre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Andre Hübner escribió:
i try to compile php5 on my own to package and make my own setup. I have some difficulties at some extenstions. ... I asked in opensuse-list but answer was "why do you compile, you can download it"...
Why don't you take the openSUSE php5.spec as a starting point? :)
Ok, thats a good point, thank you. I could solve my php5-Problems, wrong configure-switch i did not see. (humpf) Tried to adapt this solution to my php4-project but there are still some errors.
php4.spec file is different to the PHP5 one.
Is there a opensuse11 php4-project with current version php4-4.4.9? Could not find anything under http://software.opensuse.org/search
mmarek had a php4 build running, as PHP4 is out of upstream support I dont know what is the current status. -- "A computer is like an Old Testament god, with a lot of rules and no mercy. " Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
php4.spec file is different to the PHP5 one.
ok, is working now. It seems that some standard php4-extensions are hardcoded to lib folder and are ignoring %_libdir params. Latest php4.spec that i found is for php4-4.4.0, they used ~80 patches, may be for this and other reasons... Sure php4 is outdatet but some require it for compatibility reasons. I did also some tests on ubuntu-hardy 64bit where php4 compiling was pretty easy. They hold libs in libfolder, lib64 is symlinked to lib and lib32 separatly. May be a more consequent way of realising 64bit OS? How is this issue seen by other packagers. I dont know backgrounds, what are advantages/disadvantages, in which direction 64bit development will go? Thanks, Andre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Andre Huebner escribió:
php4.spec file is different to the PHP5 one.
ok, is working now. It seems that some standard php4-extensions are hardcoded to lib folder and are ignoring %_libdir params. Latest php4.spec that i found is for php4-4.4.0, they used ~80 patches, may be for this and other reasons...
The 80 patches contains fixes for this and many other problems, that's one of the reasons why it is not included in newer products.
Sure php4 is outdatet but some require it for compatibility reasons.
Care to explain what are your "compatibility" problems ? other than " Im lazy and I dont want to change some code?"
May be a more consequent way of realising 64bit OS?
maybe they use the wrong way ? ;-) How is this issue
seen by other packagers.
There is absolutely nothing to fix in this case, PHP4 is swimming with the fishes, let it rest in peace. -- "A computer is like an Old Testament god, with a lot of rules and no mercy. " Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
Care to explain what are your "compatibility" problems ? other than " Im lazy and I dont want to change some code?" if you work for your own this may be right, but if you are working for b e l o v e d customers you have to do some suboptimal things...
May be a more consequent way of realising 64bit OS? maybe they use the wrong way ? ;-) can you explain this? what could be reasons for two different 64bit layouts? ( i need some arguments against ubuntu ;) )
How is this issue > seen by other packagers. There is absolutely nothing to fix in this case, PHP4 is swimming with the fishes, let it rest in peace.
ok, php4 is dead, but i am interested in general aspects in 64 bit OS design... why did suse choose this direction? seems to be for me a very aggressiv way to push 64bit and cause developers to watch their steps of cost of expensive patching/loss of older software? Thanks, Andre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Andre Huebner escribió: and cause developers to watch their steps of
cost of expensive patching/loss of older software?
the directory layout is a tiny part of the problem, thinking that having libraries in /usr/lib instead of /usr/lib64 will avoid the need of code changes is a very naive way to see things. The place where libraries are doesnt make your software "64bit ready" in anyway see the section "Porting code" of document: http://www.amd.com/us-en/assets/content_type/DownloadableAssets/dwamd_AMD64_... just to have an idea... in short.. if it compiles does not mean it will work ;-) You have the perfect example package where changing the library locations path dont fix anything, PHP4 has a not minor quantity of 64 bit portability problems, that wont ever be fixed, most critical ones where fixed in PHP 5.1.x and the vast mayority of them are fixed in PHP 5.2.x..So.. you may see a lot of strange behaviuors ( that people tend to workaround) crashes..etc.. even in the cases we wanted to fix the problems, we can't :-P because many of the fixes will break the ABI and people out there do rely in third party, propietary extensions... If you use a 64 bit system , you must use PHP 5.x for this and many other reasons... -- "A computer is like an Old Testament god, with a lot of rules and no mercy. " Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
participants (4)
-
Andre Huebner
-
Andre Hübner
-
Cristian Rodríguez
-
Michal Marek