Bug#298028: swig: PHP generation is broken with -zts enabled (and it is now the default in sid)
Package: swig Severity: grave Tags: sid Justification: renders package unusable with zts enabled, any PHP generation generates a lot of errors. in fact, any PHP bindings generated by SWIG now FTBFS with such errors : foo.c|| error: `tsrm_ls' undeclared (first use in this function) ... foo.c|| error: (Each undeclared identifier is reported only once the problem is know upstreams (like said here [1]), but they don't seem very hasty in fixing it. Since this break all the packages generated by SWIG in debian, this is at least grave, and should really be fixed. (I'm sorry, I've not enough php internals knowledge to help you on that). you can read #294003 [2] that is an example of php binding generated by swig that is now broken. [1] http://mailman.cs.uchicago.edu/pipermail/swig-dev/2005-February/014744.html [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294003 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298028: swig: PHP generation is broken with -zts enabled (and it is now the default in sid)
Hi Pierre, On Fri, Mar 04, 2005 at 08:46:41AM +0100, Pierre Habouzit wrote: > Package: swig > Severity: grave > Tags: sid > Justification: renders package unusable Come on, you must be kidding. 1) the problem is already known and you are even referencing that other bug report 2) this breaks only php wrappers generated by swig. Given that swig can generate wrappers for 15 other languages I'd hardly agree that this makes the package unusable. For example the subversion bindings for perl and python are generated using this swig and are working just fine. > with zts enabled, any PHP generation generates a lot of errors. in > fact, any PHP bindings generated by SWIG now FTBFS with such errors : > > foo.c|| error: `tsrm_ls' undeclared (first use in this function) ... > foo.c|| error: (Each undeclared identifier is reported only once I know. > the problem is know upstreams (like said here [1]), but they don't Yes, I reported it. > seem very hasty in fixing it. No, they don't have the knowledge of PHP. > Since this break all the packages generated by SWIG in debian, this is This is false. > at least grave, and should really be fixed. (I'm sorry, I've not enough So this is false as well. > php internals knowledge to help you on that). Me neither. > you can read #294003 [2] that is an example of php binding generated > by swig that is now broken. That's interesting, I did not know of any package using swig to generate PHP bindings. I'll try to find a way to fix this. Steve Langasek already offered his help as well. Greetings Torsten signature.asc Description: Digital signature
Bug#298028: swig: PHP generation is broken with -zts enabled (and it is now the default in sid)
I would just add a warning to SWIG, so that if it is run with the -php argument it outputs a warning like "PHP wrapper support is currently broken with Debian. Please see Sourceforge bug whatever (provide a link maybe too)". I would also say since it is only a problem with threading if a user really needed to use SWIG on something, they could recompile apache and recompile php themselves and then still use the SWIG that would be in debian, just ignoring the error. Thus this SWIG package is usable, even from a php standpoint. Lastly, not very many people use SWIG for php... php doesn't even support multiple modules sharing type information (%import). John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]