Since when did libexpat become a module?? The symbol XmlInitUnknownEncoding is defined in srclib/apr-util/xml/expat/lib/xmltok.c which is part of libexpat. So its plain impossible for XmlInitUnknownEncoding not to be defined. Have you tried to do an "ldd -v libexpat.so.0" to see if there is any other library that libexpat depends on and which cannot be found? -ascs -----Original Message----- From: httpd2@xxxxxxxxxxxx [mailto:httpd2@xxxxxxxxxxxx] Sent: Monday, January 23, 2006 4:46 PM To: users@xxxxxxxxxxxxxxxx Subject: Re: [users@httpd] Problem compiling 2.2.0 on solaris 8 with enabling so It may be that Apache does not like the lib/libexpat.so module. Try commenting it out in httpd.conf. See if Apache will start then. If so, then that is obviously where the problem is. Keith In theory, theory and practice are the same; In practice they are not. On Mon, 23 Jan 2006, Harald Falkenberg wrote: > From: Harald Falkenberg <harald.falkenberg@xxxxxxx> > Subject: [users@httpd] Problem compiling 2.2.0 on solaris 8 with > enabling so > > Hallo, > > I'm trying to compile httpd 2.2.0 on solaris 8 and enabling shared > libs via using the configuration: > ./configure --prefix=/home/www/httpd-serv_2.2.0/ --enable-so > > The configuration, make and make install steps seem to run without > problems. But when I try to start the server processes I get the > following > problem: > $ ./apachectl start > ld.so.1: /home/www/httpd-serv_2.2.0/bin/httpd: fatal: > relocation error: file > /home/www/httpd-serv_2.2.0/lib/libexpat.so.0: symbol > XmlInitUnknownEncoding: referenced symbol not found Killed > > > Did I miss something or do I encounter a real problem? When I omit > --enable-so I get a startable server and so far I tested properly > running httpd server. > > Any help is welcome! > > regards > Harald --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|