#18873 [Csd]: qtdom extension causes CLI compilation to fail

ID: 18873 User updated by: kennyz@nycap.rr.com Reported By: kennyz@nycap.rr.com Status: Closed Bug Type: Compile Failure Operating System: Linux 2.4.19 PHP Version: 4CVS-2002-08-12 New Comment: I downloaded and built 200208131800, and everything built fine, including qtdom and db2. Therefore, I would consider the "qtdom" bug to be closed, and there is no need for me to open up a new "db2" bug, since it must have been fixed sometime today. Thanks for all your assistance and extremely prompt response time. Previous Comments: ------------------------------------------------------------------------ [2002-08-13 11:25:52] kalowsky@php.net Good so this is fixed. Regarding your other problem, please open a new bug with regards to that... one bug per report. I know a pain.. ------------------------------------------------------------------------ [2002-08-13 11:10:46] kennyz@nycap.rr.com Alright, qtdom.c appears to have compiled now. I changed the PHP_NEW_EXTENSION() macro to include qtdom.c, then ran ./cvsclean, followed by ./buildconf. After running ./configure, I already noticed that qtdom.lo was mentioned in the Makefile, so I was confident that it would work. HOWEVER, the PHP CLI still did not build. Here is the new error. It's probably a similar problem with a different module: ext/dba/dba_db2.lo: In function `dba_open_db2': /usr/local/src/Internet/php4-200208122100/ext/dba/dba_db2.c:74: undefined reference to `db_open' collect2: ld returned 1 exit status make: *** [sapi/cli/php] Error 1 Any ideas? ------------------------------------------------------------------------ [2002-08-13 10:16:23] kalowsky@php.net After fixing the config.m4 you will need to do "./cvsclean" and "./buildconf" to rebuild the configure script and reflect your changes. If you don't have some of the devtools (libtool 1.4.x or autoconf 2.1.5) just grab a recent snapshot as this will have already been built for you. ------------------------------------------------------------------------ [2002-08-13 10:13:18] kennyz@nycap.rr.com As you requested, I checked to see if qtdom.c was listed in the PHP_NEW_EXTENSION() macro. It was not. I added "qtdom.c" to the PHP_NEW_EXTENSION() parameter list in ext/qtdom/config.m4, so that each of the two occurrences of it looked like: PHP_NEW_EXTENSION(qtdom, qtdom_qt.cpp qtdom.c, $ext_shared) I then ran "configure" and tried building. Once again, the build failed at the same spot, with the same error. I checked in ext/qtdom, and the file qtdom.c was never built into qtdom.o. It is also not mentioned in the top-level generated Makefile. Maybe the fact that there is both a .cpp file and .c file confuses something in the configure process. I even changed PHP_NEW_EXTENSION() to include ONLY qtdom.c, and after running configure, the top-level Makefile still referenced only qtdom_qt.lo. I think configure must be finding qtdom_qt.cpp on its own, independent of whatever the PHP_NEW_EXTENSION() macro specifies. I don't think I need to build PHP all the way in order to test this anymore. I think it's clear right after the configure process whether or not qtdom.c was included by looking at the top-level Makefile. ------------------------------------------------------------------------ [2002-08-13 08:33:09] kalowsky@php.net can you make sure the config.m4 for ext/qtdom contains the qtdom.c file in the PHP_NEW_EXTENSION lines? If it doesn't please add it, or wait for a newer snapshot and try again. If it doesn, back to the drawing board for this.. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/18873 -- Edit this bug report at http://bugs.php.net/?id=18873&edit=1