From: Major A <an...@us...> - 2002-09-17 00:45:45
|
> So far there are people focussed on the C part and the PHP and Perl > extension working on this version. > Therefore your help in improving the autoconf/automake stuff would be > very much appreciated. I have part of the automake/autoconf running on the current CVS tree (written from scratch). If includes the C and PHP parts right now. C++ should be trivial to add, not so sure about Perl and Python. I'll send you the updated files once I have everything ready (the CVS code isn't really going to change in that period :-) ). > Let me know if you're interested in obtaining the current sources and/or > contributing some help to this project. I'd love to get a tarball, if you have it handy. I think ming should be handled in a single CVS tree, single branch. There should be a regular freeze-and-release cycle, which gives people the opportunity to download tested tarballs that are pretty up-to-date. This is the way it's done in SANE, and it works despite the fact that SANE deals with hardware drivers and a single person can usually only test one or two of them. New experimental features (like widechar support) should first be made optional (with a configure option that defaults to "off"). Now that I have a build system for the PHP extension, I went on to find out where the segfault occurs. Well, it's not that easy: 1. Segfaults occur much much more often when running PHP as an Apache module than when running it as a CGI. 2. Running PHP in gdb doesn't produce any segfault at all. 3. Compiling any of the code with checkergcc ruins the PHP interface because it prefixes all symbols. I guess not even recompiling PHP with checkergcc would help here. I guess something (ming, or PHP?) needs some source code auditing... Good night, I'll do the other extensions tomorrow... Andras =========================================================================== Major Andras e-mail: an...@us... www: http://andras.webhop.org/ =========================================================================== |