Hi Jeff et al, Thanks for responding. I was kind of afraid (but expected) that that'd be the situation :(...
Yours, Jim ---- Jeff Trawick <traw...@gmail.com> wrote: > On Tue, Apr 2, 2013 at 3:21 AM, Ian B <porj...@yahoo.com.au> wrote: > > > ap_log_rerror is part of the core libraries, see: > > > > http://ci.apache.org/projects/**httpd/trunk/doxygen/group__** > > APACHE__CORE__LOG.html<http://ci.apache.org/projects/httpd/trunk/doxygen/group__APACHE__CORE__LOG.html> > > > > so I think you're going to have trouble making this work without a > > recompile. > > > > The trouble you'll have is that even if you make up some hacks to get it to > load it will crash and burn (structure field offset and size changes, etc.) > whenever moving from one stable release to another (1.3->2.0, 2.0->2.2, > 2.2->2.4, etc.). > > It absolutely must be rebuilt from source. > > > > > > > > -----Original Message----- From: oh...@cox.net > > Sent: Tuesday, April 02, 2013 7:20 AM > > To: modules-dev@httpd.apache.org > > Subject: Apache 2.4.4 - undefined symbol: ap_log_rerror > > > > > > Hi, > > > > We use a 3rd party module that works fine with Apache 2.2.x, but when we > > try it with Apache 2.4.4, we get the Subject error: > > > > undefined symbol: ap_log_rerror > > > > From searching, this is due to changes in Apache 2.4, and what I've seen > > says that the module needs to be re-compiled for Apache 2.4. > > > > However, we don't have access to the source for the module (it's an Oracle > > module), and they are not saying when or if they'd modify the module for > > Apache 2.4.x, so I was wondering if there is any way to work around this. > > > > What I'm thinking/wondering if it'd be possible to LoadModule whatever > > module exports that ap_log_rerror (and probably other ap_ symbols), then > > maybe this would work? > > > > So, I was wondering if anyone tell me which shared library/.so that > > ap_log_rerror is exported from? > > > > Thanks, > > Jim > > > > > > -- > Born in Roswell... married an alien... > http://emptyhammock.com/
