Re: LoadModule is a syntax error???

> Date: Fri, 1 Dec 2000 12:21:24 -0500 (EST) > From: Patrick Lanphier <planphier@artemisgroup.com> > Reply-To: Patrick Lanphier <planphier@artemisgroup.com> > Cc: php-install@lists.php.net > > You did not compile "mod_so.c" into apache. Yes, I did. I guess I forgot to mention that I _did_ follow the compilation instructions, which explicitly specify the test you described. > {path}httpd -l > > should confirm this if you do not get a line "mod_so.c" it has not been > compiled in. Mine looks like > > Compiled-in modules: > http_core.c > mod_so.c So does mine: Compiled-in modules: http_core.c mod_so.c suexec: disabled; invalid wrapper /var/lib/apache/sbin/suexec All the rest of the modules are dynamic. Only the last LoadModule line, php4_module, gives the "syntax error" and "shared object not open" messages. From /var/lib/apache/conf/httpd.conf: # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Please read the file README.DSO in the Apache 1.3 distribution for more # details about the DSO mechanism and run `httpd -l' for the list of already # built-in (statically linked and thus always available) modules in your httpd # binary. # # Note: The order is which modules are loaded is important. Don't change # the order below without expert advice. # # Example: # LoadModule foo_module libexec/mod_foo.so LoadModule vhost_alias_module libexec/mod_vhost_alias.so LoadModule env_module libexec/mod_env.so LoadModule config_log_module libexec/mod_log_config.so LoadModule mime_magic_module libexec/mod_mime_magic.so LoadModule mime_module libexec/mod_mime.so LoadModule negotiation_module libexec/mod_negotiation.so LoadModule status_module libexec/mod_status.so LoadModule info_module libexec/mod_info.so LoadModule includes_module libexec/mod_include.so LoadModule autoindex_module libexec/mod_autoindex.so LoadModule dir_module libexec/mod_dir.so LoadModule cgi_module libexec/mod_cgi.so LoadModule asis_module libexec/mod_asis.so LoadModule imap_module libexec/mod_imap.so LoadModule action_module libexec/mod_actions.so LoadModule speling_module libexec/mod_speling.so LoadModule userdir_module libexec/mod_userdir.so LoadModule alias_module libexec/mod_alias.so LoadModule rewrite_module libexec/mod_rewrite.so LoadModule access_module libexec/mod_access.so LoadModule auth_module libexec/mod_auth.so LoadModule anon_auth_module libexec/mod_auth_anon.so LoadModule dbm_auth_module libexec/mod_auth_dbm.so LoadModule digest_module libexec/mod_digest.so LoadModule proxy_module libexec/libproxy.so LoadModule cern_meta_module libexec/mod_cern_meta.so LoadModule expires_module libexec/mod_expires.so LoadModule headers_module libexec/mod_headers.so LoadModule usertrack_module libexec/mod_usertrack.so LoadModule unique_id_module libexec/mod_unique_id.so LoadModule setenvif_module libexec/mod_setenvif.so LoadModule php4_module libexec/libphp4.so > > > > I posted this problem a few days ago, but I haven't gotten any replies. > > At the time, I still hadn't narrowed down the cause of that pesky > > "Something may be screwed up" configure message. Apparently it wanted > > /usr/local/lib instead of just /usr/local for --with-iodbc. I fixed > > that, just in case, but it didn't change anything. > > > > Compilation still completes with no errors, but as soon as I make > > install, apachectl configtest fails with: > > Syntax error on line 238 of /var/lib/apache/conf/httpd.conf: > > Cannot load /var/lib/apache/libexec/libphp4.so into server: shared object not open > > > > Line 238 is the first one make install added: > > LoadModule php4_module libexec/libphp4.so > > > > I have to comment out this line and the matching AddModule to get rid of > > this so-called "syntax error". I've deleted the offending line and the > > lines immediately preceeding and following it, and retyped them, just in > > case some invisible glitch snuck in. This had no effect. > > > > Can someone at least give me a hint here? What does "shared object not > > open" mean? Is it referring to libphp4.so? Why wouldn't Apache be able > > to open it if it's in the right place, owned by the Apache user, and set > > to mode 755? Or does "open" have some other meaning for shared > > libraries that I'm not aware of? Do I have to do something to "open" > > it, and if so, what? Or maybe it's some other shared object that isn't > > open? If that's the case, how do I find out which one? I tried > > configuring with just apxs and mysql, and got the same "syntax error". > > > > > > Dist: Slackware 7.1 > > OS: Linux 2.2.16 > > Arch: i586-pc-linux-gnu > > PHP: 4.0.3pl1 > > Apache: 1.3.12 > > MySQL: 3.23.28-gamma > > PERL: 5.6.0 > > > > configuration: --with-mysql=/usr/local > > --with-dbase > > --with-iodbc=/usr/local/lib > > --with-apxs=/var/lib/apache/sbin/apxs > > --with-msql=/usr/local/msql > > --with-pgsql > > --enable-sysvsem > > --enable-sysvshm > > --with-xml > > --with-config-file-path=/usr/local/etc > > --enable-debugger > > --enable-discard-path > > --enable-force-cgi-redirect > > > > > > > > -- -Dave Noelle, dave@Straylight.org -the Villa Straylight, http://www.straylight.org Coalition Against Unsolicited Commercial Email == http://www.cauce.com Disclaimer: Any similarities to the opinions of any real or hypothetical entities, living, dead, or otherwise, are clearly the reader's own delusion. Quote of the Day: Sign on bank: We can loan you enough money to get you completely out of debt.